Novell ACCESS MANAGER 3.1 SP1 - EVENT CODES Manual page 88

Event Code
600102008
600102009
600102010
600105001
600105002
600105003
600105004
600105005
88 Novell Access Manager 3.1 SP1 Event Codes
Message
Adds verbose data to reading
Credential Profile data from
Novell Secret Store.
The user successfully logged
into Novell Secret Store using
SAML/SASL.
Adds verbose data to reading
Credential Profile data from
an extended user
authentication object attribute.
Do not need to proxy HTTP
request to other cluster
member. Well known URL
that does not require the use
of a proxy.
Do not need to proxy HTTP
request to other cluster
member. This cluster member
can handle requests for this
user.
Obtained IP address of cluster
member handling this users
requests from URL parameter.
Obtained IP address of cluster
member handling this users
requests from HTTP cookie.
Obtained IP address of cluster
member handling this user's
requests by asking cluster
members which one handles
this user session.
Remedy
Type: DEBUG:NIDP:WSF:008
Scenario: A request was made to query data from a
user's Credential Profile. The data was successfully
read.
See Also: 500102011
Type: DEBUG:NIDP:WSF:009
Scenario: To access secrets from Novell Secret Store,
the user must authenticate to Novell Secret Store.
Type: DEBUG:NIDP:WSF:010
Scenario: A request was made to query data from a
user's Credential Profile. The data was read from an
extended schema attribute on the user's authenticated
user object.
See Also: 500102012
Type: DEBUG:NIDP:APP:001
Scenario: The request is one of a well known list of
request types that may be processed on any cluster
member, so it does not need to be forwarded to another
cluster member.
Type: DEBUG:NIDP:APP:002
Scenario: The request arrived at the cluster member
that owns the authentication information for the user.
The request may have come straight from the router to
this cluster member, or the request may have been
forwarded here by another cluster member.
Type: DEBUG:NIDP:APP:003
Scenario: Each request must be processed on the
cluster member that owns the user authentication
information. The IP address of that cluster member was
found in a URL parameter.
Type: DEBUG:NIDP:APP:004
Scenario: Each request must be processed on the
cluster member that owns the user authentication
information. The IP address of that cluster member was
found in an HTTP cookie.
Type: DEBUG:NIDP:APP:005
Scenario: Each request must be processed on the
cluster member that owns the user authentication
information. The IP address of that cluster member was
found by asking all cluster members which one knew
about the user's session.