When your web applications run in a single sign-on environment, it's possible to configure Acrolinx to work with single sign-on as well.
If you're on an Acrolinx Private Cloud instance and are interested in using single sign-on, contact us and we'll set it up for you!
Single sign-on (SSO) is a user authentication process. When you set up single sign-on, your users only have to provide their sign-in details once. That way, they don’t have to enter their sign-in details again when they switch applications. Network administrators can also use single sign-on to give users access to specific applications.
Web single sign-on only works with applications users access with a web browser. A component in the web server or the application itself receives the request to access a web resource. Unauthenticated users are sent to an authentication service and can return only after a successful authentication.
The terms "single sign-on" and "external authentication" might seem interchangeable, but they're not the same thing.
Single sign-on is a system that allows one application to trust a user that another application has already authenticated. If you have an Acrolinx Private Cloud instance, you’ll use SAML and PingFederate to Authenticate Users.
External authentication is the process of authenticating a user with an external service. For Standard Stack, you can authenticate your users with LDAP.
You can configure Acrolinx to search for an SSO identifier in the request header that the web browser sends.
When users sign in to your web application and run a check with Acrolinx, the user sign-in details are passed on to Acrolinx. If a user already exists, no further action is required. When a user doesn’t yet exist, the user is automatically created in the Acrolinx database with the same username that they used to sign in to your web application.