Novell ACCESS MANAGER 3.1 SP1 - EVENT CODES Manual page 62

Event codes
Hide thumbs Also See for ACCESS MANAGER 3.1 SP1 - EVENT CODES:
Table of Contents

Advertisement

Event Code
200104024
200104025
200104026
200104027
200104028
200104029
200104030
200104031
62
Novell Access Manager 3.1 SP1 Event Codes
Message
At least one parameter of
OCSPProcessor was
uninitialized.
Request was already
generated.
OCSP response was already
processed
Internal error occurred in the
OCSP Server.
Your request did not fit the
RFC 2560 syntax.
Your request was not signed.
The server was too busy to
answer you.
The server could not
authenticate you.
Remedy
Type: ERROR:NIDP:USERAUTH:024
Cause: At least one parameter of OCSPProcessor was
uninitialized during OCSP validations
Action: Make sure the NIDP/ESP Signing keystore has
appropriate Key/Cert in it. Also, that the NIDP/ESP
OCSP trust store has the valid public-key/certificate of
OCSP server.
Type: ERROR:NIDP:USERAUTH:025
Cause: OCSP request was already generated for
certificate(s)
Action: Check the client certificate chain.
Type: ERROR:NIDP:USERAUTH:026
Type: ERROR:NIDP:USERAUTH:027
Cause: OCSP server responded to the request with an
internal error.
Action: Contact OCSP server administrator.
Type: ERROR:NIDP:USERAUTH:028
Cause: OCSP server responded to the request with
malformed request message.
Action: Contact OCSP administrator and check the
request.
Type: ERROR:NIDP:USERAUTH:029
Cause: Request to OCSP server needs to be signed.
Action: Enable signing of OCSP requests in
X509Class administration.
Type: ERROR:NIDP:USERAUTH:030
Cause: OCSP server is too busy to respond to
requests.
Action: Contact OCSP server administrator.
Type: ERROR:NIDP:USERAUTH:031
Cause: OCSP server could not authenticate Novell
Identity server.
Action: Make sure Signing of OCSP requests is
enabled and NIDP signing keystore has appropriate key
in it. Also, make sure the OCSP server trusts Nidp
server.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents