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

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

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

85 STS-10102 to STS-20000

STS-10102: The LDAP connection settings have not been configured.
Cause: The configuration properties for LDAP connection have not been set.
Action: Enter the LDAP connection settings in the Oracle Secure Token Service Data Stores configuration..

Level: 1

Type: ERROR

Impact: Configuration

STS-10152: LDAP BindDN or password is incorrect.
Cause: The LDAP BindDN or password was configured incorrectly.
Action: Check the LDAP configuration entry for BindDN and bind password.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10158: Unable to find the exception handler mapping for the exception {0}.
Cause: ExceptionHandler mapping for this exception was missing in the configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10159: Unable to find the request handler mapping for this URL {0}.
Cause: RequestHandler mapping for this URL was missing in the configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10160: Unable to find the response handler mapping for this event response {0}.
Cause: ResponseHandler mapping for this EventResponse cannot be found in configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10161: Unable to locate a mapping for {0}.
Cause: Mapping for this class could not be located.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10164: Invalid peer provider configuration for: {0}
Cause: Metadata for this peer provider is invalid.
Action: Load metadata for this peer provider.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10168: DiscoveryProvider was not found for {0}.
Cause: A DiscoveryProvider for this type of provider is not configured.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10170: Handler was not found for URL: {0}.
Cause: Handler for this response is missing from configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10174: Property was not found: {0}.
Cause: Property is not set in configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10175: First package-search-order is used as default package search order.
Cause: Group of package-search-order was found in configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: WARNING

Impact: Configuration

STS-10179: Mapping was not defined for action {0}
Cause: Mapping for the specified action was not defined in the configuration.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: ERROR

Impact: Configuration

STS-10180: Business Processing Plugin error: {0} does not implement OperationListener
Cause: Business Processing Plugin configuration is incorrect.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10181: Property is not type of Boolean: {0}
Cause: Property was not correctly set in configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10182: Property is not of type Long: {0}
Cause: Property was not correctly set in configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10183: Property is not of type Set: {0}
Cause: Property was not correctly set in configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10184: Property is not of type List: {0}
Cause: Property was not correctly set in configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10185: Property is not of type Map: {0}
Cause: Property was not correctly set in configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10186: Property is not of type String: {0}
Cause: Property was not correctly set in configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10192: Oracle Access Server SDK could not be initialized.
Cause: There was an error during initialization of the Oracle Access Manager SDK.
Action: Check the Access Server SDK logs for diagnostic information.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10203: Property could not be retrieved from the Credential Store Framework: {0}
Cause: The Credential Store Framework did not refresh.
Action: Set the credentials again using Enterprise Manager or restart the WLS Managed Server where Oracle Secure Token Service is running.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10204: Property is not of type Integer: {0}
Cause: Property was not correctly set in configuration file.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-10503: The load of configuration for instance{0} failed for element {1} :{2}
Cause: The configuration file may be invalid or the instance and element may not be present
Action: Check the configuration file for validity and make sure the instance and the element exist

Level: 1

Type: ERROR

Impact: Configuration

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-10508: Oracle Secure Token Service is disabled
Cause: The Oracle Secure Token Service is disabled
Action: Check the configuration and enable Oracle Secure Token Service if required

Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

STS-11008: RequestHandlerMapping {0} already exists.
Cause: RequestHandlerMapping was already present.
Action: No Action.

Level: 1

Type: WARNING

Impact: Data

STS-11009: ResponseHandlerMapping {0} already exists.
Cause: ResponseHandlerMapping was already present.
Action: No Action.

Level: 1

Type: WARNING

Impact: Data

STS-11010: Replacement RequestHandlerMapping is: {0}.
Cause: RequestHandlerMapping was replaced with the new RequestHandlerMapping.
Action: No Action.

Level: 1

Type: WARNING

Impact: Data

STS-11011: Replacement ResponseHandlerMapping is: {0}.
Cause: ResponseHandlerMapping was replaced with the new ResponseHandlerMapping.
Action: No Action.

Level: 1

Type: WARNING

Impact: Data

STS-11023: Coherence chache miss occurred querying persistent store.
Cause: Object not found in coherence map
Action: No Action required

Level: 1

Type: NOTIFICATION

Impact: Data

STS-11700: Cannot connect to the LDAP server.
Cause: The LDAP credentials were incorrect.
Action: Verify the LDAP credentials in the Oracle Secure Token Service configuration.

Level: 1

Type: ERROR

Impact: Network

STS-11703: Exception while trying to connect to LDAP server.
Cause: Oracle Secure Token Service could not open a connection to the LDAP server.
Action: Verify the connection settings in the Oracle Secure Token Service configuration and that LDAP server is up.

Level: 1

Type: ERROR

Impact: Network

STS-11704: Cannot close LDAP connection.
Cause: Problem while closing the LDAP connection.
Action: Check the LDAP server logs.

Level: 1

Type: WARNING

Impact: Network

STS-12000: XML time value is empty.
Cause: An empty string was passed in as an XML time value attribute.
Action: Verify that none of the time value attributes are empty.

Level: 1

Type: ERROR

Impact: Other

STS-12003: Unsupported handler parameter type: {0}
Cause: Parameter type was not supported.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Other

STS-12007: Data Object {0} is no longer valid.
Cause: Object was destroyed.
Action: No Action.

Level: 1

Type: WARNING

Impact: Other

STS-12009: Multiple certificates are found for the public key, attempting to select a valid one.
Cause: Multiple certificates were present in the certificate store.
Action: No Action.

Level: 1

Type: WARNING

Impact: Other

STS-12010: Previous RequestHandlerMapping is replaced with the new RequestHandlerMapping for URL {0}.
Cause: New RequestHandlerMapping was found for this URL.
Action: No Action.

Level: 1

Type: WARNING

Impact: Other

STS-12011: Previous ResponseHandlerMapping is replaced with the new ResponseHandlerMapping for URL {0}.
Cause: New ResponseHandlerMapping was found for this URL.
Action: No Action.

Level: 1

Type: WARNING

Impact: Other

STS-12012: Unsupported type for attribute value {0}, type={1}
Cause: One of the retrieved values for the attribute was of an unsupported type.
Action: No Action.

Level: 1

Type: WARNING

Impact: Other

STS-12013: Discovery Create Exception: unable to create object in the repository: {0}
Cause: Unable to create a data object in the repository.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12014: Discovery Finder Exception: unable to locate object in the repository: {0}
Cause: Unable to locate a data object in the repository.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12017: Communication Exception: unable to communicate with directory or naming service: {0}
Cause: Could not communicate with directory or naming service.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12018: Duplicate Entry Exception: duplicate entry in the data store: {0}
Cause: There was a duplicate entry in the data store.
Action: Check the data store for duplicate entries.

Level: 1

Type: ERROR

Impact: Other

STS-12019: Transformer Exception: unable to transform message to or from XML: {0}
Cause: There was a problem transforming the message to or from XML.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12026: No Such Algorithm Exception: cryptographic algorithm was not recognized: {0}
Cause: JCE provider was incorrectly configured.
Action: Check that the JCE provider is configured correctly.

Level: 1

Type: ERROR

Impact: Other

STS-12028: Notification Processing Exception: could not call the notifier: {0}.
Cause: Could not process the notification.
Action: Please check any plugins or listeners, or contact Oracle Support Services to rectify the issue.

Level: 1

Type: ERROR

Impact: Other

STS-12029: Attribute Processing Exception: error when processing attributes for mapping and filtering: {0}
Cause: Could not process attributes for mapping and filtering.
Action: Check the configuration for assertion attribute mapping and filtering.

Level: 1

Type: ERROR

Impact: Other

STS-12030: IOException: {0}
Cause: There was an error during Input/Output an operation.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12031: NamingException: error while interacting with an LDAP server or JNDI module
Cause: There was an error during interaction with an LDAP or JNDI module
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12032: InterruptedException: thread interrupt occurred during sleep() {0}
Cause: Thread interrupt occurred during sleep() method.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: WARNING

Impact: Other

STS-12033: Invocation Target Exception: error while invoking method {0}
Cause: There was an error while invoking a method.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: ERROR

Impact: Other

STS-12034: No Such Method Exception: a particular method could not be found {0}
Cause: There was an error while finding a method.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: ERROR

Impact: Other

STS-12036: Persistence Exception: error while creating or modifying data in the backend store {0}
Cause: Could not create or modify data in the backend store.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12040: Unsupported Encoding Exception: {0}
Cause: The specified character encoding was not supported.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12041: Unknown Provider Exception: {0}
Cause: The specified peer provider was not known.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12043: Discovery Registration Exception: {0}
Cause: An error occurred while registering a Discovery Provider.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12044: No Such Discovery Provider Exception: {0}
Cause: Could not find the specified Discovery Provider.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12045: Parser Configuration Exception: {0}
Cause: An error occurred while parsing an XML document.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12046: Parser Configuration Exception: {0}
Cause: An error occurred while parsing.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12047: SAX Exception: {0}
Cause: An error occurred while handling XML documents.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12048: SOAP Exception: {0}
Cause: An error occurred while handling SOAP messages.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12049: Event Exception: {0}
Cause: An error occurred while processing an Event.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12050: Action Listener Init Exception: {0}
Cause: An error occurred during Action Listener initialization.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12051: Mapping Exception: {0}
Cause: An error occurred while accessing handler mappings.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12052: No Such Target Exception: {0}
Cause: An error occurred while setting up handler mappings.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12053: SAX Parse Exception: {0}
Cause: An error occurred while parsing an XML document.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12054: Malformed URL Exception: {0}
Cause: Either no legal protocol could be found in a specification string or the string could not be parsed.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12055: No Such Mapping Exception: {0}
Cause: Could not find the handler mapping.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12056: Class Not Found Exception: {0}
Cause: Tried to load class with specified name but could not find definition for such class.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12057: Instantiation Exception: {0}
Cause: Tried to load an interface or an abstract class.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12058: Illegal Access Exception: {0}
Cause: Tried to use a field, method, or constructor using reflection, whose definition is not accessible.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12059: Action Registry Exception: {0}
Cause: An error occurred while registering Action Listener.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12060: Service Locator Exception: {0}
Cause: Could not allocate Service Locator.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12061: Algorithm Identifier Exception: {0}
Cause: Inappropriate or unsupported parameters were provided to an algorithm, or an unknown algorithm was requested.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12062: Audit Exception: {0}
Cause: An error occurred while auditing an event.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12063: OPSS Exception: {0}
Cause: An error occurred while using Oracle Platform Security Services libraries.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12064: Exception: {0}
Cause: An error occurred.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12065: Target Exception: {0}
Cause: An error occurred while handling the Target of a Servlet handler.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12066: Servlet Exception: {0}
Cause: An error occurred while initializing or using Servlet.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12067: An HTTP error occurred during SOAP Exchange.
Cause: An HTTP error occurred in SOAP Exchange.
Action: Check Oracle Secure Token Service logs for HTTP error code.

Level: 1

Type: ERROR

Impact: Other

STS-12069: Length of input exceeds maximum.
Cause: Length of input exceeds maximum allowed length.
Action: Check that the incoming request is correctly formatted.

Level: 1

Type: ERROR

Impact: Other

STS-12070: No HTTP Message Sender Created
Cause: Could not create the http message sender.
Action: Check the Oracle Secure Token Service logs for more specific information. Check that http client jar is in the classpath.

Level: 1

Type: ERROR

Impact: Other

STS-12071: A Directory error occurred
Cause: An error occurred while interacting with the Identity Provider module
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12072: WSDLException: {0}
Cause: There was an error during wsdl operation.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12073: PortabilityLayerException: {0}
Cause: An exception occurred during reloading of endpoint
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12074: PrivilegedActionException: {0}
Cause: PrivilegedExceptionAction while validating Kerberos Token
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12075: LoginException: {0}
Cause: A LoginException occurred while validating kerberos token
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12076: SmeSessionTimeOutException: {0}
Cause: SME session timed out
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12077: Illegal Argument Exception: {0}
Cause: The specified object argument is illegal
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12078: Library Exception: {0}
Cause: An exception occurred while creating library instance
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12079: ResponseHandlerException: {0}
Cause: An exception occurred for the response handler in the library instance
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

STS-12080: RequestHandlerException: {0}
Cause: An exception occurred for the request handler in the library instance
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Other

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-12503: Certificate Exception: {0}.
Cause: A certificate exception occurred, indicating a problem with one of the certificates.
Action: Check logs and exception message for more information.

Level: 1

Type: ERROR

Impact: Other

STS-12504: Invalid Algorithm Parameter Exception: {0}.
Cause: An invalid algorithm parameter exception occurred.
Action: Verify that the certificate or certificate path version is 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-12509: No Such Provider Exception: {0}.
Cause: A no such provider exception occurred.
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-12522: No value for required claim: {0}
Cause: No value in a required claim
Action: Check the message and logs for more details

Level: 1

Type: ERROR

Impact: Other

STS-12523: Crypto Exception: {0}.
Cause: A crypto exception has occurred during token issuance.
Action: Check logs and exception message 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: Custom token not correctly defined in configuration
Action: Check that the custom token is configured correctly in the server

Level: 1

Type: ERROR

Impact: Other

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-13003: Remove operation not supported.
Cause: The Iterator method remove() was invoked, but is not supported by the implementation.
Action: Replace the remove operation with alternate remove option.

Level: 1

Type: ERROR

Impact: Programmatic

STS-13004: EntrySet operation not supported.
Cause: The SoftHashMap method entrySet() was invoked, but is not supported by the implementation.
Action: Replace the call to entrySet() with alternate option.

Level: 1

Type: ERROR

Impact: Programmatic

STS-13006: Internal Error: Unable to register {0} as a provider for {1}
Cause: Unable to register Discovery Provider.
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: ERROR

Impact: Programmatic

STS-13009: Cannot have an empty response name.
Cause: Response name was empty.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

STS-13010: Cannot locate class with root name of {0}
Cause: Could not locate class.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

STS-13011: Deregistering object failed.
Cause: Deregistered object does not match expected object.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

STS-13013: Internal Server Error
Cause: Internal Server Error
Action: Check the Oracle Secure Token Service logs for more specific information.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

STS-13014: Servlet cannot be configured.
Cause: Servlet configuration failed.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

STS-13017: Initializing {0}
Cause: An internal error has occurred.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

STS-15002: Cannot find User for UserID {0} in User Data Store.
Cause: The user ID was incorrect or the user record does not exist.
Action: Verify that the user ID is correct.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15040: SSL client certificate required to access SOAP service URL
Cause: No SSL Certificate was presented when accessing the SOAP service.
Action: Contact the client to notify that an SSL Certificate is required when accessing the SOAP service.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15046: Unexpected confirmation method: {0}
Cause: Oracle Secure Token Service did not recognize the specified confirmation.
Action: Check that the confirmation method included in the Assertion is valid.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15048: Unknown condition in assertion: {0}.
Cause: Oracle Secure Token Service did not recognize the specified condition.
Action: Check that the condition included in the assertion is valid.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15049: The contents of the SOAP request body are null. Closing the connection.
Cause: The Oracle Secure Token Service server encountered an error while trying to deserialize the incoming message.
Action: Check that the message is correctly formatted.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15052: A time value is invalid
Cause: A string was passed in as a time value that was in an invalid format.
Action: Verify that all of the time value attributes are in the correct format.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15053: Invalid major version number: {0}, expected version number: {1}
Cause: Major version did not match the protocol version.
Action: Verify that the major version matches the protocol version.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15054: Invalid minor version number: {0}, expected version number: {1}
Cause: Minor version did not match the protocol version.
Action: Verify that the minor version matches the protocol version.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15056: Invalid version number: {0}
Cause: The version format was incorrect.
Action: Verify that the version format is correct. Version should consist of a major part and a minor part separated by a period.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15057: Invalid version: {0}, majorVersion={1}, minorVersion={2}
Cause: Either the major or the minor version was negative.
Action: Verify that both the major and minor versions are non-negative.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15058: Error while processing the SOAP envelope.
Cause: Oracle Secure Token Service could not process the incoming SOAP envelope.
Action: Check that the SOAP envelope format is correct.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15060: Unknown message parameter: {0}
Cause: One of the message parameters was not recognized.
Action: Verify that all of the message parameter names are recognized by Oracle Secure Token Service.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15083: There is no value for a parameter.
Cause: Parameter was sent without a value.
Action: Ensure that the parameters are passed with valid value.

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15084: The response handler expects an event response that implements Target.
Cause: EventResponse object was not of the type Target.
Action: Pass EventResponse object of the type Target to the response handler.

Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

STS-15085: Throwing a runtime exception.
Cause: An internal error has occurred.
Action: Contact Oracle Support Services to rectify the issue.

Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

STS-15098: Unknown condition ignored: {0}.
Cause: Peer provider sent a message which contains unknown conditions in the message.
Action: Check with the peer provider.

Level: 1

Type: WARNING

Impact: Requests/Responses

STS-15131: Certificate was missing when trying to verify digital signature.
Cause: Certificate missing when trying to verify incoming signature.
Action: Verify that the requester specified its identity when making the request, either in the message or by authenticating to the Oracle Secure Token Service server via SSL or HTTP Basic Authentication

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15503: Token type is invalid, expecting token type {0}, but received token type {1}.
Cause: The token type received in was not the token type expected.
Action: Verify that the incoming xml message was correct.

Level: 1

Type: ERROR

