SSO - Login Error Messages

Follow

  

About the most common SSO error messages

You will find below a list below of the most common error messages that may appear when trying to log in using Single Sign On (SSO), please be aware that these are for no means exhaustive of all the possible SSO error messages. 

The following list of error messages could appear after logging into your GAN Compliance portal via SSO.

If the error message you are receiving is not listed below, please don't hesitate to contact the GAN Support.

 

"User does not exist" (UnknownUserError or UserRegistrationError)

  WHY

The message "User does not exist", shown in the screenshot below, means that the GAN Compliance platform does not recognize the username used to log in.

The reason is one of the below:

  • The SSO username is different from the one registered in the GAN platform.
  • Your account has not been added to the GAN platform.

mceclip2.png

mceclip8.png

 

  WHAT TO DO

Please contact your Compliance Manager or the contact person in your company. If you do not know who this person is, do not hesitate to contact Support as they will be able to direct you to the relevant person.

 

"The signed in user is not assigned a role for the application"

  WHY

The message "The signed in user is not assigned a role for the application", shown in the screenshot below, means your account has not been assigned the GAN application on your company's system.

 

mceclip1.png

NB: The screenshot above shows an example of the error message given by the Azure Active Directory, hence the error message you are getting could look slightly different.

 

  WHAT TO DO

Please contact your IT department and ask them to add the relevant application on your company's system.

 

"Authentication method 'WindowsIntegrated' doesn't match"

  WHY

The message "Authentication method 'WindowsIntegrated' doesn't match", shown in the screenshot below, means that the authentication request sent by the application is not accepted by your company's system.

 mceclip3.png

NB: The screenshot above shows an example of the error message given by the Azure Active Directory, hence the error message you are getting could look slightly different.

 

  WHAT TO DO

Please contact your IT department and ask them to investigate on the authentication request for the application.

 

"Invalid Signature"

  WHY

The message "Invalid Signature", shown in the screenshot below, could be due to an update of your company's system certificates and the ones on GAN were not subsequently updated.

mceclip4.png

NB: The screenshot above shows an example of the error message given by the Azure Active Directory, hence the error message you are getting could look slightly different.

 

  WHAT TO DO

Please contact Support with a screenshot of the error message you are receiving, they will be able to ask the competence center to update the certificates.

 

 

"SAML provider error"

  WHY

The message "SAML provider error", shown in the screenshot below, means that the IdP (Identification Provider, client-side) configuration is not correctly set up (Verify certificate / AuthnContext / Transport Protocol).

mceclip6.png

 

  WHAT TO DO

Please contact your IT department and ask them to investigate on the IdP configuration set up.

 

 

"Relay state not found in the body (RelayNotFoundError)"

  WHY

The message "RelayNotFoundError", shown in the screenshot below, means that the identifier is missing from the request.

mceclip9.png

  WHAT TO DO

Please contact your IT department, so they can identify the relay state as it looks as if the identifier is missing from the request.
Was this article helpful?
0 out of 0 found this helpful