WebSphere Process Server messages     Operating Systems: All supported

CWWSS

CWWSS0006W: The binding loader cannot load {0} from the repository. The file is a cell-level configuration file for Web services security.
Problem The system cannot load the cell-level ws-security.xml configuration file. The file might be corrupt, missing, or in the wrong location.
User response Verify that the configuration file exists. If the file is missing, copy the ws-security.xml file from the ${USER_INSTALL_ROOT}/config/templates directory.
CWWSS0007W: The binding loader cannot load {0} from the repository. The file is a server-level configuration file for Web services security.
Problem The system cannot load the server-level ws-security.xml configuration file. The file might be corrupt, missing, or in the wrong location.
User response Verify that the configuration file exists. If the file is missing, copy the ws-security.xml file from the ${USER_INSTALL_ROOT}/config/templates directory.
CWWSS0009W: The Application Server configuration utilities cannot load the resource file for the error messages. The exception is {0}
Problem The NLS message catalog might not exist, is corrupted, or exists in the wrong location. An error occurred when the Web services configuration utilities attempted to locate this bundle.
User response Verify that the message catalog exists in the correct location.
CWWSS0021E: The Application Server failed to load the {0} CollectionCertStore configuration. The exception is: {1}
Problem An attempt to load the collection certificate store failed. The provider of the collection certificate store might have a null value. The providor of the collection certificate store might not be configured. The collection might have a null value.
User response The CollectionCertStore configuration might be corrupted or missing. Verify that the collection certificate store is configured properly in the binding.
CWWSS0031E: The Application Server cannot retrieve the ContextManager class. The ContextManager class is null.
Problem The ContextManager class manages the state information for a request that is being processed. The code cannot access the ContextManager class for this message. Therefore, the code does not have access to this information.
User response No user action is required.
CWWSS0049E: The {0} CallbackHandler class does not support the {1} callback object.
Problem The CallbackHandler class does not support the specified Callback implementation.
User response Verify the configuration specifies the correct CallbackHandler class and that the class is implemented correctly.
CWWSS0111E: The SecurityTokenServiceAdmin MBean failed to start. The exception is {0}
Problem There is a problem with the java message beans that has prevented the SecurityTokenServiceAdmin MBean from activating. This message bean is used to perform a live refresh of the configuration of the Security Token Service.
User response There is no user action to correct this problem.
CWWSS0115W: The Application Server cannot parse the {0} value for the Nonce cache timeout. The default value of {1} seconds was used instead. The Nonce is a randomly generated value.
Problem The format for the value for the Nonce cache timeout is not an integer. The Nonce is a randomly generated value.
User response Change the value for the Nonce cache timeout to an integer. The Nonce cache timeout value is specified by the custom property com.ibm.wsspi.wssecurity.core.NonceCacheTimeout in the WS-Security bindings. The Nonce is a randomly generated value.
CWWSS0116W: The value of {0} seconds for the Nonce cache timeout is less than the minimum. The minimum value of {1} seconds was used instead. The Nonce is a randomly generated value.
Problem The specified value for the Nonce cache timeout is less than the minimum value that is required. The Nonce is a randomly generated value.
User response Change the value for the Nonce cache timeout to one within the valid range. The Nonce cache timeout value is specified by the custom property com.ibm.wsspi.wssecurity.core.NonceCacheTimeout in the WS-Security bindings. The Nonce is a randomly generated value.
CWWSS0117W: The Application Server cannot parse the {0} value for the Nonce max age. The default value of {1} seconds was used instead. The Nonce is a randomly generated value.
Problem The format for the value of the Nonce max age is not an integer. The Nonce is a randomly generated value.
User response Change the the value for the Nonce max age to an integer. The Nonce max age value is specified by the custom property com.ibm.wsspi.wssecurity.core.NonceMaxAge in the WS-Security bindings. The Nonce is a randomly generated value.
CWWSS0118W: The value of {0} seconds for the Nonce max age is not within the valid range of a minimum of {1} seconds and a maximum of {2} seconds. The minimum value of {3} seconds was used instead. The Nonce is a randomly generated value.
Problem The specified value for the Nonce max age is not within the valid range. The Nonce is a randomly generated value.
User response Change the value for the Nonce max age to one within the valid range. The Nonce max age value is specified by the custom property com.ibm.wsspi.wssecurity.core.NonceMaxAge in the WS-Security bindings. The Nonce is a randomly generated value.
CWWSS0119W: The value of {0} seconds for the Nonce clock skew is not within the valid range of a minimum of {1} seconds and a maximum of {2} seconds. The minimum value of {3} seconds was used instead. The Nonce is a randomly generated value.
Problem The specified value for the Nonce clock skew is not within the valid range. The Nonce is a randomly generated value.
User response Change the value for the Nonce clock skew to one within the valid range. The Nonce clock skew value is specified by the custom property com.ibm.wsspi.wssecurity.core.NonceClockSkew in the WS-Security bindings. The Nonce is a randomly generated value.
CWWSS0120W: The Application Server cannot parse the {0} value for the Nonce clock skew. The default value of {1} seconds was used instead. The Nonce is a randomly generated value.
Problem The format for the value of the Nonce clock skew is not an integer. The Nonce is a randomly generated value.
User response Change the value for the Nonce clock skew to an integer. The Nonce clock skew value is specified by the custom property com.ibm.wsspi.wssecurity.core.NonceClockSkew in the WS-Security bindings. The Nonce is a randomly generated value.
CWWSS0121E: The Nonce is null or of zero length. The Nonce is a randomly generated value.
Problem The value of the Nonce is either missing from the SOAP message or it was not encoded with a supported encoding type. The Nonce is a randomly generated value.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS0122E: The Nonce cache is null or is not initialized. The Nonce is a randomly generated value.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS0124W: The specified value of {0} for the Nonce cache size is less than the allowed minimum value of {1}. The default value of {2} is used. The Nonce is a randomly generated value.
Problem The specified Nonce cache size is less than the minimum value that is required. The Nonce is a randomly generated value.
User response Specify a cache size greater the minimum value. The Nonce cache size value can be specified by the custom property com.ibm.ws.wssecurity.config.token.BasicAuth.Nonce.cacheSize in the WS-Security bindings or the com.ibm.websphere.wssecurity.util.nonceCacheSize Java system property. The Nonce is a randomly generated value.
CWWSS0127W: The specified value of {0} for the Nonce length is less than the allowed minimum of {1}. The default of {2} is used. The Nonce is a randomly generated value.
Problem The specified Nonce length is less than the minimum value that is required. The Nonce is a randomly generated value.
User response Specify the Nonce length greater the minimum. The Nonce length value can be specified by the com.ibm.websphere.wssecurity.util.nonceLength Java system property. The Nonce is a randomly generated value.
CWWSS0130W: The {0} prompt CallbackHandler without specifying basic authentication information in the binding is not supported for an application running on the Application Server.
Problem The CallbackHandler with prompt behavior is not supported for applications running on the Application Server. If this is used in the Application Server, it might cause the Application Server to hang.
User response Use a CallbackHandler that is supported for the Application Server.
CWWSS0131E: The {0} CallbackHandler is not allowed to prompt on the Application Server.
Problem The CallbackHandler with prompt behavior is not supported for applications running on the Application Server. If this is used in the Application Server, it might cause the Application Server to hang.
User response Use a CallbackHandler that is supported for the Application Server.
CWWSS0133E: WSSecurityPlatformContextFactory.setServer() is already initialized.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS0139W: The timestamp timeout value of {0} seconds is less than the minimum. The minimum value of {1} seconds is used instead.
Problem The specified value for the timestamp timeout is less than the minimum value that is required.
User response Change the value for the timestamp timeout to one that is within the valid range. The timestamp timeout value is specified by the custom property com.ibm.wsspi.wssecurity.core.TimestampTimeout in the WS-Security bindings.
CWWSS0140W: The Application Server cannot parse the {0} value for the timestamp max age. The default value of {1} seconds was used instead.
Problem The format for the value of the timestamp max age is not an integer.
User response Change the value for the timestamp max age to an integer. The timestamp max age value is specified by the custom property com.ibm.wsspi.wssecurity.core.TimestampMaxAge in the WS-Security bindings.
CWWSS0141W: The value of {0} seconds for the timestamp max age is not within the valid range of a minimum of {1} seconds and a maximum of {2} seconds. The minimum value of {3} seconds was used instead.
Problem The specified value for the timestamp max age is not within the valid range.
User response Change the value for the timestamp max age to one within the valid range. The timestamp max age value is specified by the custom property com.ibm.wsspi.wssecurity.core.TimestampMaxAge in the WS-Security bindings.
CWWSS0142W: The value of {0} seconds for the timestamp clock skew is not within the valid range of a minimum of {1} seconds and a maximum of {2} seconds. The minimum value of {3} seconds was used instead.
Problem The specified value for the timestamp clock skew is not within the valid range.
User response Change the value for the timestamp clock skew to one within the valid range. The timestamp clock skew value is specified by the custom property com.ibm.wsspi.wssecurity.core.TimestampClockSkew in the WS-Security bindings.
CWWSS0143W: The Application Server cannot parse the {0} value for the timestamp clock skew. The default value of {1} seconds was used instead.
Problem The format of the value for the timestamp clock skew is not an integer.
User response Change the value for the timestamp clock skew to an integer. The timestamp clock skew value is specified by the custom property com.ibm.wsspi.wssecurity.core.TimestampClockSkew in the WS-Security bindings.
CWWSS0144W: The Application Server cannot parse the {0} value for the timestamp cache timeout. The default value of {1} seconds was used instead.
Problem The format of the value for the timestamp cache timeout is not an integer.
User response Change the value for the timestamp cache timeout to an integer. The timestamp cache timeout value is specified by the custom property com.ibm.wsspi.wssecurity.core.TimestampTimeout in the WS-Security bindings.
CWWSS0146E: The Application Server cannot add the {0} pluggable algorithm factory. Algorithm mapping is not supported when the Application Server is in FIPS mode.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS0153E: The callback handler encountered an unsupported callback.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS0155E: Retrieving the byte array representation of an X.509 Certificate caused a CertificateEncodingException. The exception is: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS0157W: The {0} algorithm is not supported by this version of the JDK. This algorithm will not be available to applications running on this JDK.
Problem The RSA-OAEP algorithm is only supported by JDK Version 1.5 and later.
User response If the application is not configured to use the RSA-OAEP algorithm, no action is required. If the application is configured to use the RSA-OAEP algorithm, change the Web services security binding configuration to use the http://www.w3.org/2001/04/xmlenc#rsa-1_5 algorithm instead.
CWWSS0158I: Hardware Crypto Acceleration is enabled: {0}
Problem This is for informational purposes only.
User response This is for informational purposes only.
CWWSS0166E: Global security must be enabled in order to use the Web services security token propagation feature.
Problem An attempt was made to use the Web services security token propagation feature, but global security was not enabled in the Application Server.
User response Enable global security in the Application Server.
CWWSS0168E: No WebSphere Credential (WSCredential) was found in the Lightweight Third-Party Authentication (LTPA) propagation token.
Problem A WebSphere Credential is expected in the Lightweight Third-Party Authentication (LTPA) propagation token and none is found.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS2500E: Failed to use hardware cryptographic provider and continue to process cryptographic operations using software provider.
Problem Cryptographic operations are processed using the software provider because the hardware cryptographic processing has failed.
User response Check the first failure data capture (FFDC) log file for error details and make sure the hardware cryptographic provider is properly configured.
CWWSS2501I: Hardware Cryptographic Acceleration is enabled.
Problem This message is for informational purposes only.
User response No action is required.
CWWSS2502I: Hardware key store is used.
Problem This message is for informational purposes only.
User response No action is required.
CWWSS5001E: There was no password specified for the {0} key store.
Problem A password is required to load the Java key store. This password does not exist in the binding.
User response Specify the key store password in the binding.
CWWSS5002E: The {0} key store cannot be opened because a FileNotFoundException error occurred.
Problem The key store path is incorrect, or the key store does not exist.
User response Verify the path to the key store in the binding does exist on the machine.
CWWSS5003E: The {0} key store cannot be read because an IOException error occurred.
Problem The I/O error could be caused by format problem with the data in the key store, no password is specified when required, or incorrect password is specified.
User response Verify that you specified the correct key store type and password in the binding.
CWWSS5004E: The {0} key store cannot be loaded, due to {1}: {2}
Problem The default provider does not support the key store type, the algorithm that is used to verify the key store integrity does not exist, or certificates in the key store cannot be loaded.
User response Use the iKeyman tool or keytool to create key store with the supported key store type. Refer to the information center for supported key store types.
CWWSS5007E: The {0} class cannot be located.
Problem The system cannot locate the Java class that you specified in the class path.
User response Verify that the class name is correct and exists in the appropriate class path.
CWWSS5008E: The {0} class cannot be instantiated.
Problem The class default constructor does not exist, or the class is one of the following class types: abstract, interface, array, primitive, or void, or other permission problem.
User response Verify that the class default constructor exists. Verify that you did not specify any of the following class types: abstract, interface, array, primitive, or void. Verify that you have the proper Java 2 Security permission or file system permission.
CWWSS5009E: The default constructor for the {0} class cannot be accessed.
Problem The class default constructor does not exist or not public.
User response Verify that the class public default constructor exists.
CWWSS5010E: The key store is invalid, exception: {0}. Verify the key store is properly setup and configured for the parameter to PKIXBuilderParameters.
Problem The key store file does not contain at least one trusted certificate entry or has not successfully initialized.
User response Verify that the key store file is correctly configured for the parameters that the PKIXBuilderParameters object specifies. Verify that the key store file contains at least one trusted certificate entry.
CWWSS5013E: The {0} class must be a subclass of {1} class.
Problem The instantiated class is not a subclass of the required class type.
User response Verify that the class implementation extends the required base class or implements the required interfaces.
CWWSS5016E: The provider does not support the {0} certificate store type.
Problem The certificate store type is not available or supported by the provider.
User response Verify that you specified a supported certificate store type.
CWWSS5017E: The {0} algorithm parameter is not valid.
Problem The specified initialization parameters for this certificate store are incorrect.
User response Verify that you specified the certificate store configuration in the binding correctly.
CWWSS5018E: The {0} provider does not exist. Error: {1}
Problem The specified provider is not configured.
User response Verify that you configured the specified provider correctly.
CWWSS5019E: The following X509 certificate file cannot be opened: {0}. Error: {1}
Problem The certificate file cannot be accessed because I/O errors occured.
User response Verify that you specified the correct certificate file path and the appropriate file system permissions.
CWWSS5020E: The X509 certificate cannot be created from the following X509 certificate file: {0}. Error: {1}
Problem The certificate file cannot be parsed.
User response Verify that the certificate file format is a supported certificate type.
CWWSS5042E: Two or more {0} elements exist.
Problem Multiple XML elements exist in the SOAP message, where only one XML element with a specific namespace is expected.
User response Verify that the SOAP message conforms to the standard specifications. If the error persists, then refer to the information center for further troubleshooting and support.
CWWSS5043E: One {0} element is required.
Problem The XML element with a specific namespace does not exist in the SOAP message.
User response Verify that the SOAP message conforms to the standard specifications. If the error persists, then refer to the information center for further troubleshooting and support.
CWWSS5046E: One or more {0} elements are required.
Problem One or more of the XML elements with a specific namespace do not exist in the SOAP message.
User response Verify that the SOAP message conforms to the standard specifications. If the error persists, then refer to the information center for further troubleshooting and support.
CWWSS5047E: {0}/@{1} attribute is required.
Problem The required attribute does not exist in the XML element.
User response Verify that the SOAP message conforms to the standard specifications. If the error persists, then refer to the information center for further troubleshooting and support.
CWWSS5048E: One of the {0} elements is required.
Problem None of required elements with the specific namespaces exist in the SOAP message.
User response Verify that the SOAP message conforms to the standard specifications. If the error persists, then refer to the information center for further troubleshooting and support.
CWWSS5082E: The {0} encoding is not supported.
Problem The encoding type that you requested is not supported.
User response Verify that you encoded the SOAP message with the supported encoding type.
CWWSS5083E: The ValueType attribute for the KeyIdentifier element cannot be found.
Problem The KeyIdentifier element requires the ValueType attribute, which cannot be found.
User response Verify that you specified the ValueType attribute for the KeyIdentifier element in the SOAP message.
CWWSS5114E: The EncryptedData element cannot be found however, the ({0}) element is found.
Problem The XML encryption process requires the EncryptedData element, which cannot be found.
User response Verify that you encrypted the SOAP message correctly using W3C XML encryption and Organization for the Advancement of Structured Information Standards (OASIS) Web service security specifications.
CWWSS5122E: The WS-Security configuration object cannot be created. Error: {0}
Problem Internal configuration files cannot be loaded.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5173E: The original fault is: {0}
Problem This message is a formatted version of a SOAP fault message.
User response Examine the formatted SOAP fault message, which will list the actual problem.
CWWSS5181E: The following certificate, which is owned by {0} with the {1} alias from the {2} keystore, has expired: {3}
Problem The certificate has expired.
User response Verify the expiration date of the certificate and obtain a valid new certificate.
CWWSS5182E: The Application Server cannot validate the certificate, which is owned by {0}, uses the {1} alias, and is located in the {2} keystore. The following exception occurred: {3}
Problem The certificate is invalid.
User response Verify that the certificate is a valid one and obtain a valid certificate if necessary.
CWWSS5185W: The Application Server cannot map the {0} distinguished name (DN) of the X.509 certificate to the security name. The following exception occurred: {1}
Problem The certificate could not be mapped to a valid user in the registry.
User response Verify that there is a valid user that corresponds to the Distinguished Name for this certificate in the registry. Either obtain a certificate that has a corresponding valid user in the registry, or assure that the Distinguished Name can map to a valid user in the registry.
CWWSS5187E: The Application Server cannot instantiate the {0} class. The following exception occurred: {1}
Problem An internal class could not be instantiated.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5189W: The certificate, which is owned by {0}, uses the {1} alias, and is located in the {2} keystore,expires in {3} days.
Problem A certificate is about to expire in the keystore.
User response Open the keystore and validate the expiration dates for all of the certificates in the keystore. Generate new certificates, if necessary.
CWWSS5190W: The {0} property contains the {1} value, which is a non-integer string value. The {2} default value has been used instead.
Problem The Application Server expects an integer value. However, the specified value is not an integer number.
User response Correct the value for the property so that it is an integer number.
CWWSS5193E: The nonce, which is a randomly generated value, has expired.
Problem The timestamp of the nonce is too old and has expired. The message might have taken too long to arrive, or there could be a time syncronization problem between client and server.
User response Ensure that the date, time, and time zone are synchronized for both the client and the server. If they are both syncronized, it will need to be determined why the message is taking so long to arrive.
CWWSS5195E: The Application Server cannot obtain the {0} algorithm from the {1} provider, which resulted in the following exception: {2}
Problem An implementation of the specified algorithm could not be obtained from the JCE provider.
User response Make sure that the JCE provider being used does provide the specified algorithm.
CWWSS5200E: The time stamp value that is associated with the nonce is not fresh. The current time on the server is {0}. The timestamp value for the nonce is {1}
Problem The clocks on the client and server might not be synchronized.
User response Ensure that the date, time, and time zone are synchronized for both the client and the server.
CWWSS5205E: The time stamp in the message has expired.
Problem The time stamp in the message is too old and has expired. The message might have taken too long to arrive, or there could be a time syncronization problem between client and server.
User response Ensure that the date, time, and time zone are synchronized for both the client and the server. If they are both syncronized, it will need to be determined why the message is taking so long to arrive.
CWWSS5206E: The time stamp is not fresh. The current time in the system is {0}. The creation time for the time stamp in the message is {1}.
Problem The clocks on the client and server might not be synchronized.
User response Ensure that the date, time, and time zone are synchronized for both the client and the server.
CWWSS5208E: The time stamp value occurs too far into the future.
Problem The clocks on the client and server might not be synchronized.
User response Ensure that the date, time, and time zone are synchronized for both the client and the server.
CWWSS5209E: The time stamp value for the nonce, which is a randomly generated value, occurs too far into the future.
Problem The clocks on the client and server might not be synchronized.
User response Ensure that the date, time, and time zone are synchronized for both the client and the server.
CWWSS5301E: The Application Server cannot resolve an entry with publicId={0} and systemId={1} values. The following exception occurred: {2}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5302E: The following file does not exist and can not be loaded: {0}.
Problem A configuration file is missing.
User response Verify that the configuration file is in the specified location.
CWWSS5303E: The Application Server cannot parse an input source. The following exception occurred: {0}
Problem There has been an error processing an XML file.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5310E: The Application Server cannot open the X.509 Certificate Revocation List (CRL) file, which is located in the following location: {0}. The following exception occurred: {1}
Problem A Certificate Revocation List file can not be found in the filesystem.
User response Verify that the file is located on the specified location.
CWWSS5311E: The Application Server cannot create an X.509 Certificate Revocation List (CRL) factory using the following CRL file: {0}. The following exception occurred: {1}
Problem There has been a problem creating a Certificate Revocation List from the CRL file.
User response Verify that the CRL file contents are correct.
CWWSS5312E: The Application Server cannot retrieve the {0} key from the {1} keystore. The following exception occurred: {2}
Problem The key could not be recovered. The password for recovering the key might be wrong.
User response Verify that the password to retrieve the key from the keystore is correct.
CWWSS5314E: missing storepass attribute {0} for KeyStore.
Problem storepass attribute required for KeyStore.
User response Verify the KeyStore:- storepass attribute in the binding is required.
CWWSS5320E: The Application Server cannot hex decode the nonce, which is a randomly generated value. The following exception occurred: {0}.
Problem There was a problem parsing a nonce value. The nonce in the message is in an incorrect format.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5321E: A duplicate nonce, which is a randomly generated value, has been found.
Problem A nonce value should be unique on each message. The current message has a nonce that has already been found in a previous message.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5322E: The Application Server cannot parse the time stamp value. The following exception occurred: {0}
Problem There has been a problem parsing a time stamp value found in the message. Could be timestamp is in an incorrect format.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5323E: The message has expired. The creation date for the time stamp was {0}. The expiration date for the time stamp was {1}. The current date on the server is {2}.
Problem The message arrived after the expiration time for the time stamp. The message might have taken too long to arrive, or there could be a time syncronization problem between client and server.
User response Ensure that the date, time, and time zone are synchronized for both the client and the server. If they are both syncronized, it will need to be determined why the message is taking so long to arrive.
CWWSS5324E: The {0} time stamp type is not supported. The expected type is {1}.
Problem A check for the time stamp type has determined that the type is not supported.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5325E: A null value is not allowed for the nonce. The Application Server expected the wsse:Nonce element.
Problem A nonce was expected in the message but it was not found.
User response Verify that the security policies and bindings for the application sending the message are configured so a nonce is added to its messages.
CWWSS5326E: A null value is not allowed for the timestamp. The Application Server expected the wsu:Timestamp element.
Problem A time stamp was expected in the message but it was not found.
User response Verify that the security policies and bindings for the application sending the message are configured so a time stamp is added to its messages.
CWWSS5327E: A null value is not allowed for the created time of the time stamp. The Application Server expected the wsu:Created element.
Problem The time stamp must have a wsu:Created element indicating the time of message creation.
User response A time stamp was expected for the UsernameToken when consuming the message. Check your bindings for the sending service and verify that they especify the use of a time stamp for the UsernameToken.
CWWSS5328E: The {0} identifier is used to identify multiple sections of the message.
Problem An identifier is used to uniquely label a section of a message. If more than one section have the same identifier, then it is impossible to associate the id to a unique section.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5350E: The following configuration is not valid: {0}
Problem The security configuration for this service is invalid.
User response Check that the specified policy and bindings for this service are correct.
CWWSS5352E: The {0} keyword is used, but it is unknown. The keyword is used in the following expression: {1}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5353E: Null is not allowed for the XPath expression in the {0} assertion.
Problem No XPath expression was specified on an XPath element in the specified assertion in the policy.
User response Verify that all XPath elements in the specified assertion in the policy contain valid XPath expressions.
CWWSS5354E: The {0} dialect value is unknown. This dialect value exists in the following configuration string: {1}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5357E: The {0} canonicalization method is not valid.
Problem An unsupported canonicalization method was specified. Possible causes are that the application security policy has specified an invalid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies.
User response Check the security policy for both server and client applications and insure that the Algorithm Suite assertions are valid and compatible.
CWWSS5358E: The {0} signature method is not valid.
Problem An unsupported signature method was specified. Possible causes are that the application security policy has specified an invalid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies.
User response Check the security policy for both server and client applications and insure that the Algorithm Suite assertions are valid and compatible.
CWWSS5360E: The {0} digest method is not valid.
Problem An unsupported digest method was specified. Possible causes are that the application security policy has specified an invalid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies.
User response Check the security policy for both server and client applications and insure that the Algorithm Suite assertions are valid and compatible.
CWWSS5361E: The {0} transform is not valid.
Problem An unsupported transform method was specified. Possible causes are that the application security policy has specified an invalid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies.
User response Check the security policy for both server and client applications and insure that the Algorithm Suite assertions are valid and compatible.
CWWSS5362E: The key information content consumer type is unknown. The current configuration of the key information content consumer is {0}.
Problem The key information content consumer type is unknown. A probable reason could be that there is an error in the key bindings.
User response Verify that key bindings for the application security bindings are correct.
CWWSS5363E: The {0} data encryption method is not valid.
Problem An unsupported encryption method was specified. Possible causes are that the application security policy has specified an invalid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies.
User response Check the security policy for both server and client applications and insure that the Algorithm Suite assertions are valid and compatible.
CWWSS5364E: The {0} key encryption method is not valid.
Problem An unsupported key encryption method was specified. Possible causes are that the application security policy has specified an invalid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies.
User response Check the security policy for both server and client applications and insure that the Algorithm Suite assertions are valid and compatible.
CWWSS5365E: The Caller identity for the Caller configuration is null. The caller configuration is: {0}
Problem The Caller configuration must have a JAAS configuration or a Caller identity. One of the two must be present. This might be a problem with the application security bindings.
User response Verify that the application security bindings are correct for Caller configuration.
CWWSS5366E: Configuration information about the signing key is missing. The current configuration for this signature consumer is: {0}.
Problem There is no configuration found for the signing key. There might be key bindings information missing in the application security bindings.
User response Verify that the key bindings configuration for signing key on the application security bindings are correct.
CWWSS5367E: No reference to any message parts can be found on the signing generator/consumer configuration. The current configuration for this signature consumer/generator is: {0}
Problem Reference to message parts are required in order to retrieve the signature algorithms from Policy. This could be an error in the bindings.
User response Verify that there are message parts to be signed on the application security bindings.
CWWSS5368E: A data encryption method is required in the configuration, but none was found. The current configuration for this encryption consumer is: {0}.
Problem There was no data encryption method found in the configuration. The Algorithm Suite assertion in the policy might not be valid.
User response Verify that a valid Algorithm Suite is specified in the application security policy.
CWWSS5369E: Configuration information about the encryption consumer key is missing. The current configuration for this encryption consumer is: {0}.
Problem There is no configuration found for the encryption consumer key. There might be key bindings information missing in the application security bindings.
User response Verify that the key bindings for the encryption consumer in the application security bindings are correct.
CWWSS5370E: No reference to any message parts can be be found on the encryption generator/consumer configuration. The current configuration for this encryption consumer/generator is: {0}
Problem Reference to message parts are required in order to retrieve the encryption algorithms from the policy. In this case there are none.
User response Verify that there are message parts to be encrypted in the application security bindings.
CWWSS5371E: The token consumer/generator configuration has a null class instance. The current token consumer/generator configuration string representation is {0}.
Problem A token consumer configuration must have a class instance. A probable reason could be that there is an error in the security bindings relating to security tokens.
User response Verify that the token/consumer generator binding information in the application security bindings are correct.
CWWSS5372E: The token consumer configuration has a null type. The current token consumer configuration string representation is {0}.
Problem A token consumer configuration must have a type. A probable reason could be that there is an error in the security bindings relating to security tokens.
User response Verify that the token consumer binding information in the application security bindings is correct.
CWWSS5373E: The key consumer configuration has a null content consumer list. The current key consumer configuration string representation is {0}.
Problem A key consumer configuration must have a content consumer list. A probable reason could be that there is an error in the key bindings configuration.
User response Verify that the key bindings configuration is correct for the application security bindings.
CWWSS5374E: The key information configuration has a null class instance. The current key information configuration string representation is {0}.
Problem A key information configuration must have a class instance. A probable reason could be that there is an error in the key bindings.
User response Verify that the key bindings configuration is correct for the application security bindings.
CWWSS5375E: The key information configuration has a null type. The current key information configuration string representation is {0}.
Problem A key information configuration must have a type. A probable reason could be that there is an error in the key bindings.
User response Verify that the key bindings information in the application security bindings are correct.
CWWSS5376E: The Application Server cannot find an XPath expression for the XPath transform.
Problem An XPath transform was specified in the signing information but an XPath expression was not provided.
User response Verify that the application bindings do provide an XPath expression in the signing information.
CWWSS5380E: Expecting TokenConsumer with QName: {1} received Unmatched QName: {0}.
Problem Invalid or Unexpected QName for the TokenConsumer.
User response Please verify that valid QName for the TokenConsumer is provided.
CWWSS5381E: Unable to resolve the expected reference: {0}.
Problem The expected reference is not available.
User response Please turn on trace to collect more debug information. Refer the infocenter to collect trace data.
CWWSS5382E: The trustanchor cannot be Null.
Problem trustanchor is not available.
User response Please verify that trustanchor information is provided in the binding.
CWWSS5386E: Missing a MessagePart that needs to be signed and/or encrypted.
Problem If there is one or more Nonce or timestamp that need to be signed, there needs to be a MessagePart that needs to be signed/encrypted as well.
User response Verify the policy if there is one or more Nonce or timestamp that need to be signed, there needs to be a MessagePart that needs to be signed/encrypted as well.
CWWSS5400E: algorithm attribute is required but found: {0}.
Problem Missing or incorrect algorithm attribute.
User response Verify the algorithm has been specified in the binding.
CWWSS5401E: factoryname is not available for the algorithm mapping configuration: {0}.
Problem One of the possible reasons be the Algorithm URI couldnot be mapped to the Algorithm Factory.
User response Verify the algorithm information in the binding.
CWWSS5402E: At least one AlgorithmURI is required: {0}.
Problem The Algorithm URI information could be missing or invalid in the binding.
User response Verify the Algorithm information in the binding.
CWWSS5403E: referenced message part is required: {0}.
Problem There is mismatch of referencing signed parts in policy and binding.
User response PartReference in SigningInfo is required to be referenced correctly in the policy and binding.
CWWSS5404E: DigestMethod is required: {0}.
Problem information for the signing algorithm is invalid or incomplete.
User response One of the places to verify is the binding, please ensure the algorithm provided is valid.
CWWSS5405E: At least one transform is required: {0} in the PartReference in SigningInfo.
Problem transform information for the signing algorithm is invalid or incomplete
User response Please verify transform information in the binding.
CWWSS5406E: Missing required MessageParts {0} for (Required)Integrity or (Required)Confidentiality.
Problem (Required)Integrity or (Required)Confidentiality: At least one MessagePart is required.
User response Please provide Required)Integrity or (Required)Confidentiality message part.
CWWSS5407E: Integrity or Confidentiality: Processing order MUST be zero or positive number: {0}.
Problem The order is negative or invalid value.
User response Verify the order is specified correctly in the binding. The order mentions how to process signature and encryption.
CWWSS5408E: MessageParts, Timestamp, or Nonce: dialect attribute is required: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5409E: MessageParts, Timestamp, or Nonce: keyword attribute is required: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5412E: missing type attribute {0} for KeyStore.
Problem type attribute required for KeyStore.
User response Verify the KeyStore:- type attribute in the binding is required.
CWWSS5413E: missing path attribute {0} for KeyStore.
Problem path attribute required for KeyStore.
User response Verify the KeyStore:- path attribute in the binding is required.
CWWSS5415E: alias attribute is required: {0} for Key.
Problem alias attribute required for Key.
User response Verify the Key:- alias attribute in the binding is required.
CWWSS5416E: name attribute is required: {0} for Key.
Problem name attribute required for Key.
User response Verify the Key:- name attribute in the binding is required.
CWWSS5417E: KeyStore: KeyStore referenced is not valid : {0}.
Problem Keystore reference is not valid.
User response Verify keystore is available, not corrupted and specified correctly in binding.
CWWSS5418E: KeyStore: KeyStore should have one of the following. Either KeyStoreRef attribute or storepass, path, type attributes.
Problem KeyStore doesnot have one of the following. Either KeyStoreRef attribute or storepass, path, type attributes.
User response Change the keystore element to have either KeyStoreRef or storepass,path,type attributes
CWWSS5419E: EncryptedParts, or SignedParts: Namespace attribute is required: {0}.
Problem When specifying a Header to be signed or encrypted, the Namespace attribute is required.
User response Specify the Namespace attribute for the Header on the EncryptedParts or SignedParts.
CWWSS5430E: Unexpected keyinfo {0} in Generator SigningInfo.
Problem Only one KeyInfo is required in Generator SigningInfo.
User response Verify the binding for the Signature Generators KeyInfo.
CWWSS5431E: Expecting only one KeyInfo in Generator EncryptionInfo but found: {0}.
Problem Only one KeyInfo is required in Generator EncryptionInfo.
User response Verify the binding for the Encryption Generators KeyInfo.
CWWSS5432E: error in instantiating the TokenGenerator: {0}.
Problem TokenGenerator classname and instance attribute is required.
User response Verify binding for correct TokenGenerator classname.
CWWSS5433E: ValueType is required: {0} for TokenGenerator.
Problem TokenGenerator ValueType attribute is required.
User response Verify binding for valueType of TokenGenerator.
CWWSS5434E: Missing classname attribute {0} in CallbackHandler.
Problem CallbackHandler classname attribute is required.
User response Verify the binding if the CallbackHandler className is valid.
CWWSS5435E: BasicAuth: User id is null, but user password is not null.
Problem BasicAuth: User id is null, but user password is not null.
User response Verify the User ID and password for the BasicAuth in the binding.
CWWSS5436E: Missing or invalid keyinfo in Generator - SigningInfo or EncryptionInfo: Only one KeyInfo is required found: {0}.
Problem Generator SigningInfo or EncryptionInfo: Only one KeyInfo is required.
User response Please verify the binding for keyinfo information.
CWWSS5437E: The combination of secret key algorithms [{0}] and the type of key information [{1}] is not allowed.
Problem The combination of secret key algorithms [{0}] and the type of key information [{1}] is not allowed.
User response Verify if the secret key algorithm information provided in policy and key information provided in binding are valid.
CWWSS5440W: There are no allowed transform algorithms defined.
Problem There are no allowed transform algorithms defined.
User response Please verify if the transform algorithm in binding and algorithmSuite in policy are valid.
CWWSS5441W: There are no allowed canonicalization algorithms defined.
Problem There are no allowed canonicalization algorithms defined.
User response Verify the algorithm attributes in binding and algorithmSuite in policy are valid.
CWWSS5442W: There are no allowed signature algorithms defined.
Problem There are no allowed signature algorithms defined.
User response Verify the algorithm attributes in binding and algorithmSuite in policy are valid.
CWWSS5443W: There are no allowed digest algorithms defined.
Problem There are no allowed digest algorithms defined.
User response Verify the algorithm attributes in binding and algorithmSuite in policy are valid.
CWWSS5444W: There are no allowed data encryption algorithms defined.
Problem There are no allowed data encryption algorithms defined.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5445W: There are no allowed key encryption algorithms defined.
Problem There are no allowed key encryption algorithms defined.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5450E: Null or empty is not allowed to the name of Integrity, Confidentiality, RequiredIntegrity, or RequiredConfidentiality.
Problem Null or empty is not allowed to the name of Integrity, Confidentiality, RequiredIntegrity, or RequiredConfidentiality.
User response Verify wsu:Id value is set valid for Integrity and Confidentiality in policy.
CWWSS5452E: Null or empty is not allowed to the name of SecurityToken or RequiredSecurityToken.
Problem Null or empty is not allowed to the name of SecurityToken or RequiredSecurityToken.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5453E: AddCreateTimestamp/@expires has invalid format string: {0}
Problem AddCreateTimestamp/@expires has invalid format string.
User response Verify binding for valid timestamp format.
CWWSS5454E: Unable to find the default configuration.
Problem Unable to find the default configuration.
User response Verify default binding have not been modified, deleted or corrupted.
CWWSS5455E: Null or empty is not allowed to the name of TokenGenerator or TokenConsumer.
Problem Null or empty is not allowed to the name of TokenGenerator or TokenConsumer.
User response Verify the binding for valid name attribute for TokenGenerator and TokenConsumer.
CWWSS5457E: Null or empty is not allowed to the name of KeyInfo.
Problem Null or empty is not allowed to the name of KeyInfo.
User response Verify the binding for valid name attribute for KeyInfo.
CWWSS5458E: Missing TokenGenerator reference in the KeyInfo.
Problem Missing TokenGenerator reference in the KeyInfo.
User response Verify the binding for TokenGenerator reference in KeyInfo.
CWWSS5490E: Unsupported type of WS-Security factory: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5491E: Unable to obtain the object type {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5492E: Unsupported type of WS-Security component: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5493E: Unable to obtain the classpath used for instantiation for {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5494E: Unexpected error during the instantiation of {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5501E: All tokens in the message must be consumed.
Problem The message contained tokens that could not be consumed. This could be a problem with the token consumer bindings.
User response Verify that the token consumer bindings in the application security bindings are correct.
CWWSS5502E: The target element: {0} was not expected.
Problem The target element: {0} was not expected.
User response To get more information on the error, please turn on trace to collect more debug information. Refer the infocenter to collect trace data.
CWWSS5503E: Unknown child element {0} in the {1} parent element.
Problem Unexpected child element.
User response To get more information on the error, please turn on trace to collect more debug information. Refer the infocenter to collect trace data.
CWWSS5504E: The namespace URI {0} is diffrent than expected.
Problem Unexpected Namespace URI.
User response Verify the namespace URI is correct.
CWWSS5505E: There are different namespaceURIs for WS-Security {0}.
Problem There is mismatch of WS-Security Namespace URI versions.
User response Verify in binding approrpriate WS-Security Namespace URI versions are specified.
CWWSS5506E: All the attempts based on each SigningInfo failed. The last exception is {0}
Problem The provided SigningInfo is corrupted or invalid.
User response Verify SigningInfo information in the binding.
CWWSS5507E: All the attempts based on each EncryptionInfo failed. The last exception is {0}
Problem The provided EncryptionInfo is corrupted or invalid.
User response Verify EncryptionInfo information in the binding.
CWWSS5508E: All the attempts based on each TokenConsumer failed. The last exception is {0}
Problem The provided TokenConsumer is corrupted or invalid.
User response Verify TokenConsumer information in the binding.
CWWSS5509E: A security token whose type is [{0}] is required.
Problem Expected Security Token missing.
User response Verify the valuetype information of the Token in the binding.
CWWSS5510E: An exception occurred during the signature verification. The exception is {0}
Problem Error during signature verification.
User response For more information on error please turn on trace to collect more debug information. Refer the infocenter to collect trace data.
CWWSS5511E: An exception occurred during the decryption of a message. The exception is {0}
Problem Error during message decryption.
User response For more information on error please turn on trace to collect more debug information. Refer the infocenter to collect trace data.
CWWSS5512E: Unable to cast to the appropriate SecurityToken {0} into {1}.
Problem The securitytoken provided in policy or binding is not supported or valid.
User response Verify the Token information in the policy and binding.
CWWSS5514E: An exception while processing WS-Security message.
Problem An exception while processing WS-Security message.
User response Please turn on trace to collect more debug information. Refer the infocenter to collect trace data.
CWWSS5518W: Unable to obtain the X509 certificate from a token.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5519W: A valid X509 Certificate is not found in the token.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5520E: An exception occurred during token processing. The exception is: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5524W: The server cannot find the security header for a Web service with the actor: {0}
Problem The SOAP message might not have the security constraints defined, or the actor on the server and the client do not match.
User response Verify that the client has security configured for Web services and that the actor matches on both the client and the server.
CWWSS5525E: The server cannot find the security header for a Web service with no actor.
Problem The SOAP message might not have the security constraints defined, or the actor on the server and the client do not match.
User response Verify that the client has security configured for Web services and that the actor matches on both the client and the server.
CWWSS5526E: The server cannot find the security header for a Web service with the actor: {0}
Problem The SOAP message might not have the security constraints defined, or the actor on the server and the client do not match.
User response Verify that the client has security configured for Web services and that the actor matches on both the client and the server.
CWWSS5527E: The response message did not contain the expected Value attribute on the signature confirmation element.
Problem The RequireSignatureConfirmation policy assertion might not be specified in the policies for the client or the server.
User response Verify that the RequireSignatureConfirmation policy assertion has been specified in the policies for both the client and the server.
CWWSS5528E: The signature confirmation value on the response does not match a signature value from the request.
Problem The RequireSignatureConfirmation policy assertion might not be specified in the policies for the client or the server.
User response Verify that the RequireSignatureConfirmation policy assertion has been specified in the policies for both the client and the server.
CWWSS5529E: Expected {0} signature confirmation elements in the response and found {1}.
Problem The RequireSignatureConfirmation policy assertion might not be specified in the policies for the client or the server.
User response Verify that the RequireSignatureConfirmation policy assertion has been specified in the policies for both the client and the server.
CWWSS5530E: The response message did not contain the expected signature confirmation element with no Value attribute.
Problem The RequireSignatureConfirmation policy assertion might not be specified in the policies for the client or the server.
User response Verify that the RequireSignatureConfirmation policy assertion has been specified in the policies for both the client and the server.
CWWSS5531E: An EncryptedHeader element with mustUnderstand equal 1 was misunderstood while processing the security header for a Web service.
Problem An EncryptedHeader element with mustUnderstand equal 1 was not decrypted while processing the security header for a Web service.
User response Verify that the EncryptedHeader element was targeted to the correct role or actor.
CWWSS5532W: A SignatureConfirmation element found, but it is not required. It will not be verified. This might be a configuration error.
Problem The RequireSignatureConfirmation policy assertion might be specified in the service policy but not in the client policy.
User response Verify that the RequireSignatureConfirmation policy assertion is not needed in the client policy.
CWWSS5550E: Unable to obtain the message context.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5552E: Found an unexpected element as the parent element: {0}. Expected the {1} element with a supported namespace.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5553E: The message cannot be generated. Unexpected configuration found: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5554E: Unknown version of the SOAP specification: versionId={0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5555E: The mustUnderstand attribute on the Security header does not have the required value: existing value={0}, required value={1}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5556E: A Timestamp element was not found. Cannot move the Timestamp element.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5557E: More than one parent elements exists. Cannot move the Timestamp element.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5600E: Required DataReference/@URI attribute was not specified.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5601E: The following exception occured while decrypting the message: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5602E: The EncryptedKey/EncryptionMethod {0} not found.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5603E: Null is not allowed as the target element. An enc:EncryptedKey or enc:ReferenceList element was expected when decrypting the message.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5604W: An exception occurred while decrypting an EncryptedHeader that had a mustUnderstand attribute not equal to true.
Problem The EncryptedHeader was not processed because of the exception. Because the mustUnderstand attribute was not equal to true, processing of the message was allowed to continue.
User response No action is required.
CWWSS5610E: Unable to create the {0} element. The exception is: {1}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5611E: Generating the key for data encryption produced the following exception: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5612E: Encrypting the data produced the following exception: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5613E: Encrypting the key for data encryption produced the following exception: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5614E: Constructing the EncryptionMethod element produced the following exception: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5615E: Null is not allowed as the parent element of the enc:EncryptedKey or the enc:EncryptedData element.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5620E: Signature verification failed: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5621E: There is an unsupported signed part: URI={0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5624E: Null is not allowed as the target element. The {0} element was expected when consuming the message.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5625E: All the attempts based on each Reference failed. The last exception is: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5630E: Null is not allowed for the type when selecting elements.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5631E: The {0} type is not supported when selecting elements.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5632E: The {0} value is not supported when selecting elements.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5633E: Constructing the Signature element produced the following exception: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5634E: Signing the message produced the following exception: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5635E: Null is not allowed as the parent element of the {0} element.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5640E: A Timestamp header could not be added to the message when processing security for a Web service because a Timestamp header already existed.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5641E: More than one Timestamp element was found. Cannot move the Timestamp.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5660E: All the attempts based on each KeyInfoConsumer failed. The last exception is: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5670E: Null is not allowed for the canonicalization method during the processing of the STR-Transform.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5671E: There was an unknown canonicalization method: {0}, during the processing of the STR-Transform.
Problem The AlgorithmSuite specified in the client policy and the server policy might not be compatible.
User response Verify that the AlgorithmSuite specified in the client policy and the server policy are compatible.
CWWSS5672E: Null is not allowed for the ID resolver during the processing of the STR-Transform.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5673E: There was an unsupported type of URI: {0}, during the processing of the STR-Transform.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5674E: The processing of the STR-Transform failed.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5680E: Tranforming the XPath expression {0} produced the following exception: {1}
Problem The specified XPath expression was not properly formed.
User response Correct the XPath expression in the policy.
CWWSS5685E: The required Header/@Namespace attribute was not specified.
Problem The Header/@Namespace attribute is required. The Header/@Name attribute is optional.
User response Verify that the Header/@Namespace is specified correctly in the policy.
CWWSS5695E: The encrypting data object must contain the timestamp or nonce: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5696E: Null is not allowed as the node.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5697E: Null is not allowed as the value when selecting elements.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5700E: There is no wsu:Timestamp to be moved.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS5710E: A required message part [{0}] is not encrypted.
Problem The policy expected the specified message part to be encrypted.
User response Verify that the policies on both the client and the server specify the same EncryptedParts and EncryptedElements.
CWWSS5720E: A required message part [{0}] is not signed.
Problem The policy expected the specified message part to be signed.
User response Verify that the policies on both the client and the server specify the same SignedParts and SignedElements.
CWWSS5721E: A required nonce is not found in the message part [{0}].
Problem The policy expected the specified message part to contain a Nonce element, which is a randomly generated value.
User response Verify that the policies on both the client and the server specify that a Nonce is required for the specified message part.
CWWSS5730E: A required timestamp is not found.
Problem The policy expected a Timestamp header to be found in the message.
User response Verify that the policies on both the client and the server specify that a Timestamp is required on the message.
CWWSS5731E: A required timestamp is not found in the message part [{0}].
Problem The policy expected the specified message part to contain a Timestamp element.
User response Verify that the policies on both the client and the server specify that a Timestamp is required for the specified message part.
CWWSS5800E: The KeyStoreRef attribute for the configured key store is not valid.
Problem The KeyStoreRef attribute name must be valid.
User response Verify that the KeyStoreRef attribute exists in the binding and valid.
CWWSS6000E: The configuration for the KeyInfo was not obtained.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6001E: Key object was not obtained.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6002E: The KeyInfo type {0} is not valid. The Key object was not obtained.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6012E: All the attempts to resolve the key based on each Key Information failed. The last exception is: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6013E: The KeyInfo type is UNKNOWN.
Problem KeyInfo specified in the bindings probably is not valid.
User response Check the bindings
CWWSS6014E: The Reference Element was not processed.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6015E: The KeyIdentifier Element was not processed.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6016E: The Embedded Element was not processed.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6017E: The Key extraction fails because of an exception occurred during the key extraction. The exception is: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6020E: The TokenGenerator object is not obtained.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6031E: The Reference Element was not processed.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6032E: The URI attribute is not found.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6040E: TokenConsumer object is not obtained.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6042E: The Id attribute is not found.
Problem The Embedded key id is missing
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6052E: The EncodingType attribute is not found.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6054E: The IdentifierType attribute is not found
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6060E: The KeyName Element was not processed.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6081E: The X509Data Element was not processed.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6092E: Unknown key usage type: key type={0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6093E: Invalid algorithm for Identifier generation.
Problem KeyIdentifier element does not have the correct Algorithm specified
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6094E: A null value is not allowed in the value type field.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6095E: Value type must be {0}, but {1} is found.
Problem bindings have the information related to Value Type of the token
User response Check the Value Type of the token configuration in the bindings
CWWSS6096E: An Exception occured during the generation of the Key Identifier.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6500E: There is no caller identity candidate that can be used to login.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6501E: There is no trusted identity candidate that can be used.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6502E: The token that is used to specify the caller identity or trusted identity cannot be null.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6503E: There are more than one candidates used to specify the trusted identifier. Only one trust identifier is expected
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6504E: There are more than one candidates used to specify the caller identifier. Only one caller identifier is expected
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6510E: The following login failure occured : {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6513E: The Principal already exists in the subject.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6514E: Public Credentials already exist in the subject.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6515E: Private Credentials already exist in the subject.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6520E: An Exception occured during the construction of the login context
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6521E: The Login failed because of an exception
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6525E: The {0} callback handler instantiation failed
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6526E: The callback handler {0} cannot handle the callbacks correctly.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6527E: Unable to find the processing result of the login module: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6540E: A subject in the context is null.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6541E: The instance of ContextManager was not obtained.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6542E: The caller subject was not obtained from the ContextManager.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6543E: The invocation subject was not obtained from the ContextManager.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6544E: The caller subject was not set correctly to the ContextManager.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6545E: The invocation subject was not set correctly to the ContextManager.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6620E: An exception occured during the handling of a Public Key Infrastructure (PKI) path.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6621E: Decoding the binary token data that is sent in the message resulted in null.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6630E: An exception occured during the handling a Public Key Cryptograpgy Standards (PKCS7) object.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6650E: Failed to handle the callback handler and the reason is : [{0}]
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6711W: Default KeyInfoContentConsumer element is not defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6712W: Default TokenConsumer element is not defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6713W: Java Authentication and Authorization Service (JAAS) configuration is not defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6714W: Default KeyLocator element is not defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6715W: Default KeyInfoContentGenerator element is not defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6716W: Default TokenGenerator element is not defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6717W: Default CallbackHandler element is not defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6718E: Namespace value used to get the Qualified Name (QName) is null.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6719E: The Qualified Name (QName) {0} was not found.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6731E: The Application Server cannot load the keystore with the reference {0}. The following exception occurred: {1}
Problem A keystore with the specified reference could not be loaded.
User response Verify that the keystore reference in the bindings is correct.
CWWSS6733E: Multiple namespaces exist in the Web Services Addressing (WS-Addressing) headers.
Problem Multiple conflicting Web Services Addressing (WS-Addressing) namespaces in the SOAP message.
User response Make sure the correct and supported WS-Addressing namespace is used.
CWWSS6734E: The generator or consumer configuration for Web services security is missing from message.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6735E: The user registry or login is unable to validate the {0} . {1}
Problem It might be that the user is not included in token, or the user is not in user registry, or the token could not be validated.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6736E: The Application Server cannot load the keystore with reference {0}.
Problem A keystore with the specified reference could not be loaded.
User response Verify that the keystore reference in the bindings is correct.
CWWSS6800E: The entry with alias {0} of keystore {1} cannot be found: {2}
Problem The specified key alias is not in keystore.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6801E: The {0} encoded key is unknown.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6802E: The {0} causes integer overflow.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6803E: The 0x{0} is not a BIT STRING.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6804E: The {0} identifier type is unknown.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6805E: The certificate owned by {0} has expired: {1}
Problem The certificate is expired.
User response Please check keystore, and make sure certificate is not expired.
CWWSS6806E: An exception occurs while validating the certificate owned by {0}: {1}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6808E: There is no X509 certificate in request message.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6809E: The X509 certificate owned by {0}, which is created from the binary in the message is different from the X509 certificate owned by {1}, which is acquired from the keystore Path: {2}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6810E: The runtime can not identify the key corresponding to the identifier [{0}].
Problem The keystore configuration used by key locator is not defined in the consumer side.
User response Please check binding file.
CWWSS6811E: The key identifier {0} retrieved from the message is different from the key identifier {1} acquired from the keystore Path: {2}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6812E: The key name {0} retrieved from the message is different from the key name {1} acquired from the keystore Path: {2}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6813E: The issuer name {0} retrieved from the message is different from the issuer name {1} acquired from the keystore Path: {2}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6815E: The {0} token generator that refers to the security token in the policy is used for signature. The security token should be used for stand-alone tokens.
Problem The security token should be used for stand-alone tokens.
User response Please check binding file.
CWWSS6816E: The {0} token generator that refers to the security token in the policy is used for encryption. The security token should be used for stand-alone tokens.
Problem The security token should be used for stand-alone tokens.
User response Please check the binding file.
CWWSS6817E: The {0} security token with the {1} type does not have a matching token generator..
Problem The security token need a matching token generator.
User response Please check binding file for the security token type.
CWWSS6818E: The {0} security token does not have a token generator references.
Problem The Security token need a token generator reference.
User response Please check binding file for the security token type.
CWWSS6819E: The {0} security token with is the {1} type is required, but it does not have a matching token consumer.
Problem The security token type need define a matching token consumer.
User response Please check binding file for the security token type.
CWWSS6820E: The {0} security token does not have a token consumer references.
Problem The Security token need a token consumer reference.
User response Please check binding file for the security token type.
CWWSS6821E: The {0} token consumer that refers to the required security token in the policy is used for signature verification. Use the required security token for stand-alone tokens.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6822E: The {0} token consumer that refers to the required security token in the policy is used for decryption. Use the required security token for stand-alone tokens.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6823W: The configured Nonce cache size {0} is not a valid integer. Using default Nonce cache size {1}.
Problem Nonce cache size must be an integer.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6824W: The configured Nonce length {0} is not a valid integer. Using default Nonce length {1}.
Problem Nonce length must be an integer.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6825W: The {0} seconds value for the certificate cache timeout is less than the minimum. The minimum {1} seconds is used.
Problem The certificate cache timeout has a minimum value.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6826W: The {0} certificate cache size is less than the allowed minimum size {1}. The default {2} cache size is used.
Problem The certificate cache size is less than the allowed minimum size.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6827W: The certificate cache size {0} is not a valid integer. The default cache size {1} is used.
Problem Please use integer number as cache size.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6828W: The {0} seconds token cache timeout is less than the minimum. The minimum token cache timeout {1} seconds is used.
Problem The token cache timeout is less than the minimum.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6829W: The {0} token cache size is less than the allowed minimum {1}. The default token cache size {2} is used.
Problem The token cache size is less than the allowed minimum.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6830W: The token cache size {0} is not a valid integer. The default token cache size {1} is used.
Problem Please use integer value as cache size.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6831W: The {0} milliseconds token cushion is less than the minimum. The minimum token cushion {1} milliseconds is used.
Problem The token cushion is less than the minimum.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6832E: More than one wsse:Security elements to be processed.
Problem Only one wsse:Security element is allowed.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6833W: Unknown element {0} in the {1} element.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6834E: The Java Authentication and Authorization Service (JAAS) login configuration name is not defined in the configuration: {0}.
Problem JAAS login configuration name is not defined.
User response Please check binding file and security.xml file for JAAS login name.
CWWSS6836E: The certificate of initial sender is not in message.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6837E: The caller login failed. The exception is
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6838E: All caller login failed. The last exception is
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6840E: The certificate cache manager is not initialized on the Java 2 Platform, Enterprise Edition (J2EE) client side or the server side.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6841E: The AxisService class value is NULL. The Application Server cannot decide if the object is a service provider or requester.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6842E: The Application Server cannot validate the trusted identity because a list of trusted identities is not specified.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6843E: The following authentication result exists in the pool but it is not a candidate for the caller identity: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6844E: The following authentication result exists in the pool but it is not candidate for trusted identity: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6850E: The request is not valid or is malformed.
Problem The request might be missing required elements.
User response Refer to the information center for information on the request formats.
CWWSS6851E: Authentication failed.
Problem The request does not meet the authentication requirements.
User response Refer to the configuration files for the authentication requirements.
CWWSS6852E: The specified request failed.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6853E: Security token has been revoked.
Problem The security token is not valid.
User response Obtain a new security token.
CWWSS6854E: The digest elements are not sufficient.
Problem The request is missing some of the required authentication information.
User response Refer to the information center for information on the authentication requirements.
CWWSS6855E: The specified RequestSecurityToken token is not understood.
Problem The Application Server cannot process the request because elements exist that are not understood.
User response Refer to the information center for information on the request formats.
CWWSS6856E: The request data is out of date.
Problem The data in the request has expired.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6857E: The requested time range is not valid or not supported.
Problem The Application Server cannot process the request because the requested time range is not valid or not supported.
User response Refer to the documentation or the configuration to determine the valid time ranges.
CWWSS6858E: The requested scope is not valid or not supported.
Problem The Application Server cannot process the request because the requested scope is not valid or not supported.
User response Refer to the documentation or the configuration to determine the valid scopes.
CWWSS6859E: A renewable security token has expired.
Problem The security token has expired.
User response Renew the security token.
CWWSS6860E: The requested renewal failed.
Problem The Application Server cannot renew the security token.
User response Obtain a new security token.
CWWSS6861E: The requested context elements are not sufficient or not supported.
Problem The context token does not contain the required information.
User response Refer to the information center for information on the required context information.
CWWSS6862E: Not all of the values that are associated with the security context token (SCT) are supported.
Problem Some of the values in the request that are associated with the security context token (SCT) are not supported.
User response Refer to the information center for information on the supported values.
CWWSS6863E: The specified source for the derivation is unknown.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS6864E: The provided context token has expired.
Problem The context token has expired.
User response If the token is renewable, renew the context token. Otherwise, obtain a new context token.
CWWSS6865E: The specified context token cannot be renewed.
Problem Some context tokens cannot be renewed.
User response Obtain a new context token.
CWWSS6901E: The Application Server cannot load the configuration file for the security token service.
Problem The configuration file for the security token service is needed for normal operation.
User response Verify that the file has not been moved or become corrupt.
CWWSS6902E: The Application Server cannot load the plugins configuration file for the security token service.
Problem The plugins configuration file for the security token service is needed for normal operation.
User response Verify that the file has not been moved or become corrupt.
CWWSS6903E: The Application Server cannot load the targets configuration file for the security token service.
Problem The targets configuration file for the security token service is needed for normal operation.
User response Verify that the file has not been moved or become corrupt.
CWWSS6904E: The Application Server cannot create Uniform Resource Identifiers (URI) for the security context token (SCT) type, the SCT get request type, or the SCT put request type.
Problem There is a syntax problem for the URIs specifying the SCT token type, the SCT get request, or the SCT put request type.
User response Verify that the install image has not been corrupted.
CWWSS6905W: The Application Server cannot create a mapping for the default token type.
Problem This issue causes errors for messages that are targeted for an unconfigured endpoint.
User response Verify that the configuration file for the security token service targets specifies a default token type.
CWWSS6906W: The Application Server cannot create the Uniform Resource Identifier (URI) for wildcard mapping.
Problem There is a syntax problem for the URI specifying the wildcard mapping.
User response Verify that the install image has not been corrupted.
CWWSS6907E: The Application Server failed to obtain the instance of the security token service.
Problem This instance of the security token service is required for normal operation.
User response Verify that the instance of the security token service exists.
CWWSS7001W: The builder.getDocumentElement method returns a null value.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7002W: The following parse error occurred: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7003E: The following argument in the JAXWSGenerationContextPutter.put(Object messageContext, Object wssGenerationContext) method has a null value: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7004E: The argument in the JAXWSGenerationContextRetriever.getWSSGeneratoinContext(Object object) method has a null value.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7005E: The argument in the OMStructure.isFeatureSupported(String feature) method has a null value.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7006E: The transform(Object obj) method in the following class has a null value: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7007E: The Application Server cannot obtain the class name from the generatorMap field.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7008E: The argument in the WSSGenerationContextImpl.generate(Object obj) method has a null value.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7009E: The argument in WSSTimestampImpl.setDuration(Duration time) method has a null value.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7010E: The Application Server cannot obtain a part from the partMap field.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7011E: The argument to the get factory method in the following class has a null value: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7012E: This method is unsupported in the current implementation: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7013E: PolicyInboundConfig(String bindFilename, String policyFilename, boolean isRequest, ClassLoader appClassLoader,WSSecurityDefaultConfiguration defaultConfiguration): [{0}]
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7014E: No WS-Security Bindings found.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7015E: Exception received from JAXB.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7016E: Exception received from FileInputStream.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7017E: Actor URI validation failed.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7018E: The policy assertion [{0}] is not a valid sign/encrypt part/element.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7019E: The policy assertion [{0}] is not a valid AsymmetricBinding QName assertion.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7020E: Initiator Token assertion found when an Initiator Encryption Token assertion was already defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7021E: Initiator Token assertion found when an Initiator Token assertion was already defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7022E: Recipient Token assertion found when a Recipient Encryption Token assertion was already defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7023E: Recipient Token assertion found when a Recipient Signature Token assertion was already defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7024E: Initiator Signature Token assertion found when an Initiator Token assertion was already defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7025E: Recipient Signature Token assertion found when a Recipient Token assertion was already defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7026E: Initiator Encryption Token assertion found when an Initiator Token assertion was already defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7027E: Recipient Encryption Token assertion found when a Recipient Token assertion was already defined.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7028E: The policy assertion [{0}] is not a valid SymmetricBinding QName assertion.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7029E: The policy assertion [{0}] is not a valid Supportingtoken QName assertion.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7030E: The policy assertion [{0}] is not a valid WSS10 QName assertion.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7031E: The policy assertion [{0}] is not a valid WSS11 QName assertion.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7032E: The policy assertion [{0}] is not a valid Trust10 QName assertion.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7033E: An exception was caught formatting the following LDAP port number: {0}
Problem The format of the LDAP port number is wrong.
User response Check the LDAP port number and make sure it is correct.
CWWSS7034W: Both Policy Set and WSSAPI configurations have been read. Policy Set configuration will override WSSAPI configuration.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7035E: [{0}] :: is not supported on Thinclient environment.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7036E: [{0}] :: is not supported on Websphere Server.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7037W: Token Assertion for token of type [{0}] not supported.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7038E: Unable to get ClientConfigurationFactory.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7039E: Unable to get ConfigurationContext.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7040E: Unable to get AxisConfiguration.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7041E: An exception has been caught while selecting an X509Certificate. The exception is [{0}]
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7042E: An invalid cryptographic algorithm has been specified . The requested algorithm was {0} and the caught exception is [{1}]
Problem The requested cryptographic algorithm is not available on this environment.
User response Specify an available cryptographic algorithm.
CWWSS7043E: An invalid algorithm parameter has been found. Specified parameters were: [{0}]
Problem An invalid parameter for a cryptographic algorithm has been found.
User response Check parameters and insure they are valid.
CWWSS7044E: No SCT found in the client side cache with uuid [{0}].
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7045E: Exception received while loading the web services security default bindings:
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7046E: Null returned from jaxb for the web services security default bindings.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7047E: No web services security default bindings were found.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7048E: Could not load ws-security.xml file.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7049E: Exception received while loading the web services security custom bindings:
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7050E: Null returned from jaxb for the web services security custom bindings.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7051E: No web services security custom bindings or default bindings were found.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7052E: Policy set not found for application.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7053W: No web services security custom bindings were found. Default bindings will be used.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7054E: Problem found while loading WSSecurity policy. Expected {0}, found {1}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7055E: Exception retrieved from PolicyTypeLoader:
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7056E: Policy set attachment type {0} not valid.
Problem Valid policy set attachment types are client, application, or system/trust.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7057E: No policy set attachment type found. Cannot determine if policy set is for client, application or system/trust.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7058E: Unable to process inbound SOAP message. Exception retrieved from PolicyTypeLoader:
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7059E: Unable to process inbound SOAP message. Unexpected object {0} in PolicyTypeBinding.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7060E: Unable to process outbound SOAP message. Exception retrieved from PolicyTypeLoader:
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7061E: Unable to process outbound SOAP message. Unexpected object {0} in PolicyTypeBinding.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7062E: Failed to check username [{0}] and password in the UserRegsitry: {1}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7063E: Failed to check username [{0}] in the UserRegsitry: {1}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7064E: Both KeyStore Reference and KeyStore Path are null.
Problem Incomplete keystore configuration was found, either KeyStore Reference or KeyStore Path must be specified, but not both at the same time.
User response Check the keystore configuration in the binding and make sure either KeyStore Reference or KeyStore Path is specified.
CWWSS7065W: Unable to instantiate the class {0}.
Problem The may be caused by instantiation of class that is an abstract class, an interface, an array class, a primitive type, or void, or the class has no default constructor, but could also be other reasons.
User response Make sure the class specified is not an abstract class, an interface, an array class, a primitive type, or void, and has default constructor.
CWWSS7066E: Certificate type {0} is not supported, exception: {1}
Problem This error is caused by the requested certificate type is not available from the JCE provider.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7067E: The Security Context Token is not canceled. The exception is:
Problem The AxisService from the BindingProvider object may not be correct for this Security Context Token.
User response Make sure the BindingProvider object specified on the cancel operation is correct.
CWWSS7068E: The Securtiy Context Token is expired and is not renewable.
Problem The Security Context Token is not renewable after expiration.
User response Make sure the renewableAfterExpiration property is set to true in the security token service (STS) configuration if the desired behavior is to renew the Security Context Token after expiration.
CWWSS7069E: Cannot get valid Lifetime information for Security Context Token.
Problem Either the createdDate or expiredDate is null. Both createdDate and expiredDate are required when renewing a Security Context Token.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7070E: The Security Context Token is not renewable. The exception is:
Problem The Security Context Token could not be renewed because an exception was received.
User response Make sure the security token service (STS) is configured to allow the Security Context Token to be renewed. Also check that the WSSGenerationContext and WSSConsumingContext specified on the renew operation are correct.
CWWSS7071E: The Security Context Token is not validated. The exception is:
Problem The Security Context Token could not be validated because an exception was received.
User response Make sure the security token service (STS) is configured correctly, and that the WSSGenerationContext and WSSConsumingContext specified on the validate operation are correct.
CWWSS7072E: The Securtiy Context Token is expired and is not renewable.
Problem The Security Context Token is not renewable after expiration.
User response Make sure the renewableAfterExpiration property is set to true in the security token service (STS) configuration if the desired behavior is to renew the Security Context Token after expiration.
CWWSS7073E: The key is not retrieved. The exception is:
Problem The encrypting key or signing key could not be retrieved from the security token. Either an exception occurred or null was returned.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7074E: The key is not retrieved. The exception is:
Problem The decrypting key or verifying key could not be retrieved from the security token because an exception was received.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7075E: The duration is invalid.
Problem The default duration for the timestamp for WSS APIs does not have a valid format. This value is defined in the web services security runtime.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7076E: {0} is not instantiated.
Problem A required class could not be instantiated.
User response If the class was specified for token generators or consumers, make sure the class name is correct and that the class is in the correct location.
CWWSS7077E: The login module name is null.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7078E: Nonce manager must not be accessed.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7079E: {0} is not instantiated.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7101E: No handler for request type: {0}
Problem The request type is not recognized.
User response Verify that the plugins configuration file contains the correct information.
CWWSS7102W: No custom property in the SCT plugin configuration is defined for the issue request type.
Problem A valid URI value for the issue request type must be present in the SCT configuration.
User response Verify that the SCT configuration file contains a valid URI for the custom property issueRequestTypeRST.
CWWSS7103W: No custom property in the SCT plugin configuration is defined for the cancel request type.
Problem A valid URI value for the cancel request type must be present in the SCT configuration.
User response Verify that the SCT configuration file contains a valid URI for the custom property cancelRequestTypeRST.
CWWSS7104W: No custom property in the SCT plugin configuration is defined for the renew request type.
Problem A valid URI value for the renew request type must be present in the SCT configuration.
User response Verify that the SCT configuration file contains a valid URI for the custom property renewRequestTypeRST.
CWWSS7105W: No custom property in the SCT plugin configuration is defined for the validate request type.
Problem A valid URI value for the validate request type must be present in the SCT configuration.
User response Verify that the SCT configuration file contains a valid URI for the custom property validateRequestTypeRST.
CWWSS7106E: The SCT issue request handler class is not initialized.
Problem The SCT handler classes must be initialized before use.
User response Refresh the Security Token Service or restart the server.
CWWSS7107W: The request is missing entropy information.
Problem Requests are required to contain Entropy and BinarySecret elements.
User response Refer to the documentation for acceptable issue request formats.
CWWSS7108E: The requested security context token cannot be issued due to cache failure.
Problem The attempt to cache the security context token failed.
User response Verify that the SCT configuration file contains the fully qualified name of an accessible token cache factory class under the property tokenCacheFactory.
CWWSS7109W: The URI for the WSC namespace could not be created. The exception is: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7110W: The specified cancel request is missing the CancelTarget element.
Problem Cancel requests must have the CancelTarget element, which specifies the UUID of the security context token to cancel.
User response Refer to the documentation for acceptable cancel request formats.
CWWSS7111W: Could not extract UUID from the CancelTarget element in the request.
Problem Failed to extract the UUID of the security context token from the CancelTarget element in the request. The UUID is needed to fulfill the cancel request.
User response Refer to the documentation for acceptable cancel request formats.
CWWSS7112E: The SCT renew request handler class is not initialized.
Problem The SCT handler classes must be initialized before use.
User response Refresh the Security Token Service or restart the server.
CWWSS7113W: The specified renew request is missing the RenewTarget element.
Problem Renew requests must have the RenewTarget element, which specifies the UUID of the security context token to renew.
User response Refer to the documentation for acceptable renew request formats.
CWWSS7114W: Could not extract UUID from the RenewTarget element in the request.
Problem Failed to extract the UUID of the security context token from the RenewTarget element in the request. The UUID is needed to fulfill the renew request.
User response Refer to the documentation for acceptable renew request formats.
CWWSS7115E: The algorithm and provider information is missing from the cached security context token.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7116W: The specified validate request is missing the ValidateTarget element.
Problem Validate requests must have the ValidateTarget element, which specifies the UUID of the security context token to validate.
User response Refer to the documentation for acceptable validate request formats.
CWWSS7117W: Could not extract UUID from the ValidateTarget element in the request.
Problem Failed to extract the UUID of the security context token from the ValidateTarget element in the request. The UUID is needed to fulfill the validate request.
User response Refer to the documentation for acceptable validate request formats.
CWWSS7118E: AxisConfiguration in MessageContext is null.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7119E: ConfigurationContext in MessageContext is null.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7120E: EndpointReference is null. WS-Address might be not enabled. It is required for Secure Conversation.
Problem WS-Address might not be enabled. It is required for Secure Conversation.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7121W: Failed to load WS-SecureConversation client cache configuration. Using default values.
Problem WS-SecureConversation client cache configuration file, WSSCCache.xml, could not be loaded by using JAXB.
User response Please verify the WSSCCache.xml is in Cell name directory. If WSSCCache.xml existed and problem still persists, please contact your service representative.
CWWSS7122W: Failed to create distributed SecurityContextToken cache.
Problem The request to using distributed SecurityContextToken cache could not be done. SecurityContextToken will be cached in local server only, and will not be distributed to all other cluster members.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7200E: Unable to create AxisService from ServiceEndpointAddress : {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7201E: Lifetime information of the Security Context Token is not valid
Problem Requested Security Token Response message does not have the valid life time information of the Security Context Token
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7202E: Issuing of Security Context Token fails. The exception is : {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7203E: Derived Key generation fails with an exception: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7204E: Derived key is not valid
Problem Might be due to a problem during the derived key generation
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7205E: Invalid Security Context Token
Problem Security Context Token is expired.
User response When using WSSAPIs, user can try to renew the token and retry the request
CWWSS7211E: Cannot find derived key token with id [{0}] in the subject
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7212E: Cannot verify security context token using the reference information from the derived key token element
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7213E: Unsupported Value Type. Expecting this [{0}], but found [{1}].
Problem The Value Type specified in the token configuration is not correct
User response Check and correct the Value Type information in the bindings for the token consumer configuration
CWWSS7214E: Cannot get valid security context token from the trust service
Problem The security context token might be expired or there is a problem retrieving the token from the trust service
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7215E: Cannot get valid security context token from the cache
Problem The security context token might be expired or the token does not exist in the cache
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7221I: Security context token is expired and is not renewable after expiration
Problem This is informational message only. Runtime will automatically request for a new SC token
User response Informational message
CWWSS7222E: Security context token lifetime is lower than the WS-SecureConversation client cache cushion
Problem Newly issued security context token should have more lifetime than the WS-SecureConversation client cache cushion
User response Either lower the client cache cushion setting or increase the lifetime of the security context token
CWWSS7223E: Renew of security context token fails with an exception : {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7224E: The serialized security token version is different from current token version.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7225E: The JAXB is unable to load WS-SecureConversation client cache configuration file. The exception is {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7226E: The AdminCommand could not find WS-SecureConversation client cache configuration file.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7227E: The AdminCommand could not find the property {0} in WS-SecureConversation client cache configuration file.
Problem The requested property is not in WS-SecureConversation client cache configuration file.
User response Please check WS-SecureConversation client cache configuration file.
CWWSS7228E: The AdminCommand could not update the WS-SecureConversation client cache configuration file. The exception is {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7229E: The AdminCommand {0} creation failed. The exception is {1}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7230E: The AdminCommand {0} loading failed. The exception is {1}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7231E: The WS-Security SelfManagedData serialization fails. The exception is {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7232E: The WS-Security SelfManagedData de-serialization fails. The exception is {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7233E: The security subject is not returned from login process.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWSS7234I: The SecurityContextToken is either invalidated or not renewable. Cancel request is not procsssed.
Problem This is information only.
User response No action is required.
CWWSS7235I: The specified SecurityContextToken could not be renewed. A new context token will be issued.
Problem This is information only.
User response No action is required.
CWWSS7236E: The {0} configuration file contains invalid settings.
Problem The Application Server encountered invalid settings while loading the configuration file.
User response Verify that the configuration files contain valid settings.
CWWSS7237E: The Application Server was unable to configure the security token service (STS).
Problem A problem was encountered when attempting to configure the STS.
User response Verify that the STS configuration files have not been corrupted or removed.
CWWSS7238E: The Application Server encountered the {0} token type, which is invalid for the {1} endpoint.
Problem The token type that was specified is not valid for the endpoint.
User response Verify that the token type is valid for the endpoint.
CWWSS7239E: The Application Server encountered an invalid Soap Envelope Body. The Soap Envelope Body must consist of exactly one RequestSecurityToken element.
Problem One possibility is that the RequestSecurityToken element was not present in the sent message. Another is that the soap message may not have been decrypted, because of an issue with the policy set.
User response Verify that the policy set is correct.
CWWSS7240E: The Application Server encountered multiple {0} elements in the token request.
Problem The element can only occur once in the token request.
User response Remove the extra elements from the token request and resubmit the request.
CWWSS7241E: The RequestSecurityToken element contains an invalid {0} element.
Problem The Application Server encountered an invalid element while processing the RequestSecurityToken.
User response Remove the invalid element from the RequestSecurityToken and resubmit the request.
CWWSS7242E: The RequestSecurityToken element is missing the required {0} header element.
Problem The Application Server could not successfully process the RequestSecurityToken because of a missing header element.
User response Specify the missing header element in the RequestSecurityToken and resubmit the request.
CWWSS7243E: The security token service (STS) must only return 1 response. It returned {0} responses.
Problem The Application Server encountered an incorrect number of responses from the STS.
User response No user action is required.
CWWSS7244E: The Application Server was unable to load the trust related policy set for the {0} resource.
Problem The trust related policy set for the resource failed to load.
User response Verify that the trust related policy set for the resource is correct.
CWWSS7245E: Order is a required attribute for encryption information on outbound bindings.
Problem The attached WS-PolicySet binding file is invalid.
User response Regenerate the binding file.
CWWSS7246E: Order is a required attribute for signing information on outbound bindings.
Problem The attached WS-PolicySet binding file is invalid.
User response Regenerate the binding file.
CWWSS7509W: The received SOAP request message is rejected because it does not correctly specify a SOAP action and a WS-Addressing action while there is at least one PolicySet attachment at operation level of the {0} service.
Problem The Web services security runtime cannot find correct SOAP action or correct WS-Addressing action to determine whether an operation level PolicySet must be used to validate the received message. The request message is therefore rejected due to security considerations.
User response Modify the Web services client so that the correct SOAP action or WS-Addressing action is specified in request messages.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.wssecurity.resources.wssmessages.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)