When a user with an Azure AD Premium authentication type cannot be authenticated in QM10, the 1st thing to confirm is connecting to Microsoft services with the same user account used to login to SOLABS QM10 (Production environment) using the following URL:
Your password may have expired or has been reset, which forces a new password to be created.
Alternatively you can use the following URL to change your Microsoft password:
Once access to the Microsoft services has been confirmed, and after confirmation that the user account is not locked in QM10, accessing QM10 should no longer be an issue.When access to QM10 (Production) works fine, but the user cannot access other SOLABS services (ex.: the reports or the eRoom), it is quite possible that the relationship between the Microsoft credentials and the SOLABS infrastructure is out of sync.
In this situation, the user should start by accessing the Microsoft services to change their password, set a New one, and then log into their SOLABS QM10 Production instance. The new password is asked when login in to QM10 (Production). Once login has been confirmed, access to the other SOLABS Services should no longer be an issue.
Learn more on our SEO integrations: Single Sign-On solutions & QM10 – SOLABS
Comments
0 comments
Please sign in to leave a comment.