Common Errors Encountered When Using AD FS - Common Errors Encountered When Using AD FS - OnBase - Legacy Authentication Methods - OnBase/Legacy-Authentication-Methods/Foundation-25.1/Legacy-Authentication-Methods/Configuring-Active-Directory-Federation-Services-AD-FS/Troubleshooting/Common-Errors-Encountered-When-Using-AD-FS - Foundation 25.1 - Foundation 25.1

The following errors may be encountered when using AD FS and are typically resolved by the solutions presented in the following sections:

• A SignInResponse message may only redirect within the current application

• Bootstrap Token was Empty

• Failed to connect. User '' does not belong to any user groups.

• HTTP 400 Bad Request

• Object not set for an instance of an object

• OEM Authentication Failed

• SAML Assertions are not included in token

• The issuer of the security token was not recognized by the IssuerNameRegistry

• The same client browser session has made X requests in the last Y seconds. Contact your administrator for details.

• The type initializer for Hyland.Canvas.CanvasClientConfiguration threw an exception

• This page cannot be displayed

• Value cannot be null

• Web Client displays a login page