When applications do not natively support OATH seed imports, Deepnet DualShield can act as your SAML 2.0 Identity Provider (IdP) to seamlessly manage hardware tokens and authenticate users.
The DualShield SAML Bridge integrates with various platforms across Cloud Infrastructure, IAM, Password Managers, Developer Tools, Security Hardware, and Business Productivity apps. Configuration involves importing token seeds, creating token-based logon procedures, exchanging metadata, and registering service providers.
Refer to the official documentation for comprehensive integration steps and app-specific directories.
If your application is not listed in this table but supports external identity providers (as most do), you can still integrate it using our general SAML solution or with assistance from our support team.
General SAML Solution (For Any SAML-Compatible Service)
Even if your specific application is not listed in our product-specific guides below, you can still use pre-programmed hardware tokens as long as the service supports SAML 2.0 Single Sign-On (SSO).
- Import Your Token Seeds: Upload your pre-programmed hardware token seed file into the DualShield Management Console and assign the tokens to your users.
- Create a Logon Procedure & Application: Configure a SAML-enabled Logon Procedure in DualShield that requires a hardware token (OTP) as an authentication factor.
- Exchange Metadata: Download the DualShield Identity Provider (IdP) metadata and signing certificate, and upload them to your service provider.
- Register the Service Provider: Add your application's Service Provider (SP) metadata (Entity ID and Assertion Consumer Service URL) into DualShield.
For step-by-step instructions on configuring any SAML 2.0 service provider, refer to our core SAML Integration Tutorial.