Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 1 (11.1.1)

Part Number E10113-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

45 OAMAP-60501 to OAMAP-60520

OAMAP-60501: OAM Access Server entry is not specified in required format host:port
Cause: Some or all of OAM Access Server entries were not specified correctly.
Action: Ensure that OAM Access Server entries are specified in host:port format;where host is name of Access server Hosr and port is the port number.

Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60502: No CallbackHandler is supplied to OAM LoginModule.
Cause: No CallbackHandler was found during OAM LoginModule initialization.
Action: Please contact Oracle support along with the log file.

Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60503: A required callback is not found.
Cause: A required Callback was not found by Provider's LoginModule.
Action: Please contact Oracle support along with the log file.

Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60504: Unable to read user input from CallbackHandler.
Cause: Failed to read user input from CallbackHandler.
Action: Ensure that you enter the credentials.

Level: 1

Type: ERROR

Impact: Data

OAMAP-60505: Found unsupported token type.
Cause: OAM Identity Asserter was invoked with unsupported token type.
Action: Please contact Oracle support along with the log file.

Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60506: Found unsupported token class.
Cause: OAM Identity Asserter received unknown token class "{0}", Expected a byte[].
Action: Please contact Oracle support along with the log file.

Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60507: Found an invalid SSO Token.
Cause: OAM Identity Asserter received a SSO token with no characters.
Action: Please contact Oracle support along with the log file.

Level: 1

Type: ERROR

Impact: Data

OAMAP-60508: Authentication failed, found invalid ObSSOCookie.
Cause: Invalid ObSSOCookie was received.
Action: Ensure that ObSSOCookie is not corrupted/timedout before is is passed to OAM LoginModule.

Level: 1

Type: ERROR

Impact: Data

OAMAP-60509: OAM LoginModule doesn't support NameCallback.
Cause: NameCallback was not found in callback array.
Action: Please contact Oracle support.

Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60510: OAM LoginModule doesn't support PasswordCallback.
Cause: PasswordCallback was not found in callback array.
Action: Please contact Oracle support.

Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60511: Resource "{0}" is not protected in OAM policy for OAM Provider.
Cause: OAM Provider detected that resource "{0}" is not protected in OAM policy for OAM Provider.
Action: Ensure that Resource type, Resource Name and Resource operations are specified correctly for provider and resource specified by Resource Name is protected in OAM.

Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60512: Unable to get user name from Return Actions configured in OAM policy for this provider.
Cause: This provider didn't get any Return Action named uid from Access Server.
Action: Ensure that Return Action is configured correctly in OAM policy to return user's login name.

Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60513: Required parameters are not configured for OAM provider.
Cause: OAM Provider didn't find one or more required parameters.
Action: Ensure that AccessGate Name, AccessGate Password, Primary/Secondary Access Server Name parameters are specified correctly.

Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60514: Unable to get user name.
Cause: No user name found in NameCallback.
Action: Specify a user name during authentication challenge.

Level: 1

Type: ERROR

Impact: Data

OAMAP-60515: AccessGate Name is not recognised by OAM Access server.
Cause: Incorrect AccessGate name was found.
Action: Go to OAM Admin Console and ensure that AccessGate name configured for OAM Authenticator exists in OAM.

Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60516: Unable to create OAM Provider AccessGate.
Cause: AccessGate instance creation failed.
Action: Please look into OAM Provider logs for error.

Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60517: Failed to validate SSO Token.
Cause: OAM Provider failed to validate SSO token.
Action: Please look into OAM Provider logs for error.

Level: 1

Type: ERROR

Impact: Data

OAMAP-60518: Authentication failed.
Cause: OAM Provider failed to authenticate with given credentials.
Action: Please look into OAM Provider logs for error.

Level: 1

Type: ERROR

Impact: Data

OAMAP-60519: Couldn't find SSO Token in callback.
Cause: SSO Token was not found in CallbackHandler.
Action: Please contact Oracle support.

Level: 1

Type: ERROR

Impact: Internal Error.

OAMAP-60520: Couldn't get a logger instance.
Cause: Couldn't create a logger instance.
Action: Please contact Oracle support.

Level: 1

Type: ERROR

Impact: Internal Error.