Skip to main content
In ABBYY FlexiCapture, you can implement your own custom Single Sign-On authentication (SSO). This may be necessary if you are using a non-standard identity provider or a non-standard work process. Both SAML 2.0 and JSON Web Tokens (JWT) standards are supported.

​
How custom Single Sign-On authentication works

The authentication process runs in five stages.
  1. The custom application sends the identity data to the identity provider.
  2. The identity provider returns a token containing the identity information.
  3. The application passes the token to the Application Server.
  4. The Application Server issues an internal authentication ticket.
  5. The internal authentication ticket authenticates the user on web stations and API services.
Diagram of the custom Single Sign-On flow in ABBYY FlexiCapture, showing the application sending identity data to the identity provider, receiving an identity token, passing it to the Application Server for an internal authentication ticket, and authenticating against web stations and API services.