Novell ACCESS MANAGER 3.1 SP1 - EVENT CODES Manual page 65

Event Code Message
200104054 Error processing certificate
validations.
200104055 Protocol not supported or
none specified.
200104057 Unable to do X509 Certificate
based authentication over non
SSL (HTTP)
200104100 Error processing
Authorization header
200104101 Error processing SPNEGO/
Kerberos
200104102 No Kerberos Principal found
in the token
200104103 No SPNEGO Token found
200104104 GSS Context already
established
200104106 Unrecognized SPNEGO
Token
Remedy
Type: ERROR:NIDP:USERAUTH:054
Cause: Error processing CRL/OCSP validations.
Action: Check X509class config and user/client
certificate CRL extension.
Type: ERROR:NIDP:USERAUTH:055
Cause: Transport protocol not supported to fetch CRL.
Action: Currently, CRLs can be fetched over http and
LDAP protocols. Make sure the X509class config and/
or user/client certificate CRL extension does not have
any other transport protocol specified.
Type: ERROR:NIDP:USERAUTH:057
Cause: URL protocol is HTTP
Action: URL protocol needs to be HTTPS
Type: ERROR:NIDP:USERAUTH:100
Cause: Could not process HTTP Authorization header
Action: Try with correct authorization header with
base64 encoded SPNEGO token
Type: ERROR:NIDP:USERAUTH:101
Cause: Error processing SPNEGO/Kerberos. The
cause is included in detailed message
Action: Take action as per the detailed error message
Type: ERROR:NIDP:USERAUTH:102
Cause: Failure at GSS-API
Action: Make sure the Kerberos keytab file is
generated correctly by KDC
Type: ERROR:NIDP:USERAUTH:103
Cause: No SPNEGO Token found in the request
Action: Include the SPNEGO token in the request to
use this authentication
Type: ERROR:NIDP:USERAUTH:104
Cause: GSS Context already established
Action: Close the browser and try again
Type: ERROR:NIDP:USERAUTH:106
Cause: Unrecognized SPNEGO Token
Action: Include the correct SPNEGO token in the
request to use this authentication
Identity Server (001) 65