Novell ACCESS MANAGER 3.1 SP1 - EVENT CODES Manual page 84

Event Code
500103004
500104002
500104007
500104013
500104014
500104016
500104048
500104113
500105001
500105002
84 Novell Access Manager 3.1 SP1 Event Codes
Message
User interaction policy and
data values received.
Getting properties from file
(informational)
X509 Authentication matched
principal (informational)
No CRL/OCSP defined by the
administrator
No CRL/OCSP found in the
certificate.
Could not fetch CRL from the
local cache (informational)
Successfully loaded NIDP
PKIX Certificate Path Checker
Class (informational)
Kerberos Principal match
found in the user store
(informational)
Forwarding HTTP request to
cluster member.
Successfully initialized JNDI
connections.
Remedy
Type: INFO:NIDP:WSC:004
Scenario: A Web Service request was made to query or
modify user attributes. It was determined that the user
must be asked if the attribute operation is acceptable.
The user's answers have been returned to the NIDP.
Type: INFO:NIDP:USERAUTH:002
Scenario: Getting properties from file
Type: INFO:NIDP:USERAUTH:007
Scenario: X509 Authentication matched principal
Type: INFO:NIDP:USERAUTH:013
Cause: No CRL/OCSP defined by the administrator
Type: INFO:NIDP:USERAUTH:014
Cause: No CRL/OCSP found in the certificate
Action: CRL/OCSP validations are enabled but no
CRL/OCSP responder URL was defined by the
administrator. CRL/OCSP URLs may be defined if
needed.
Type: INFO:NIDP:USERAUTH:016
Scenario: Could not fetch CRL from the local cache,
getting it from the CDP
Type: INFO:NIDP:USERAUTH:048
Scenario: Successfully loaded NIDP PKIX Certificate
Path Checker Class
Type: INFO:NIDP:USERAUTH:113
Scenario: Kerberos Principal found in the user store
Type: INFO:NIDP:APP:001
Scenario: A request was received on a cluster member
that does not own the authentication information for the
associated user. The request must be processed on the
cluster member that does own the user authentication
information, so the request is being forwarded to that
cluster member.
Type: INFO:NIDP:APP:002
Scenario: NIDP attempts to create JNDI connections to
each user store replica during NIDP startup. In this
case, NIDP was able to establish connections with the
indicated host.