
- The user clicks the Log in with [external server name] button.
-
ABBYY FlexiCapture generates an
AuthnRequestmessage, puts it into theSAMLRequestparameter of a URL GET request, and sends the request to the identity provider. Encrypted SAML SSO connections are not supported. TheAuthnRequestlooks similar to this: - The identity provider authorizes the user.
-
If the authentication is successful, the identity provider generates an assertion message, puts it into the
SAMLResponseparameter of the request, and sends the request back to ABBYY FlexiCapture. - The request containing the assertion message is sent to the ABBYY FlexiCapture Application Server to determine whether the specified user has the necessary permissions to log in to the specified station.
- The Application Server verifies the assertion message using a public certificate obtained from the identity provider and then authorizes the user.
- The Application Server performs the required operations and issues an internal authentication ticket.
- The user is granted access to the appropriate web station with the issued authentication ticket.
This feature has been tested using the following identity providers: Azure Active Directory, OneLogin, and Okta.
Multiple identity providers can be used simultaneously. For example, different identity providers can be used for different tenants. New authentication methods will be used side by side with the existing methods, including those used by default.
