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

Part Number E10113-10
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
PDF · Mobi · ePub

90 STS-10506 to STS-15541

STS-10506: Username Token Password type {0} is not recognized
Cause: The password type has not been configured in the sts configuration file
Action: Create a mapping for the passwordtype in the usernametokenpasswordtypeuris map

Level: 1

Type: ERROR

Impact: Configuration

STS-10507: Multiple partners {2} were returned during the token mapping operation with Attribute ID={0} and Token Value={1}
Cause: Multiple partner entries have the same identification strings
Action: Update the configuration for the partners so that there is no conflict

Level: 1

Type: ERROR

Impact: Configuration

STS-12500: Xpath Exception: {0}.
Cause: An Xpath exception occurred while trying to locate desired xml element.
Action: Verify that incoming xml message was correct.

Level: 1

Type: ERROR

Impact: Other

STS-12501: JAXB Exception: {0}.
Cause: A JAXB exception occurred while trying to parse the xml element.
Action: Verify that the xml message was correct.

Level: 1

Type: ERROR

Impact: Other

STS-12507: Invalid Key Exception: {0}.
Cause: An invalid key exception has occurred.
Action: Verify that all the keys present in all the certificates are valid (correct length, format, etc).

Level: 1

Type: ERROR

Impact: Other

STS-12508: Signature Exception: {0}.
Cause: A signature exception has occurred, certificate signature could not be verified.
Action: Check logs and exception message for more information.

Level: 1

Type: ERROR

Impact: Other

STS-12510: Signing template configured in the template is missing.
Cause: An error occurred due to missing signing template.
Action: Check configuration to add the missing signing template or check the template to specify an existing signing template.

Level: 1

Type: ERROR

Impact: Other

STS-12511: Encryption template configured in the validation template is missing.
Cause: An error occurred due to missing encryption template.
Action: Check configuration to add the missing encryption template or check the validation template to specify an existing signing template.

Level: 1

Type: ERROR

Impact: Other

STS-12512: Token processing Exception: {0}
Cause: An exception has occurred during token processing.
Action: Check logs and exception message for more information.

Level: 1

Type: ERROR

Impact: Other

STS-12513: Keysource Exception: {0}.
Cause: A keysource exception has occurred during token processing
Action: Check logs and exception message for more information.

Level: 1

Type: ERROR

Impact: Other

STS-12514: No authenticator was found for authentication type: {0}.
Cause: AuthenticationType specified for UsernameToken validation is invalid in template
Action: Check the authentication type in validation template

Level: 1

Type: ERROR

Impact: Other

STS-12515: No validation template found.
Cause: Validation template was not found
Action: Check configuration to add validation template

Level: 1

Type: ERROR

Impact: Other

STS-12516: Unknown token: {0}.
Cause: Token is not known type
Action: Check the token type in the message

Level: 1

Type: ERROR

Impact: Other

STS-12517: Unknown name id format: {0}
Cause: Name ID format is not known
Action: Check the nameid format

Level: 1

Type: ERROR

Impact: Other

STS-12518: User was not mapped.
Cause: The user could not be mapped.
Action: Check the logs for more information

Level: 1

Type: ERROR

Impact: Other

STS-12519: Recipient providerID not found
Cause: The recipient provider not found
Action: Check logs for more information

Level: 1

Type: ERROR

Impact: Other

STS-12520: Certificate not found for provider: {0}
Cause: Certificate was not found for the provider
Action: Obtain the required certificates

Level: 1

Type: ERROR

Impact: Other

STS-12521: Requester providerID not found.
Cause: The requester provider was not found.
Action: Check the logs for more information

Level: 1

Type: ERROR

Impact: Other

STS-12531: Requested claims have been filtered due to policies
Cause: The Requester or Recipient Partner profiles filtered out some requested claims
Action: Check the list of attributes that can be requested by a Requester in the partner profiles of the Requester and Recipient

Level: 1

Type: ERROR

Impact: Other

STS-12532: WSS Token Error: {0}.
Cause: Token is Missing
Action: Check that the token is present in wss header

Level: 1

Type: ERROR

Impact: Other

Cause: Token Type mismatch.
Action: Check that the token matches the token type in the validation template of the endpoint
Cause: Custom token not correctly defined in configuration
Action: Check that the custom token is configured correctly in the server
STS-12533: Invalid Token Mapping Action for None Token Type: {0}
Cause: Token Mapping Action is not valid
Action: The token mapping action should be none or maprequesterbindingdata for tokentype none

