You can use the error code and message returned by the Barco CIAM service while logging in.
| Error Code | Error Message | Notes |
|---|---|---|
| AADB2C | B2C_1A_ZSSO* policy in 'barcociamdev.onmicrosoft.com' specifies the subject claim 'sub' which is missing in the claims collection. | When using SAML, this means that the assertions you defined in Barco Management Suite are not all present in your IdP. When using OIDC, this means that the claims you defined in Barco Management Suite are not all present in your IdP. |
| An exception has occurred. | Contact Barco support describing your error and add screenshot of the error message. | |
| AADB2C90017 | The client assertion provided in the request is invalid. | When using SAML, this means that the assertions you defined in Barco Management Suite are not all present in your IdP. |
| AADB2C90031 | Policy 'B2C_1A_Common' or 'B2C_1A_ZSSO*' does not specify a default user journey. Ensure that the policy or it's parents specify a default user journey as part of a relying party section. |
This might mean that the URL's used to redirect from the IDP to/from Barco IAM is incorrect (e.g. in Okta setup that the Single sign-on URL or Audience URI are incorrect). Contact Barco support describing your error and add screenshot of the error message. |
| AADB2C90168 | The HTTP-Redirect request does not contain the required parameter 'Signature' for a signed request. | When using SAML, this means the certificate wasn't signed properly. We expect it to be signed – both the SAML response and assertions. The exact signing algorithm can be selected in Barco Management Suite. Note: you need to reupload your certificate after signing. |
| AADB2C90188 | The SAML technical profile 'identityProviderMetadata' specifies a PartnerEntity URL of 'metadata.xml', but fetching the metadata fails with reason 'Unexpected XML declaration. The XML declaration must be the first node in the document, and no white space characters are allowed to appear before it. Line 2, position 3.'. | When using SAML, this means there XML metadata file (uploaded to Barco Management Suite) could not be parsed properly. E.g. the XML file starts with a white space -- removing these will fix the issue. |
| AADB2C90243 | The IDP's client key/secret is not properly configured. | When using OIDC, this means the client key/secret provided in Barco Management Suite are incorrect, updating these will fix this. |
| AADB2C90289 | We encountered an 'invalid_client' error connecting to the identity provider. | |
| E002003 | An internal error has occurred. | When using SAML, this means that the assertions you defined in Barco Management Suite are not all present in your IdP. When using OIDC, this means that the claims you defined in Barco Management Suite are not all present in your IdP. |
