Integrate provisioning functionality
- 13 Dec 2024
- 1 Minute à lire
- SombreLumière
- PDF
Integrate provisioning functionality
- Mis à jour le 13 Dec 2024
- 1 Minute à lire
- SombreLumière
- PDF
The content is currently unavailable in French. You are viewing the default English version.
Résumé de l’article
Avez-vous trouvé ce résumé utile ?
Merci pour vos commentaires
Provisioning can be integrated via client integration or in the context of back-end authentication. It can be processed as single-device licensing (SDL) (see Standard provisioning operations) or multi-device licensing (MDL) provisioning (see Multi-device licensing (MDL) provisioning operations).
Client integration
OneSpan Authentication Server provisioning functionality can be integrated into any application that supports SOAP. This integration can be done at the client level by one of the following:
- Using provisioning client interface wrappers
- Sending SOAP requests directly
OneSpan provides standard wrappers for integrating OneSpan Authentication Server features into custom applications. For more information about wrappers provided by OneSpan in the OneSpan Authentication Server SDK, see Wrappers.
Back-end authentication
You can integrate back-end authentication in the context of software authenticator provisioning (SDL and MDL) or compliant hardware authenticator provisioning (MDL, Digipass 760).
Integrating provisioning via back-end authentication is useful when a legacy authentication system is used to verify a historical password. With this type of integration, the historical password is used as user credential that must be provided as part of the registration request. Once the historical password is provided, a software authenticator is assigned to that user.
For more information, refer to the OneSpan Authentication Server SDK Plug-In Engine Guide.
Cet article vous a-t-il été utile ?