Level: 1

Type: ERROR

Impact: Other

STS-15504: Validation template cannot be used to process the following type of token: {0}
Cause: The validation template is configured to process a token type different from the one presented
Action: Check that the validation template is configured for the correct protocol type

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15505: Token is missing during validation processing with validation template {0}
Cause: The security token is missing in the incoming request
Action: Check that the request is providing the expected security token for the validation template

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15506: Missing data for SAML Authentication Statement
Cause: The authentication method or context is missing
Action: Check that the token was validated correctly and that an authentication mechanism was set by the validation module

Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: The authentication instant is missing
Action: Check that the token was validated correctly and that an authentication mechanism was set by the validation module
STS-15507: Digest Password Type not supported for Username Token Validation
Cause: The Username Token contains a Password of type Digest
Action: Contact the client to request the password to be of type Text in the Username Token

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15508: Authorization Failure for Relying Party {0}, Requester {1} and User {2}
Cause: The authorization policy evaluation failed for the specified parameters
Action: Check the configuration and/or policy for any errors

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15509: Assertion ID is missing
Cause: The SAML Assertion in the Validation Request has AssertionID missing
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15510: Invalid SAML version in the token
Cause: THE SAML Version specified in the token is not valid
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15511: Issuer information is missing
Cause: Issuer information in the token to be validated is missing
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15512: Invalid issue instant
Cause: Token Issue instant is not valid
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15513: NOT_BEFORE Condition failed for the token
Cause: NOT_BEFORE condition for the token validity failed
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15514: NOT_ONAFTER Condition for the token failed
Cause: NOT_ONAFTER condition for the token validity failed
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15515: Authentication Time is invalid
Cause: Authentication time for the token is not valid
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15516: Subject is invalid
Cause: Subject for the token is not Valid
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15517: Authentication Method is not specified
Cause: Authentication Method is not specified in the token
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15518: Authentication Instant is missing
Cause: Authentication Instant is missing in the token
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15519: Authentication Context is missing
Cause: Authentication Context is not specified in the token
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15520: Subject Confirmation NOT_ONBEFORE condition failed
Cause: The assertion not before condition was not satisfied
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15521: Subject Confirmation NOT_ONAFTER condition failed
Cause: The subject confirmation not on or after condition was not satisfied
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15522: Authentication Statement NOT_ON_AFTER condition failed
Cause: The authentication statement not on or after condition was not satisfied
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15523: Creation Date could not be parsed
Cause: The created date format could not be parsed
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15524: Creation Time is not valid
Cause: The created time was before the valid period
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15525: Nonce was already used
Cause: The nonce in the message was previously used
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15526: No Username in the token
Cause: There is no user name in the token
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15527: Invalid Nonce Encoding
Cause: The nonce encoding type is invalid
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15528: Nonce could not be decoded
Cause: Nonce could not be decoded
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15530: Token could not be prased
Cause: The token could not be parsed
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15531: Token Type {0} is invalid
Cause: Token Type is not valid
Action: Check that the token type in the SOAP request is valid

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15532: Signature in the token could not be verified
Cause: Signature in the token could not be verified
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15533: Nonce Encoding is neither null nor default
Cause: Nonce Encoding is neither null nor default
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15534: Message could not be decrypted
Cause: The message could not be decrypted
Action: Check the logs and Exception for more information

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15535: SAML 1.1 Assertion does not contain any statements
Cause: No Attribute Statement and no Authentication Statement are included in the Assertion
Action: Check that the Oracle Secure Token Service is configured to include one of the statements

Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: No Attribute Statement and no Authentication Statement are included in the Assertion, even if Oracle Secure Token Service is configured to include an Attribute Statement
Action: Check that at least one attribute can be used to populate the Attribute Statement
STS-15538: WSS token validation failed for ValidationTemplateID: {0} and Message {1}
Cause: Invalid WSS token
Action: Provide valid WSS token.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15541: WSTrust token validation failed for ValidationTemplateID: {0} and Message {1}
Cause: Invalid WSTrust token
Action: Provide valid WSTrust token.

Level: 1

Type: ERROR

Impact: Requests/Responses