Once the SSO feature is configured and activated a few changes happen in the system.
Here is a list of changes:
- Authentication requests are redirected to the SSO user directory:
- The authentication box will change and reflect the SSO provider activated.
- The username and password to be used will now be the one from your SSO vendor (Microsoft Azure or One Login)
- Login types will now be restricted the login type related to the activated SSO vendor:
- Microsoft Azure, login type = Azure AD
- One Login, login type = OneLogin
- Our internal user directory (Microsoft Active Directory), will continue synchronizing your username and password from your SSO directory to enable a seamless customer experience with other services offered within the QM10 ecosystem like the QM10 Report portal.
- e-Signatures are also redirected to your selected SSO vendor for validation, there is however no visual change in the system that can be perceived by the user.
- For external accounts, we suggest the use of B2B when using Microsoft Azure.
Known-issues with SSO & SOLABS QM:
Wrong "login error" page:
- When a user that has an external SSO Login Type (Azure AD or OneLogin) is locked or deactivated and then tries to access the application, they will be directed to a general error page (OOOPS! page) instead of being directed to the Login page that displays the appropriate error message
ERoom Link not displayed:
- The ERoom link is not displayed at the top of the SOLABS QM10 page for accounts having the One Login or Azure or Login Types, for users that have the appropriate ERoom access role in the Root Instance.
Learn more about our SSO Capabilities: Single Sign-On solutions & QM10 – SOLABS