Impact: Requests/Responses

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 instant 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

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-15529: User not authenticated
Cause: User could not be authenticated with the provided password
Action: Provide correct user in the Request token

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, 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

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15536: Certificate Validation failed for certificate {0}
Cause: The certificate could not be validated
Action: Check the certificate and/or add the necessary Trust Anchor

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15537: Requester could not be authenticated
Cause: WSS token validation failed
Action: Provide valid WSS token.

Level: 1

Type: ERROR

Impact: Requests/Responses

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-15539: The partner identified by {0} is unknown
Cause: The referenced entity is not a partner
Action: Create a partner entry if necessary

Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15540: The partner is not trusted: {0}
Cause: The partner is not marked as trusted
Action: Verify the configuration of the partner

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

STS-18003: Assertion is not signed.
Cause: The assertion was not signed.
Action: Verify that the assertion was signed.

Level: 1

Type: ERROR

Impact: Security

STS-18026: Error while reading the client SSL certificate
Cause: Client SSL certificate is corrupt.
Action: Obtain a new client SSL certificate.

Level: 1

Type: ERROR

Impact: Security

STS-18034: Untrusted server certificate chain.
Cause: Certificate Authority certification keystore in JRE did not contain the Certificate Authority certificate.
Action: Add the Certificate Authority certificate of the LDAP server to the Certificate Authority certs keystore of the JRE.

Level: 1

Type: ERROR

Impact: Security

STS-18041: Illegal UTF encoding
Cause: The UTF encoding was not supported.
Action: Verify the UTF encoding to be a valid one.

Level: 1

Type: ERROR

Impact: Security

STS-18047: Certificate {0} is replaced with the certificate {1}.
Cause: Old certificate was replaced with the newer one.
Action: Ensure correct certificate is uploaded for normal functioning of the Oracle federation server.

Level: 1

Type: WARNING

Impact: Security

STS-18048: The certificate corresponding to the private key is expired: {0}
Cause: The certificate was expired.
Action: Use the certificate with the correct validity period.

Level: 1

Type: WARNING

Impact: Security

STS-18049: Public key algorithm is not known:{0}.
Cause: Public key algorithm was unknown.
Action: Use the correct certificate with the correct public key algorithm.

Level: 1

Type: WARNING

Impact: Security

STS-18050: User is not authenticated.
Cause: User was not authenticated.
Action: Login to the server using the correct user.

Level: 1

Type: WARNING

Impact: Security

STS-18055: Unknown pseudo-random number generator configured. Using Java default.
Cause: Default pseudo-random number generator configured is unknown.
Action: No Action.

Level: 1

Type: NOTIFICATION

Impact: Security

STS-18073: An error occurred during a cryptographic operation: {0}
Cause: The Oracle Secure Token Service encountered an error while invoking the crypto engine for signature creation/verification, encryption/decryption operations.
Action: Check the logs for more detailed error messages, and correct the problem related to the error.

Level: 1

Type: ERROR

Impact: Security

STS-18074: Signature verification failed for provider ID {0}
Cause: The signature might be have been spoofed.
Action: Contact Administrator to verify

Level: 1

Type: ERROR

Impact: Security

STS-18075: Decryption operation failed for message sent by provider ID {0}
Cause: The message is not intended for Oracle Secure Token Service.
Action: Contact Administrator to verify

Level: 1

Type: ERROR

Impact: Security

STS-18076: Security services exception: {0}
Cause: An error occurred while verifying/signing/encrypting/decrypting a message.
Action: Please check previous log entries for more specific information.

Level: 1

Type: ERROR

Impact: Security

STS-18077: XML decryption error: EncryptedData element not found
Cause: The XML EncryptedData element was not found when trying to decrypt the incoming data.
Action: Check the message and contact the remote server administrator if necessary.

Level: 1

Type: ERROR

Impact: Security

STS-18078: XML decryption error: could not get the decryption secret key
Cause: The key to decrypt the EncryptedData element could not be retrieved.
Action: Check the message and contact the remote server administrator if necessary.

Level: 1

Type: ERROR

Impact: Security

STS-18080: Could not retrieve key from the key store. Please verify that the key password is equal to the key store password.
Cause: Invalid key or key password is not equal to the key store password.
Action: Verify that the key is valid and the key password is equal to the key store password.

Level: 1

Type: ERROR

Impact: Security

STS-20000: Cannot open the key store.
Cause: Invalid or unsupported key store, or incorrect password. During installation, this error is expected.
Action: Verify that password is correct and the store is a valid PKCS #12 PFX wallet or Java KeyStore file. During installation, this error can be ignored.

Level: 1

Type: ERROR

Impact: Session