security.wssecurity.XPathElementSelector.s01=CWWSS5680E: Tranforming the XPath expression {0} produced the following exception: {1} The specified XPath expression was not properly formed. Correct the XPath expression in the policy. security.wssecurity.IdUtil.s01=CWWSS5328E: The {0} identifier is used to identify multiple sections of the message. 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. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC0166E=CWWSS0166E: Global security must be enabled in order to use the Web services security token propagation feature. An attempt was made to use the Web services security token propagation feature, but global security was not enabled in the Application Server. Enable global security in the Application Server. security.wssecurity.WSEC6718E=CWWSS6718E: Namespace value used to get the Qualified Name (QName) is null. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6826W=CWWSS6826W: The {0} certificate cache size is less than the allowed minimum size {1}. The default {2} cache size is used. The certificate cache size is less than the allowed minimum size. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6717W=CWWSS6717W: Default CallbackHandler element is not defined. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6825W=CWWSS6825W: The {0} seconds value for the certificate cache timeout is less than the minimum. The minimum {1} seconds is used. The certificate cache timeout has a minimum value. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.soapsecurityexception.orig.fault=CWWSS5173E: The original fault is: {0} This message is a formatted version of a SOAP fault message. Examine the formatted SOAP fault message, which will list the actual problem. security.wssecurity.WSEC6716W=CWWSS6716W: Default TokenGenerator element is not defined. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SCTGenerateLoginModule.issueSCT=CWWSS7202E: Issuing of Security Context Token fails. The exception is : {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6824W=CWWSS6824W: The configured Nonce length {0} is not a valid integer. Using default Nonce length {1}. Nonce length must be an integer. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.trust.client.wsanamespace=CWWSS7518E: Invalid WS-Addressing namespace [{0}]. The WS-Addressing namespace specified is not a valid namespace. Specify a WS-Addressing namespace that is supported by the trust client. security.wssecurity.CWWSS7566E=CWWSS7566E: The SecurityToken of type {0} must contain an OMElement representation. A SecurityToken was identified in the security header without an OMElement representation The token generator must be configured to create tokens using an OMElement representation. security.wssecurity.WSEC6715W=CWWSS6715W: Default KeyInfoContentGenerator element is not defined. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS8029E=CWWSS8029E: The SAML AudienceRestriction MUST contain EntityID [{0}] of the service provider. The SAML AudienceRestriction does not contain the service provider's EntityID. Check with your SAML identity provider, and ensure it emits the correct AudienceRestriction. security.wssecurity.WSEC6823W=CWWSS6823W: The configured Nonce cache size {0} is not a valid integer. Using default Nonce cache size {1}. Nonce cache size must be an integer. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS7565E=CWWSS7565E: No unique Id was defined in the SAML attributes. A unique Id is required but was not found in the SAML attributes. Define a uniqueId for the SAML token in the bindings. security.wssecurity.WSEC6714W=CWWSS6714W: Default KeyLocator element is not defined. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS8028E=CWWSS8028E: The received Assertion must not exceed the time in the SessionNotOnOrAfter attribute in the <AuthnStatement> element. The received Assertion has exceeded the SessionNotOnOrAfter attribute from <AuthnStatement> element. Synchronize the system clocks between your SAML identity provider and WebSphere Application Server service provider, and ensure SessionNotOnOrAfter is large enough for recipient processing. security.wssecurity.WSEC6859E=CWWSS6859E: A renewable security token has expired. The security token has expired. Renew the security token. security.wssecurity.EncryptionReceiver.enc13=CWWSS5114E: The EncryptedData element cannot be found however, the ({0}) element is found. The XML encryption process requires the EncryptedData element, which cannot be found. 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. security.wssecurity.CWWSS7564E=CWWSS7564E: No principal was defined in the SAML attributes. A principal is required but was not found in the SAML attributes. Define a principal for the SAML token in the bindings. security.wssecurity.WSEC6713W=CWWSS6713W: Java Authentication and Authorization Service (JAAS) configuration is not defined. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SCTGenerateLoginModule.DKG02=CWWSS7204E: Derived key is not valid Might be due to a problem during the derived key generation If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS8027E=CWWSS8027E: The NotBefore attribute in the <SubjectConfirmationData> element is not allowed. The NotBefore attribute in the <SubjectConfirmationData> element is not allowed. Check with your SAML identity provider, and ensure it does not emit the NotBefore attribute in the <SubjectConfirmationData> element. security.wssecurity.WSEC6822E=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. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6858E=CWWSS6858E: The requested scope is not valid or not supported. The Application Server cannot process the request because the requested scope is not valid or not supported. Refer to the documentation or the configuration to determine the valid scopes. security.wssecurity.CertificateFactory.getInstance=CWWSS7066E: Certificate type {0} is not supported, exception: {1} This error is caused by the requested certificate type is not available from the JCE provider. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS7563E=CWWSS7563E: No realm was defined in the SAML attributes. A realm is required but was not found in the SAML attributes. Define a realm for the SAML token in the bindings. security.wssecurity.WSEC6712W=CWWSS6712W: Default TokenConsumer element is not defined. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS8026E=CWWSS8026E: The SAML Assertion must not pass NotOnOrAfter in the <SubjectConfirmationData> element. The SAML Assertion has passed NotOnOrAfter in the <SubjectConfirmationData> element. Synchronize the system clocks between your SAML identity provider and WebSphere Application Server service provider, and ensure NotOnOrAfter is large enough for recipient processing. security.wssecurity.WSEC6821E=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. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6857E=CWWSS6857E: The requested time range is not valid or not supported. The Application Server cannot process the request because the requested time range is not valid or not supported. Refer to the documentation or the configuration to determine the valid time ranges. security.wssecurity.CWWSS7562E=CWWSS7562E: The SAML token contains more than one unique ID. Only one unique ID may be defined for a SAML token Define a single unique ID for the SAML token in the bindings. security.wssecurity.WSEC6711W=CWWSS6711W: Default KeyInfoContentConsumer element is not defined. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSOutboundConfig.s01=CWWSS7308E: The WSS API configuration is not valid. The following exception occurred: {0} The WSS API configuration is not valid. See the referenced exception. Correct the WSS API configuration. security.wssecurity.CWWSS8025E=CWWSS8025E: The SAML recipient attribute [{0}] MUST match the assertion consumer service URL [{1}]. The SAML recipient is a URI specifying the entity or location to which an attesting entity can present the assertion. Check with your SAML identity provider, and ensure it emits a correct Recipient attribute. security.wssecurity.trust.client.requestfailed=CWWSS7533E: The trust client request failed [{0}]. The trust client failed to establish communications with the specified trust service provider. Verify that the specified trust service provider Web service address is correct, and the application trust policy set and bindings are configured correctly for the trust service provider. security.wssecurity.WSEC6820E=CWWSS6820E: The {0} security token does not have a token consumer references. The Security token need a token consumer reference. Check binding file for the security token type. security.wssecurity.WSEC6856E=CWWSS6856E: The request data is out of date. The data in the request has expired. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KRBGenerateLoginModule.s03=CWWSS7318E: Invalid SPN format: {0}. Expected format: service_name/hostname The format to use for the property is in service_name/hostname. Verify the value of property named com.ibm.wsspi.wssecurity.krbtoken.serviceSPN. security.wssecurity.KRBGenerateLoginModule.s02=CWWSS7317E: Failed to login for Kerberos AP_REQ token generation due to exception {0}. Kerberos login failed to generate the Kerberos AP_REQ token for the current message due to the exception stated. Verify the intended user is valid in Kerberos registry and specified correctly in the binding file. Set JVM properties, com.ibm.security.jgss.debug=all, com.ibm.security.krb5.Krb5Debug=all, com.ibm.security.ktp.debug=all for more log messages. security.wssecurity.KRBGenerateLoginModule.s01=CWWSS7292E: Failed to login for Kerberos AP_REQ token generation due to exception {0} from Kerberos Token Profile processing runtime. Kerberos login failed to generate the Kerberos AP_REQ token for the current message due to the exception. Verify the intended user is valid in Kerberos registry and specified correctly in the binding file. Set JVM properties, com.ibm.security.jgss.debug=all, com.ibm.security.krb5.Krb5Debug=all, com.ibm.security.ktp.debug=all for more log messages. security.wssecurity.trust.client.instance=CWWSS7531E: Unable to create a new instance of the trust client. The trust client was unable to access the necessary resources to create a new instance. Verify that the product was installed properly, and the application classpath is correct. security.wssecurity.CWWSS7561E=CWWSS7561E: The SAML attribute for unique ID has more than one value. The SAML attribute defining the unique ID can have only one value. Assign a single value to the SAML attribute defining the unique ID in the bindings. security.wssecurity.CWWSS8024E=CWWSS8024E: The SAML Assertion MUST contain a Recipient in the <SubjectConfirmationData> element. The SAML Assertion does not contain a required Recipient in <SubjectConfirmationData> element. Check with your SAML identity provider, and ensure it emits <SubjectConfirmationData> element. security.wssecurity.WSEC6855E=CWWSS6855E: The specified RequestSecurityToken token is not understood. The Application Server cannot process the request because elements exist that are not understood. Refer to the information center for information on the request formats. security.wssecurity.CWWSS7560E=CWWSS7560E: The SAML token contains more than one realm. Only one realm may be defined for a SAML token Define a single realm for the SAML token in the bindings. security.wssecurity.CWWSS8023E=CWWSS8023E: The SAML Assertion MUST contain a SubjectConfirmation Method of urn:oasis:names:tc:SAML:2.0:cm:bearer. The SAML Assertion does not contain a required SubjectConfirmation Method of urn:oasis:names:tc:SAML:2.0:cm:bearer. Check with your SAML identity provider, and ensure it emits a bearer Subject Confirmation method. security.wssecurity.WSEC6854E=CWWSS6854E: The digest elements are not sufficient. The request is missing some of the required authentication information. Refer to the information center for information on the authentication requirements. security.wssecurity.CWWSS8022E=CWWSS8022E: The SAML Assertion MUST contain a <Subject> element. The SAML Assertion MUST contain a <Subject> element. Check with your SAML identity provider, and ensure it emits a <Subject> element. security.wssecurity.WSEC6853E=CWWSS6853E: Security token has been revoked. The security token is not valid. Obtain a new security token. security.wssecurity.KRBConsumeLoginModule.s02=CWWSS7294E: Failed to login for Kerberos AP_REQ token consumption due to exception {0}. Kerberos login failed to consume the Kerberos AP_REQ token for the current message due to the exception. Verify the Kerberos Distribution Center(KDC) is configured properly to accept the request AP_REQ token. Set JVM properties, com.ibm.security.jgss.debug=all, com.ibm.security.krb5.Krb5Debug=all, com.ibm.security.ktp.debug=all for more log messages. security.wssecurity.KRBConsumeLoginModule.s01=CWWSS7293E: Failed to login for Kerberos AP_REQ token consumption due to exception {0} from Kerberos Token Profile processing runtime. Kerberos login failed to consume the Kerberos AP_REQ token for the current message due to the exception. Verify the Kerberos Distribution Center(KDC) is configured properly to accept the request AP_REQ token. Set JVM properties, com.ibm.security.jgss.debug=all, com.ibm.security.krb5.Krb5Debug=all, com.ibm.security.ktp.debug=all for more log messages. security.wssecurity.CWWSS8021E=CWWSS8021E: The SAML assertions MUST contain at least one <AuthnStatement> element that reflects the authentication of the principal to the identity provider. The SAML assertions do not contain a required <AuthnStatement> element that reflects the authentication of the principal to the identity provider. Check with your SAML identity provider, and ensure it emits at least one <AuthStatement> element. security.wssecurity.WSEC6852E=CWWSS6852E: The specified request failed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.ReferenceProcessor.s01=CWWSS5533E: A digest value over {0} and the containing element {1} does not satisfy onlySignEntireHeadersAndBody assertion. A signature digest must cover over the entire soap body, or cover over an entire soap header, or cover over a direct child element of the security header when the onlySignEntireHeadersAndBody assertion presents. Please refer to Section 6.6 "[Entire Header and Body Signatures] Property" of the WS-SecurityPolicy v1.2 Specification. Check the security policy for both server and client applications and correct the corresponding SignedElements assertion. security.wssecurity.CWWSS8020E=CWWSS8020E: The SAML response MUST contain at least one <Assertion> element. The SAML response does not contain a required <Assertion> element. Check with your SAML identity provider, and ensure it emits at least one <Assertion> element. security.wssecurity.WSEC6851E=CWWSS6851E: Authentication failed. The request does not meet the authentication requirements. Refer to the configuration files for the authentication requirements. security.wssecurity.WSEC6850E=CWWSS6850E: The request is not valid or is malformed. The request might be missing required elements. Refer to the information center for information on the request formats. security.wssecurity.KeyInfoConsumer.getValueType03=CWWSS6016E: The Embedded Element was not processed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyInfoConsumer.getValueType02=CWWSS6015E: The KeyIdentifier Element was not processed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyInfoConsumer.getValueType01=CWWSS6014E: The Reference Element was not processed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.ctxmgr.isnull=CWWSS0031E: The Application Server cannot retrieve the ContextManager class. The ContextManager class is null. 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. No user action is required. security.wssecurity.WSSecurityConsumerHandler.s05=CWWSS7509W: The received SOAP request message is rejected becasue it does not correctly specify SOAP action and WS-Addressing action while there is at least one PolicySet attachment at operation level of the {0} service. Web services security runtime cannot find correrct 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 for security consideration. Modify web services client so that correct SOAP action or WS-Addressing action is specified in request messages. security.wssecurity.WSSecurityConsumerHandler.s04=CWWSS7244E: The Application Server was unable to load the trust related policy set for the {0} resource. The trust related policy set for the resource failed to load. Verify that the trust related policy set for the resource is correct. security.wssecurity.WSSecurityConsumerHandler.s03=CWWSS7059E: Unable to process inbound SOAP message. Unexpected object {0} in PolicyTypeBinding. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSecurityConsumerHandler.s02=CWWSS7058E: Unable to process inbound SOAP message. Exception retrieved from PolicyTypeLoader: This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSecurityConsumerHandler.s01=CWWSS7034W: Both Policy Set and WSSAPI configurations have been read. Policy Set configuration will override WSSAPI configuration. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7239E=CWWSS7239E: The Application Server encountered an invalid Soap Envelope Body. The Soap Envelope Body must consist of exactly one RequestSecurityToken element. 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. Verify that the policy set is correct. security.wssecurity.DTKeyInfoResolver.s01=CWWSS5660E: All the attempts based on each KeyInfoConsumer failed. The last exception is: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SCTGenerateLoginModule.getClientConfigurationFactory=CWWSS7038E: Unable to get ClientConfigurationFactory. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7238E=CWWSS7238E: The Application Server encountered the {0} token type, which is invalid for the {1} endpoint. The token type that was specified is not valid for the endpoint. Verify that the token type is valid for the endpoint. security.wssecurity.X509TokenGenerator.s03=CWWSS6527E: Unable to find the processing result of the login module: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.X509TokenGenerator.s02=CWWSS6526E: The callback handler {0} cannot handle the callbacks correctly. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.X509TokenGenerator.s01=CWWSS6525E: The {0} callback handler instantiation failed This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyInfoGenerator.getKey03=CWWSS6002E: The KeyInfo type {0} is not valid. The Key object was not obtained. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyInfoGenerator.getKey02=CWWSS6001E: Key object was not obtained. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyInfoGenerator.getKey01=CWWSS6000E: The configuration for the KeyInfo was not obtained. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SCTGenerateLoginModule.getAxisConfiguration=CWWSS7040E: Unable to get AxisConfiguration. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.X509TokenConsumer.s02=CWWSS6521E: The Login failed because of an exception This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.X509TokenConsumer.s01=CWWSS6520E: An Exception occured during the construction of the login context This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7235I=CWWSS7235I: The specified SecurityContextToken could not be renewed. A new context token will be issued. This is information only. No action is required. security.wssecurity.SCTConsumeLoginModule.invalidSCT05=CWWSS7218E: SCT is not valid for the webservice endpoint "{0}". SCT is issued for "{1}". The security context token is valid at the webservice endpoint specified in the RequestSecurityToken. Ensure the endpoint address of the webservice (To: header) matches the AppliesTo URL specified in the RequestSecurityToken including port number. Verify an intermediate server is not modifying the To: header. security.wssecurity.SCTConsumeLoginModule.invalidSCT04=CWWSS7216E: Missing instance information in the Security Context Token. The security context is associated with more than one instance Security Context Token should have instance information security.wssecurity.SCTConsumeLoginModule.invalidSCT03=CWWSS7215E: Cannot get valid security context token from the cache The security context token might be expired or the token does not exist in the cache If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SCTConsumeLoginModule.invalidSCT02=CWWSS7214E: Cannot get valid security context token from the trust service The security context token might be expired or there is a problem retrieving the token from the trust service If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7234I=CWWSS7234I: The SecurityContextToken is either invalidated or not renewable. Cancel request is not procsssed. This is information only. No action is required. security.wssecurity.trust.client.loadpolicyset=CWWSS7530E: Unable to load the application trust policyset and bindings [{0}], [{1}, {2}, {3}, {4}, {5}]. Loading the application trust policy set and bindings produced an error. Verify that the specified policy set and bindings names are correct. Also, verify that the policy set and bindings files exist, and are in the correct location. security.wssecurity.WSSecurityDefaultGeneratorConfig.s01=CWWSS7320E: A securityTokenReference with name [{0}] was found in a token generator of type [{1}] when loading default bindings. A securityTokenReference is not supported on default bindings. A securityTokenReference is not supported on default bindings. Regenerate the token generator in the default bindings, so the securityTokenReference is removed. security.wssecurity.DecryptedPartChecker.s01=CWWSS5710E: A required message part [{0}] is not encrypted. The policy expected the specified message part to be encrypted. Verify that the policies on both the client and the server specify the same EncryptedParts and EncryptedElements. security.wssecurity.WSSecurityDefaultConsumerConfig.s04=CWWSS7319E: A securityTokenReference with name [{0}] was found in the token consumer of type [{1}] when loading default bindings. A securityTokenReference is not supported on default bindings. A securityTokenReference is not supported on default bindings. Regenerate the token consumer in the default bindings, so the securityTokenReference is removed. security.wssecurity.WSSecurityDefaultConsumerConfig.s03=CWWSS7043E: An invalid algorithm parameter has been found. Specified parameters were: [{0}] A not valid parameter for a cryptographic algorithm has been found. Check parameters and ensure they are valid. security.wssecurity.WSSecurityDefaultConsumerConfig.s02=CWWSS7042E: An invalid cryptographic algorithm has been specified . The requested algorithm was {0} and the caught exception is [{1}] The requested cryptographic algorithm is not available on this environment. Specify an available cryptographic algorithm. security.wssecurity.WSSecurityDefaultConsumerConfig.s01=CWWSS7041E: An exception has been caught while selecting an X509Certificate. The exception is [{0}] This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSAuditEventGeneratorImpl.s03=CWWSS7289E: Insufficient data to generate the specified security audit event. The WebSphere platform audit subsystem platform implementation cannot generate a security audit event because critical data was missing. Contact WebSphere support for help. security.wssecurity.WSSAuditEventGeneratorImpl.s02=CWWSS7288W: Caught Exception [{0}] when generating security audit events. The WebSphere platform audit subsystem platform implementation failed generating a security audit event. Examine the exception for possible cause. Contact WebSphere support for help if this problem was not caused by a configuration problem or failure of an external component such as an event log database. security.wssecurity.WSEC0127W=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. The specified Nonce length is less than the minimum value that is required. The Nonce is a randomly generated value. 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. security.wssecurity.SCTGenerateLoginModule.getSCTLifetime=CWWSS7201E: Lifetime information of the Security Context Token is not valid Requested Security Token Response message does not have the valid life time information of the Security Context Token If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7012E=CWWSS7012E: This method is unsupported in the current implementation: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateCommonConfig.s20=CWWSS5419E: EncryptedParts, or SignedParts: Namespace attribute is required: {0}. When specifying a Header to be signed or encrypted, the Namespace attribute is required. Specify the Namespace attribute for the Header on the EncryptedParts or SignedParts. security.wssecurity.trust.client.rstc.provider=CWWSS7528E: The specified request security token trust service provider [{0}] must match the existing provider [{1}] in the collection. The request security token cannot be added to the collection because the token trust service provider address does not match the trust service provider address of the existing requests in the collection. Ensure that the trust service provider of the request security token matches the provider of existing requests in the collection. security.wssecurity.PrivateCommonConfig.s19=CWWSS5418E: KeyStore: KeyStore should have one of the following. Either KeyStoreRef attribute or storepass, path, type attributes. KeyStore doesnot have one of the following. Either KeyStoreRef attribute or storepass, path, type attributes. Change the keystore element to have either KeyStoreRef or storepass,path,type attributes security.wssecurity.PrivateCommonConfig.s18=CWWSS5417E: KeyStore: KeyStore referenced is not valid : {0}. Keystore reference is not valid. Verify keystore is available, not corrupted and specified correctly in binding. security.wssecurity.PrivateCommonConfig.s17=CWWSS5416E: name attribute is required: {0} for Key. name attribute required for Key. Verify the Key:- name attribute in the binding is required. security.wssecurity.PrivateCommonConfig.s16=CWWSS5415E: alias attribute is required: {0} for Key. alias attribute required for Key. Verify the Key:- alias attribute in the binding is required. security.wssecurity.PrivateCommonConfig.s15=CWWSS5314E: missing storepass attribute {0} for KeyStore. storepass attribute required for KeyStore. Verify the KeyStore:- storepass attribute in the binding is required. security.wssecurity.PrivateCommonConfig.s14=CWWSS5413E: missing path attribute {0} for KeyStore. path attribute required for KeyStore. Verify the KeyStore:- path attribute in the binding is required. security.wssecurity.WSEC7011E=CWWSS7011E: The argument to the get factory method in the following class has a null value: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateCommonConfig.s13=CWWSS5412E: missing type attribute {0} for KeyStore. type attribute required for KeyStore. Verify the KeyStore:- type attribute in the binding is required. security.wssecurity.PrivateCommonConfig.s10=CWWSS5409E: MessageParts, Timestamp, or Nonce: keyword attribute is required: {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyNameContentConsumer.getKeyName01=CWWSS6060E: The KeyName Element was not processed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateCommonConfig.s09=CWWSS5408E: MessageParts, Timestamp, or Nonce: dialect attribute is required: {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateCommonConfig.s08=CWWSS5407E: Integrity or Confidentiality: Processing order MUST be zero or positive number: {0}. The order is negative or not valid value. Verify the order is specified correctly in the binding. The order mentions how to process signature and encryption. security.wssecurity.PrivateCommonConfig.s07=CWWSS5406E: Missing required MessageParts {0} for (Required)Integrity or (Required)Confidentiality. (Required)Integrity or (Required)Confidentiality: At least one MessagePart is required. Provide Required)Integrity or (Required)Confidentiality message part. security.wssecurity.PrivateCommonConfig.s06=CWWSS5405E: At least one transform is required: {0} in the PartReference in SigningInfo. transform information for the signing algorithm is not valid or incomplete Verify transform information in the binding. security.wssecurity.WSWSSLoginModule.s02=CWWSS7314E: The asserted identity {0} is not trusted. Realm of the asserted identity is not in list of trusted inbound realms. Verify the list of inbound trusted realms. security.wssecurity.PrivateCommonConfig.s05=CWWSS5404E: DigestMethod is required: {0}. information for the signing algorithm is not valid or incomplete. One of the places to verify is the binding, ensure the algorithm provided is valid. security.wssecurity.WSWSSLoginModule.s01=CWWSS7297E: Failed to update Subject with Kerberos credentials due to exception {0} in Caller processing. Caller processing failed due to the exception. Verify the caller configuration and look for other failures in JGSS and Java Kerberos logs. security.wssecurity.PrivateCommonConfig.s04=CWWSS5403E: referenced message part is required: {0}. There is mismatch of referencing signed parts in policy and binding. PartReference in SigningInfo is required to be referenced correctly in the policy and binding. security.wssecurity.WSEC7010E=CWWSS7010E: The Application Server cannot obtain a part from the partMap field. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.BinaryTokenReceiver.token16=CWWSS5083E: The ValueType attribute for the KeyIdentifier element cannot be found. The KeyIdentifier element requires the ValueType attribute, which cannot be found. Verify that you specified the ValueType attribute for the KeyIdentifier element in the SOAP message. security.wssecurity.PrivateCommonConfig.s03=CWWSS5402E: At least one AlgorithmURI is required: {0}. The Algorithm URI information could be missing or not valid in the binding. Verify the Algorithm information in the binding. security.wssecurity.BinaryTokenReceiver.token15=CWWSS5082E: The {0} encoding is not supported. The encoding type that you requested is not supported. Verify that you encoded the SOAP message with the supported encoding type. security.wssecurity.PrivateCommonConfig.s02=CWWSS5401E: factoryname is not available for the algorithm mapping configuration: {0}. One of the possible reasons be the Algorithm URI couldnot be mapped to the Algorithm Factory. Verify the algorithm information in the binding. security.wssecurity.PrivateCommonConfig.s01=CWWSS5400E: algorithm attribute is required but found: {0}. Missing or incorrect algorithm attribute. Verify the algorithm has been specified in the binding. security.wssecurity.WSEC0124W=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. The specified Nonce cache size is less than the minimum value that is required. The Nonce is a randomly generated value. 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. security.wssecurity.PolicyOutboundConfig.s10=CWWSS7347E: Failed to load bootstrap configuration. The following exception was caught: [{0}]. There was a problem loading the bootstrap configuration. The caught exception has the precise reason. Look at the exception that was caught and take appropriate action. security.wssecurity.PolicyOutboundConfig.s09=CWWSS7339E: Can not find encryption bindings for specified confidential parts for an outbound message in the default bindings. Confidential parts were specified for outbound messages in the policy, but there was no matching encryption information on the outbound section of the default bindings. Regenerate the default bindings, so there are encryption bindings for the specified outbound integral parts. security.wssecurity.PolicyOutboundConfig.s08=CWWSS7338E: Can not find signature bindings for specified integral parts for an outbound message in the default bindings. Integral parts were specified for outbound messages in the policy, but there was no matching signing information on the outbound section of the default bindings. Regenerate the default bindings, so there are signature bindings for the specified outbound integral parts. security.wssecurity.PolicyOutboundConfig.s07=CWWSS7328E: Did not find a token generator for the supporting token of type [{0}]. A token generator was not found in the bindings for the supporting token of this type. Correct the bindings so a token generator for the supporting token in the policy is defined. security.wssecurity.PolicyOutboundConfig.s06=CWWSS7326E: Found two UsernameToken Token generators one configured as trusted id and the other as a caller id, of UsernameToken type [{0}] in the default bindings, but only one UsernameToken SupportingToken assertion in the policy. Do not know which generator to chose. Two UsernameToken token generators, one configured as trusted id and the other as a caller id were found, but do not know which one to use, as only one UsernameToken assertion was found in the policy. This is an ambiguous situation. Correct the policy so two Usernametoken SupportingToken assertions are in the policy, or remove one of the two UsernameToken token generators from the default bindings. security.wssecurity.SecureConversationCacheImpl.s01=CWWSS7122W: Failed to create distributed SecurityContextToken cache. 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. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PolicyOutboundConfig.s05=CWWSS7323E: More than one supporting token generator of the type [{0}] found on the default bindings. Only one token generator per supporting token type is allowed. Only one token generator per supporting token type is allowed. Correct the default bindings so only one token generator for each supporting token type is configured. security.wssecurity.PolicyOutboundConfig.s04=CWWSS7322E: More than one idAssertion UsernameToken generator of type [{0}] was found in the default bindings. In default bindings only one idAssertion UsernameToken generator is allowed. Correct the bindings and ensure that it has exactly one idAssertion UsernameToken generator. security.wssecurity.PolicyOutboundConfig.s03=CWWSS7321E: More than one trustedId UsernameToken generator of type [{0}] was found in the default bindings. In default bindings only one trustedId UsernameToken generator is allowed. Correct the bindings and ensure that it has exactly one trustedId UsernameToken generator. security.wssecurity.WSSAuditEventGeneratorFactory.s01=CWWSS7287W: Caught Exception [{0}] during audit subsystem initialization. The audit subsystem failed initialization. One possible reason is the implementation class cannot be found or loaded. Examine the exception for possible cause. Contact the vendor who provided the audit service extension implementation for help. security.wssecurity.LoginProcessor.s16=CWWSS6515E: Private Credentials already exist in the subject. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PolicyOutboundConfig.s02=CWWSS7291E: Lightweight Third-Party Authentication (LTPA) token is not supported on Thinclient environment. The LTPA token is only supported on WebSphere Server. Change the token type in the policy and regenerate the file. security.wssecurity.LoginProcessor.s15=CWWSS6514E: Public Credentials already exist in the subject. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PolicyOutboundConfig.s01=CWWSS7290E: Value type {0} not valid for the token generator configuration when the {1} property is set to false. Value type {2} must be used. The above property determines what the valid value types are. Change the value type in the binding and regenerate the file, or set the above property to true. security.wssecurity.LoginProcessor.s14=CWWSS6513E: The Principal already exists in the subject. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.LoginProcessor.s13=CWWSS6512E: The protection token of type [{0}] is used as a caller token, but a total number of {1} were found in the message. This protection token type was designated as a caller, but more than one token of the same type was found in the message. Do not know which one to use as caller. Service sending the message with multiple tokens of this same type should be reconfigured to send only one. security.wssecurity.LoginProcessor.s12=CWWSS6511E: The supporting token of type [{0}] is used as a caller token, but a total number of {1} were found in the message. This supporting token type was designated as a caller, but more than one token of the same type was found in the message. Do not know which one to use as caller. Service sending the message with multiple tokens of this same type should be reconfigured to send only one. security.wssecurity.KeyInfoConsumer.getKeyInfoType01=CWWSS6013E: The KeyInfo type is UNKNOWN. KeyInfo specified in the bindings probably is not valid. Check the bindings security.wssecurity.LoginProcessor.s11=CWWSS6510E: The following login failure occured : {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.LoginProcessor.s09=CWWSS6509E: A valid WebSphere security subject was not found during caller login. Caller login failed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.LoginProcessor.s08=CWWSS6508E: The caller of type [{0}] is used as a caller token, but more than one was found in the message. This token type was designated as a caller, but more than one token of the same type was found in the message. Do not know which one to use as caller. Service sending the message with multiple tokens of this same type should be reconfigured to send only one. security.wssecurity.LoginProcessor.s07=CWWSS6507E: None of the required callers was found in the message. A set of callers was defined in the bindings, and no caller token was found in the incoming message. Do not require caller in the bindings or ensure that the client does send the required token. security.wssecurity.LoginProcessor.s06=CWWSS6505E: There is more than one token used as caller in the message and no caller order of preference found. More than one caller token type was specified in the bindings without specifying and order attribute, and more than one caller token was found on the message. Not enough information available to decide which token to use as caller. Specify a single token type to use as caller in the bindings, or utilize order attribute when specifying multiple callers to eliminate ambiguity. security.wssecurity.LoginProcessor.s05=CWWSS6504E: There are more than one candidates used to specify the caller identifier. Only one caller identifier is expected This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.LoginProcessor.s04=CWWSS6503E: There are more than one candidates used to specify the trusted identifier. Only one trust identifier is expected This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.LoginProcessor.s03=CWWSS6502E: The token that is used to specify the caller identity or trusted identity cannot be null. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.LoginProcessor.s02=CWWSS6501E: There is no trusted identity candidate that can be used. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.LoginProcessor.s01=CWWSS6500E: There is no caller identity candidate that can be used to login. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6819E=CWWSS6819E: The {0} security token with is the {1} type is required, but it does not have a matching token consumer. The security token type need define a matching token consumer. Check binding file for the security token type. security.wssecurity.WSSCCacheCommand.s06=CWWSS7230E: The AdminCommand {0} loading failed. The exception is {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSCCacheCommand.s05=CWWSS7229E: The AdminCommand {0} creation failed. The exception is {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSCCacheCommand.s04=CWWSS7228E: The AdminCommand could not update the WS-SecureConversation client cache configuration file. The exception is {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC0158I=CWWSS0158I: Hardware Crypto Acceleration is enabled: {0} This is for informational purposes only. This is for informational purposes only. security.wssecurity.WSSCCacheCommand.s03=CWWSS7227E: The AdminCommand could not find the property {0} in WS-SecureConversation client cache configuration file. The requested property is not in WS-SecureConversation client cache configuration file. Check WS-SecureConversation client cache configuration file. security.wssecurity.WSSCCacheCommand.s02=CWWSS7226E: The AdminCommand could not find WS-SecureConversation client cache configuration file. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC0122E=CWWSS0122E: The Nonce cache is null or is not initialized. The Nonce is a randomly generated value. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSCCacheCommand.s01=CWWSS7225E: The JAXB is unable to load WS-SecureConversation client cache configuration file. The exception is {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7079E=CWWSS7079E: {0} is not instantiated. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC0157W=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. The RSA-OAEP algorithm is only supported by JDK Version 1.5 and later. 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. security.wssecurity.WSSRealmImpl.s02=CWWSS7312E: Failed to parse realm qualified identity. The identity delimiter pattern appears more than once. Either the user name or the unique representation of the user in the identity string {0} contains the identity delimeter pattern {1}. Modify the name representation to remove any ambiguity. security.wssecurity.WSEC6818E=CWWSS6818E: The {0} security token does not have a token generator references. The Security token need a token generator reference. Check binding file for the security token type. security.wssecurity.WSSRealmImpl.s01=CWWSS7311W: Failed to construct realm qualified identity. A RunAs Subject may not exist or may not contain WebSphere user security attributes. Check if the application server security is enabled. security.wssecurity.WSEC0121E=CWWSS0121E: The Nonce is null or of zero length. The Nonce is a randomly generated value. 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. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7078E=CWWSS7078E: Nonce manager must not be accessed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC0120W=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. The format for the value of the Nonce clock skew is not an integer. The Nonce is a randomly generated value. 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. security.wssecurity.CWWSS7559E=CWWSS7559E: The SAML attribute for realm has more than one value. The SAML attribute defining the realm can have only one value. Assign a single value to the SAML attribute defining the realm in the bindings. security.wssecurity.STRReferenceContentGenerator.getKey01=CWWSS6020E: The TokenGenerator object is not obtained. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6817E=CWWSS6817E: The {0} security token with the {1} type does not have a matching token generator.. The security token need a matching token generator. Check binding file for the security token type. security.wssecurity.WSEC7077E=CWWSS7077E: The login module name is null. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS7558E=CWWSS7558E: The SAML token contains more than one principal. Only one principal may be defined for a SAML token Define a single principal for the SAML token in the bindings. security.wssecurity.WSEC6816E=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. The security token should be used for stand-alone tokens. Check the binding file. security.wssecurity.WSEC0155E=CWWSS0155E: Retrieving the byte array representation of an X.509 Certificate caused a CertificateEncodingException. The exception is: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7076E=CWWSS7076E: {0} is not instantiated. A required class could not be instantiated. 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. security.wssecurity.EmbeddedContentConsumer.getKey01=CWWSS6040E: TokenConsumer object is not obtained. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS7557E=CWWSS7557E: The SAML attribute for principal has more than one value. The SAML attribute defining the principal can have only one value. Assign a single value to the SAML attribute defining the principal in the bindings. security.wssecurity.WSEC6815E=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. The security token should be used for stand-alone tokens. Check binding file. security.wssecurity.trust.client.rstc.header=CWWSS7527E: The specified request security token header [{0}] must match the existing header [{1}] in the collection. The request security token cannot be added to the collection because the token header does not match the header of the existing requests in the collection. Ensure that the request security token header matches the header of the existing requests in the collection. security.wssecurity.WSEC7075E=CWWSS7075E: The duration is invalid. 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. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.FileConfigSSR.init=CWWSS5122E: The WS-Security configuration object cannot be created. Error: {0} Internal configuration files cannot be loaded. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS7556E=CWWSS7556E: The [{0}] SAML confirmation method is not supported by login module [{1}]. The SAML token specifies a confirmation method that is not supported by the login module. The SAML token provider must be configured to not send SAML tokens with the unsupported confirmation method. security.wssecurity.CWWSS8019E=CWWSS8019E: Authentication Error: HTTP Artifact Binding is not supported. Authentication Error: HTTP Artifact Binding is not supported. Contact WebSphere Application Server support for help. security.wssecurity.WSEC0153E=CWWSS0153E: The callback handler encountered an unsupported callback. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WasConfigHelperImpl.s01=CWWSS7315E: Caught an exception attempting to create default configuration objects. The following exception occurred: {0} There was a problem loading named bindings or default bindings for this application. Exception will have details on what went wrong during loading. Please examine specific exception and take corrective actions. security.wssecurity.trust.client.axisserviceparam=CWWSS7522E: The specified configuration setting is invalid: [{0}, {1}]. The trust client cannot configure the outgoing request with the specified configuration setting. Verify that the configuration setting is correct. security.wssecurity.WSEC7074E=CWWSS7074E: The key is not retrieved. The exception is: The decrypting key or verifying key could not be retrieved from the security token because an exception was received. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS7555E=CWWSS7555E: More than one bootstrap binding was found in the bindings. There can be at most one bootstrap binding in the bindings. Regenerate the bindings and insure only a single bootstrap binding is present. security.wssecurity.CWWSS8018E=CWWSS8018E: Authentication Error: SAMLResponse could not be verified. Please review and correct the TAI configuration, and try again. Authentication Error: SAMLResponse could not be verified. Please review and correct the TAI configuration, and try again. Contact WebSphere Application Server support for help if this problem was not caused by a configuration problem. security.wssecurity.WSEC6813E=CWWSS6813E: The issuer name {0} retrieved from the message is different from the issuer name {1} acquired from the keystore Path: {2}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7073E=CWWSS7073E: The key is not retrieved. The exception is: The encrypting key or signing key could not be retrieved from the security token. Either an exception occurred or null was returned. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS7554E=CWWSS7554E: More than one application binding was found in the bindings. There can be at most one application binding in the bindings. Regenerate the bindings and insure only a single application binding is present. security.wssecurity.CWWSS8017E=CWWSS8017E: Authentication Error: Single-Sign-on cookie is not present or could not be verified. Please login to the SAML Identity Provider, and try again. Authentication Error: There is no valid Single-Sign-on cookie. Please login to the SAML Identity Provider, and try again. Please login to the SAML Identity Provider, and try again. security.wssecurity.WSEC6812E=CWWSS6812E: The key name {0} retrieved from the message is different from the key name {1} acquired from the keystore Path: {2}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7072E=CWWSS7072E: The Securtiy Context Token is expired and is not renewable. The Security Context Token is not renewable after expiration. 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. security.wssecurity.CWWSS7553E=CWWSS7553E: The keyType attribute with value of {0} is not valid for the {1} confirmation method. The keyType attribute for this request is not valid this confirmation method. Select an appropriate keyType attribute for the given confirmation method. security.wssecurity.CWWSS8016E=CWWSS8016E: Authentication Error: SAMLResponse is required for this operation. Please login to the SAML Identity Provider, and try again. Authentication Error: SAMLResponse is required for the request to SAML AssertionConsumerService. Please login to the SAML Identity Provider, and try again. Contact WebSphere Application Server support for help if this problem was not caused by a configuration problem. security.wssecurity.WSEC6811E=CWWSS6811E: The key identifier {0} retrieved from the message is different from the key identifier {1} acquired from the keystore Path: {2}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7071E=CWWSS7071E: The Security Context Token is not validated. The exception is: The Security Context Token could not be validated because an exception was received. Make sure the security token service (STS) is configured correctly, and that the WSSGenerationContext and WSSConsumingContext specified on the validate operation are correct. security.wssecurity.KeyIdContentConsumer.getIdentifierType01=CWWSS6054E: The IdentifierType attribute is not found This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS7552E=CWWSS7552E: The RunAs subject might not exist, might not contain the required SecurityToken or might contain more than one required SecurityToken. The outgoing request is not able to use the token in the RunAs subject to exchange it for the requested token from the security token service. If a token cannot be extracted from the RunAs subject, change the configuration to issue a new token by removing the custom property, useRunAsSubjectOnly, from the callback handler. security.wssecurity.CWWSS8015E=CWWSS8015E: The Single-Sign-on partner was not established in the SAML TAI configuration. The Single-Sign-on partner is required in the SAML TAI configuration. Check the SAML TAI configuration, and ensure at least one Single-Sign-On partner is created. security.wssecurity.WSEC6810E=CWWSS6810E: The runtime can not identify the key corresponding to the identifier [{0}]. The keystore configuration used by key locator is not defined in the consumer side. Check binding file. security.wssecurity.WSEC7070E=CWWSS7070E: The Security Context Token is not renewable. The exception is: The Security Context Token could not be renewed because an exception was received. 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. security.wssecurity.CWWSS7551E=CWWSS7551E: The value of the ValueType attribute for the SAML token cannot be determined. This token cannot be parsed. To parse a SAML token, the parser is required to determine the value of the ValueType attribute for the token. Receiving an unsupported SAML token type is one possible cause for this error. Ensure the security token service that provides the token is configured to return a supported SAML token type. See the Information Center for list of supported SAML token types. security.wssecurity.CWWSS8014E=CWWSS8014E: The Issuer name in the SAML Assertion is not trusted. The Issuer name in the SAML Assertion is not trusted. Check TAI configuration to make sure the issuer name is trusted. security.wssecurity.CWWSS7550E=CWWSS7550E: The request to the security token service does not return a GenericSecurityToken object, or the value of the ValueType attribute for the returned token is not [{0}]. The outgoing request is not able to use the token in the RunAsSubject to exchange it for the requested token from the security token service. Configure the security token service to return a GenericSecurityToken with the expected ValueType attribute value. security.wssecurity.Instantiate=CWWSS7065W: Unable to instantiate the class {0}. 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. Make sure the class specified is not an abstract class, an interface, an array class, a primitive type, or void, and has default constructor. security.wssecurity.CWWSS8013E=CWWSS8013E: The Signature element in the SAML Assertion is not valid. The Signature element in the SAML Assertion is not valid. Examine the exception for possible cause. Contact WebSphere Application Server support for help if this problem was not caused by a configuration problem. security.wssecurity.WSEC6844E=CWWSS6844E: The following authentication result exists in the pool but it is not candidate for trusted identity: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6735E=CWWSS6735E: The user registry or login is unable to validate the {0} . {1} 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. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS8012E=CWWSS8012E: The Signature element in the response is not valid. The Signature element in the SAML response is not valid. Examine the exception for possible cause. Contact WebSphere Application Server support for help if this problem was not caused by a configuration problem. security.wssecurity.WSEC6843E=CWWSS6843E: The following authentication result exists in the pool but it is not a candidate for the caller identity: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS8011W=CWWSS8011W: The Extension element in the response is ignored. The Extension element in the SAML response is not validated. Check with your SAML identity provider if you do not want the Extension element present. security.wssecurity.WSEC6734E=CWWSS6734E: The generator or consumer configuration for Web services security is missing from message. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6842E=CWWSS6842E: The Application Server cannot validate the trusted identity because a list of trusted identities is not specified. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6733E=CWWSS6733E: Multiple namespaces exist in the Web Services Addressing (WS-Addressing) headers. Multiple conflicting Web Services Addressing (WS-Addressing) namespaces in the SOAP message. Make sure the correct and supported WS-Addressing namespace is used. security.wssecurity.CWWSS8010E=CWWSS8010E: The SAML response Destination [{0}] is not for the service provider [{1}]. A URI reference indicating the address to which the request has been sent. The Destination attribute in response is present, but it does not match the configured AssertionConsumerService URL. Check with your SAML identity provider. Ensure it either does not emit the Destination attribute, or the Destination matches the partner's AssertionConsumerService URL. security.wssecurity.PrivateGeneratorConfig.nullValueType=CWWSS7340E: The token generator with name {0} has a null ValueType. The ValueType is required. The ValueType on the token generator is missing. Check and correct the ValueType information in the bindings. The token generator configuration must specify a valid ValueType. security.wssecurity.WSEC6841E=CWWSS6841E: The AxisService class value is NULL. The Application Server cannot decide if the object is a service provider or requester. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSGenerator.s14=CWWSS5557E: More than one parent elements exists. Cannot move the Timestamp element. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSGenerator.s13=CWWSS5556E: A Timestamp element was not found. Cannot move the Timestamp element. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSGenerator.s12=CWWSS5555E: The mustUnderstand attribute on the Security header does not have the required value: existing value={0}, required value={1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSGenerator.s11=CWWSS5554E: Unknown version of the SOAP specification: versionId={0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.UNTConsumeLoginModule.s03=CWWSS7313W: The received identity should be but is not qualified by realm name. The user identity should be qualified by realm name when the com.ibm.wsspi.wssecurity.token.IDAssertion.sendRealm property value is set to true. Check if the com.ibm.wsspi.wssecurity.token.IDAssertion.sendRealm property is set to true in binding on sending side. security.wssecurity.SecurityTokenImpl.version=CWWSS7224E: The serialized security token version is different from current token version. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CommonReceiverConfig.s22=CWWSS5018E: The {0} provider does not exist. Error: {1} The specified provider is not configured. Verify that you configured the specified provider correctly. security.wssecurity.WSEC6840E=CWWSS6840E: The certificate cache manager is not initialized on the Java 2 Platform, Enterprise Edition (J2EE) client side or the server side. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CommonReceiverConfig.s21=CWWSS5017E: The {0} algorithm parameter is not valid. The specified initialization parameters for this certificate store are incorrect. Verify that you specified the certificate store configuration in the binding correctly. security.wssecurity.CommonReceiverConfig.s20=CWWSS5016E: The provider does not support the {0} certificate store type. The certificate store type is not available or supported by the provider. Verify that you specified a supported certificate store type. security.wssecurity.WSSGenerator.s04=CWWSS5553E: The message cannot be generated. Unexpected configuration found: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSGenerator.s03=CWWSS5552E: Found an unexpected element as the parent element: {0}. Expected the {1} element with a supported namespace. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSGenerator.s01=CWWSS5550E: Unable to obtain the message context. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SignatureGenerator.s13=CWWSS5635E: Null is not allowed as the parent element of the {0} element. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SignatureGenerator.s12=CWWSS5634E: Signing the message produced the following exception: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SignatureGenerator.s11=CWWSS5633E: Constructing the Signature element produced the following exception: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CommonReceiverConfig.s12=CWWSS5010E: The key store is invalid, exception: {0}. Verify the key store is properly setup and configured for the parameter to PKIXBuilderParameters. The key store file does not contain at least one trusted certificate entry or has not successfully initialized. 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. security.wssecurity.WSEC5195E=CWWSS5195E: The Application Server cannot obtain the {0} algorithm from the {1} provider, which resulted in the following exception: {2} An implementation of the specified algorithm could not be obtained from the JCE provider. Make sure that the JCE provider being used does provide the specified algorithm. security.wssecurity.SignatureGenerator.s03=CWWSS5632E: The {0} value is not supported when selecting elements. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SignatureGenerator.s02=CWWSS5631E: The {0} type is not supported when selecting elements. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SignatureGenerator.s01=CWWSS5630E: Null is not allowed for the type when selecting elements. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC5193E=CWWSS5193E: The nonce, which is a randomly generated value, has expired. 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. 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. security.wssecurity.trust.client.provider=CWWSS7532E: An invalid trust service provider webservice address [{0}] was specified. The specified trust service provider is not a valid Web service address for processing trust client requests. Verify that the specified trust service provider Web service address is correct and accessible. security.wssecurity.CWWSS8041E=CWWSS8041E: No unique Id was defined in the SAML attributes. A unique Id is required but was not found in the SAML attributes. Define a uniqueId for the SAML token in the TAI. security.wssecurity.WSTrustCallbackHandler.expiredSCT02=CWWSS7217E: Security context token is expired and is not renewable after expiration Cannot renew the security context token set renewableAfterExpiration property to true security.wssecurity.WSEC7009E=CWWSS7009E: The argument in WSSTimestampImpl.setDuration(Duration time) method has a null value. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.trust.client.setting=CWWSS7529E: The specified trust client settings [{0}, {1}] is invalid. The specified trust client key value settings is not valid. Verify that the value of the trust client settings key is correct. security.wssecurity.CWWSS8040E=CWWSS8040E: No principal was defined in the SAML attributes. A principal is required but was not found in the SAML attributes. Define a principal for the SAML token in the TAI. security.xml.AlgorithmFactory.s03=CWWSS2502I: Hardware key store is used. This message is for informational purposes only. No action is required. security.xml.AlgorithmFactory.s02=CWWSS2501I: Hardware Cryptographic Acceleration is enabled. This message is for informational purposes only. No action is required. security.wssecurity.WSSFactory.s01=CWWSS5490E: Unsupported type of WS-Security factory: {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.xml.AlgorithmFactory.s01=CWWSS2500E: Failed to use hardware cryptographic provider and continue to process cryptographic operations using software provider. Cryptographic operations are processed using the software provider because the hardware cryptographic processing has failed. Check the first failure data capture (FFDC) log file for error details and make sure the hardware cryptographic provider is properly configured. security.wssecurity.WSEC7008E=CWWSS7008E: The argument in the WSSGenerationContextImpl.generate(Object obj) method has a null value. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.QNameHeaderSelector.s01=CWWSS5685E: The required Header/@Namespace attribute was not specified. The Header/@Namespace attribute is required. The Header/@Name attribute is optional. Verify that the Header/@Namespace is specified correctly in the policy. security.wssecurity.PrivateGeneratorConfig.s34=CWWSS7280E: Token Generator token type [{0}] does not match encryption token type defined in the policy. The Token Generator token type in the bindings file must match the encryption token type in the policy file. Correct the policy or binding file and regenerate the file. security.wssecurity.PrivateGeneratorConfig.s33=CWWSS7279E: Token Generator token type [{0}] does not match signature token type defined in the policy. The Token Generator token type in the bindings file must match the signature token type in the policy file. Correct the policy or binding file and regenerate the file. security.wssecurity.PKCS7CallbackHandler.s01=CWWSS6630E: An exception occured during the handling a Public Key Cryptograpgy Standards (PKCS7) object. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC5190W=CWWSS5190W: The {0} property contains the {1} value, which is a non-integer string value. The {2} default value has been used instead. The Application Server expects an integer value. However, the specified value is not an integer number. Correct the value for the property so that it is an integer number. security.wssecurity.load.cell.wssecurity.xml=CWWSS0006W: The binding loader cannot load {0} from the repository. The file is a cell-level configuration file for Web services security. The system cannot load the cell-level ws-security.xml configuration file. The file might be corrupted, missing, or in the wrong location. 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. security.wssecurity.sct.s17=CWWSS7117W: Could not extract UUID from the ValidateTarget element in the request. 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. Refer to the documentation for acceptable validate request formats. security.wssecurity.sct.s16=CWWSS7116W: The specified validate request is missing the ValidateTarget element. Validate requests must have the ValidateTarget element, which specifies the UUID of the security context token to validate. Refer to the documentation for acceptable validate request formats. security.wssecurity.DOMUtil.s04=CWWSS5303E: The Application Server cannot parse an input source. The following exception occurred: {0} There has been an error processing an XML file. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.sct.s15=CWWSS7115E: The algorithm and provider information is missing from the cached security context token. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.DOMUtil.s03=CWWSS5302E: The following file does not exist and can not be loaded: {0}. A configuration file is missing. Verify that the configuration file is in the specified location. security.wssecurity.sct.s14=CWWSS7114W: Could not extract UUID from the RenewTarget element in the request. 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. Refer to the documentation for acceptable renew request formats. security.wssecurity.DOMUtil.s02=CWWSS5301E: The Application Server cannot resolve an entry with publicId={0} and systemId={1} values. The following exception occurred: {2} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.sct.s13=CWWSS7113W: The specified renew request is missing the RenewTarget element. Renew requests must have the RenewTarget element, which specifies the UUID of the security context token to renew. Refer to the documentation for acceptable renew request formats. security.wssecurity.sct.s12=CWWSS7112E: The SCT renew request handler class is not initialized. The SCT handler classes must be initialized before use. Refresh the Security Token Service or restart the server. security.wssecurity.sct.s11=CWWSS7111W: Could not extract UUID from the CancelTarget element in the request. 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. Refer to the documentation for acceptable cancel request formats. security.wssecurity.CWWSS0111E=CWWSS0111E: The SecurityTokenServiceAdmin MBean failed to start. The exception is {0} 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. There is no user action to correct this problem. security.wssecurity.sct.s10=CWWSS7110W: The specified cancel request is missing the CancelTarget element. Cancel requests must have the CancelTarget element, which specifies the UUID of the security context token to cancel. Refer to the documentation for acceptable cancel request formats. security.wssecurity.PrivateGeneratorConfig.s29=CWWSS5458E: Missing TokenGenerator reference in the KeyInfo. Missing TokenGenerator reference in the KeyInfo. Verify the binding for TokenGenerator reference in KeyInfo. security.wssecurity.WSEC7007E=CWWSS7007E: The Application Server cannot obtain the class name from the generatorMap field. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateGeneratorConfig.s28=CWWSS5457E: Null or empty is not allowed to the name of KeyInfo. Null or empty is not allowed to the name of KeyInfo. Verify the binding for valid name attribute for KeyInfo. security.wssecurity.PrivateGeneratorConfig.s26=CWWSS5455E: Null or empty is not allowed to the name of TokenGenerator or TokenConsumer. Null or empty is not allowed to the name of TokenGenerator or TokenConsumer. Verify the binding for valid name attribute for TokenGenerator and TokenConsumer. security.wssecurity.PrivateGeneratorConfig.s25=CWWSS5454E: Unable to find the default configuration. Unable to find the default configuration. Verify default binding have not been modified, deleted or corrupted. security.wssecurity.PrivateGeneratorConfig.s24=CWWSS5453E: AddCreateTimestamp/@expires has invalid format string: {0} AddCreateTimestamp/@expires has a not valid format string. Verify binding for valid timestamp format. security.wssecurity.PrivateGeneratorConfig.s23=CWWSS5452E: Null or empty is not allowed to the name of SecurityToken or RequiredSecurityToken. Null or empty is not allowed to the name of SecurityToken or RequiredSecurityToken. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateGeneratorConfig.s21=CWWSS5450E: Null or empty is not allowed to the name of Integrity, Confidentiality, RequiredIntegrity, or RequiredConfidentiality. Null or empty is not allowed to the name of Integrity, Confidentiality, RequiredIntegrity, or RequiredConfidentiality. Verify wsu:Id value is set valid for Integrity and Confidentiality in policy. security.wssecurity.sct.s09=CWWSS7109W: The URI for the WSC namespace could not be created. The exception is: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.sct.s08=CWWSS7108E: The requested security context token cannot be issued due to cache failure. The attempt to cache the security context token failed. Verify that the SCT configuration file contains the fully qualified name of an accessible token cache factory class under the property tokenCacheFactory. security.wssecurity.sct.s07=CWWSS7107W: The request is missing entropy information. Requests are required to contain Entropy and BinarySecret elements. Refer to the documentation for acceptable issue request formats. security.wssecurity.sct.s06=CWWSS7106E: The SCT issue request handler class is not initialized. The SCT handler classes must be initialized before use. Refresh the Security Token Service or restart the server. security.wssecurity.sct.s05=CWWSS7105W: No custom property in the SCT plugin configuration is defined for the validate request type. A valid URI value for the validate request type must be present in the SCT configuration. Verify that the SCT configuration file contains a valid URI for the custom property validateRequestTypeRST. security.wssecurity.sct.s04=CWWSS7104W: No custom property in the SCT plugin configuration is defined for the renew request type. A valid URI value for the renew request type must be present in the SCT configuration. Verify that the SCT configuration file contains a valid URI for the custom property renewRequestTypeRST. security.wssecurity.sct.s03=CWWSS7103W: No custom property in the SCT plugin configuration is defined for the cancel request type. A valid URI value for the cancel request type must be present in the SCT configuration. Verify that the SCT configuration file contains a valid URI for the custom property cancelRequestTypeRST. security.wssecurity.sct.s02=CWWSS7102W: No custom property in the SCT plugin configuration is defined for the issue request type. A valid URI value for the issue request type must be present in the SCT configuration. Verify that the SCT configuration file contains a valid URI for the custom property issueRequestTypeRST. security.wssecurity.sct.s01=CWWSS7101E: No handler for request type: {0} The request type is not recognized. Verify that the plugins configuration file contains the correct information. security.wssecurity.WSEC7006E=CWWSS7006E: The transform(Object obj) method in the following class has a null value: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateGeneratorConfig.s16=CWWSS5445W: There are no allowed key encryption algorithms defined. There are no allowed key encryption algorithms defined. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateGeneratorConfig.s15=CWWSS5444W: There are no allowed data encryption algorithms defined. There are no allowed data encryption algorithms defined. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateGeneratorConfig.s14=CWWSS5443W: There are no allowed digest algorithms defined. There are no allowed digest algorithms defined. Verify the algorithm attributes in binding and algorithmSuite in policy are valid. security.wssecurity.PrivateGeneratorConfig.s13=CWWSS5442W: There are no allowed signature algorithms defined. There are no allowed signature algorithms defined. Verify the algorithm attributes in binding and algorithmSuite in policy are valid. security.wssecurity.PrivateGeneratorConfig.s12=CWWSS5441W: There are no allowed canonicalization algorithms defined. There are no allowed canonicalization algorithms defined. Verify the algorithm attributes in binding and algorithmSuite in policy are valid. security.wssecurity.PrivateGeneratorConfig.s11=CWWSS5440W: There are no allowed transform algorithms defined. There are no allowed transform algorithms defined. Verify if the transform algorithm in binding and algorithmSuite in policy are valid. security.wssecurity.WSEC7005E=CWWSS7005E: The argument in the OMStructure.isFeatureSupported(String feature) method has a null value. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateGeneratorConfig.s08=CWWSS5437E: The combination of secret key algorithms [{0}] and the type of key information [{1}] is not allowed. The combination of secret key algorithms [{0}] and the type of key information [{1}] is not allowed. Verify if the secret key algorithm information provided in policy and key information provided in binding are valid. security.wssecurity.PrivateGeneratorConfig.s07=CWWSS5436E: Missing or invalid keyinfo in Generator - SigningInfo or EncryptionInfo: Only one KeyInfo is required found: {0}. Generator SigningInfo or EncryptionInfo: Only one KeyInfo is required. Verify the binding for keyinfo information. security.wssecurity.PrivateGeneratorConfig.s06=CWWSS5435E: BasicAuth: User id is null, but user password is not null. BasicAuth: User id is null, but user password is not null. Verify the User ID and password for the BasicAuth in the binding. security.wssecurity.PrivateGeneratorConfig.s05=CWWSS5434E: Missing classname attribute {0} in CallbackHandler. CallbackHandler classname attribute is required. Verify the binding if the CallbackHandler className is valid. security.wssecurity.PrivateGeneratorConfig.s04=CWWSS5433E: ValueType is required: {0} for TokenGenerator. TokenGenerator ValueType attribute is required. Verify binding for valueType of TokenGenerator. security.wssecurity.PrivateGeneratorConfig.s03=CWWSS5432E: error in instantiating the TokenGenerator: {0}. TokenGenerator classname and instance attribute is required. Verify binding for correct TokenGenerator classname. security.wssecurity.PrivateGeneratorConfig.s02=CWWSS5431E: Expecting only one KeyInfo in Generator EncryptionInfo but found: {0}. Only one KeyInfo is required in Generator EncryptionInfo. Verify the binding for the Encryption Generators KeyInfo. security.wssecurity.PrivateGeneratorConfig.s01=CWWSS5430E: Unexpected keyinfo {0} in Generator SigningInfo. Only one KeyInfo is required in Generator SigningInfo. Verify the binding for the Signature Generators KeyInfo. security.wssecurity.WSEC0119W=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. The specified value for the Nonce clock skew is not within the valid range. The Nonce is a randomly generated value. 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. security.wssecurity.WSEC5209E=CWWSS5209E: The time stamp value for the nonce, which is a randomly generated value, occurs too far into the future. The clocks on the client and server might not be synchronized. Ensure that the date, time, and time zone are synchronized for both the client and the server. security.wssecurity.PrivateConsumerConfig.nullValueType=CWWSS7341E: The token consumer with name {0} has a null ValueType. The ValueType is required. The ValueType on the token consumer is missing. Check and correct the ValueType information in the bindings. The token consumer configuration must specify a valid ValueType. security.wssecurity.WSSUserRegistryProcessor.s02=CWWSS7063E: Failed to check username [{0}] in the UserRegsitry: {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7004E=CWWSS7004E: The argument in the JAXWSGenerationContextRetriever.getWSSGeneratoinContext(Object object) method has a null value. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSUserRegistryProcessor.s01=CWWSS7062E: Failed to check username [{0}] and password in the UserRegsitry: {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSecurityAssertionTransform.s08=CWWSS7508E: Security header layout assertion - strict - can not be supported if the EncryptionBeforeSigning assertion is present. Strict header layout can not be guaranteed when encrypting before signing. Modify the policy and select an alternative header order. security.wssecurity.WSSecurityAssertionTransform.s07=CWWSS7507E: Message part encryption and signing order is unclear The order attribute in the signature and encryption references in the bindings can not be published using WS-Policy Modify the bindings to ensure that all signature order attributes are either higher or all lower than the encryption order attribute values. security.wssecurity.WSSecurityAssertionTransform.s06=CWWSS7506E: A signature transform was found in the bindings that can not be published The signature reference contains a transformation algorithm that can not be published using WS-Policy Modify the WS-Security bindings to remove the transformation algorithm that can not be published using WS-Policy security.wssecurity.WSEC0118W=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. The specified value for the Nonce max age is not within the valid range. The Nonce is a randomly generated value. 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. security.wssecurity.WSSecurityAssertionTransform.s05=CWWSS7505E: The signature transform algorithms found in the bindings do not match those found in the policy file. The policy file contains an AlgorithmSuite assertion that has parameters that contradict settings in the bindings. Modify either the policy file or the bindings to ensure the Algorithm suite parameters match. security.wssecurity.WSSecurityAssertionTransform.s04=CWWSS7504E: The trust service bootstrap policy can not be published. Request message part protection and response message part protection policies must be the same in order for bootstrap policy to be published. Modify the trust system policy set to ensure the message part protection policies are the same for request and response. security.wssecurity.WSSecurityAssertionTransform.s03=CWWSS7503E: A problem occurred transforming the trust service bootstrap policy None None security.wssecurity.WSSecurityAssertionTransform.s02=CWWSS7502E: More than one signature or encryption token was found in the WS-Security bindings At most one signature token and one encryption token can be declared in the WS-Security bindings Modify the WS-Security bindings to ensure there is no more than one encryption token and one signature token security.wssecurity.WSSecurityAssertionTransform.s01=CWWSS7501E: The WS-Policy transform operation was called with incorrect or missing parameters None None security.wssecurity.WSEC5208E=CWWSS5208E: The time stamp value occurs too far into the future. The clocks on the client and server might not be synchronized. Ensure that the date, time, and time zone are synchronized for both the client and the server. security.wssecurity.WSEC7003E=CWWSS7003E: The following argument in the JAXWSGenerationContextPutter.put(Object messageContext, Object wssGenerationContext) method has a null value: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC0117W=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. The format for the value of the Nonce max age is not an integer. The Nonce is a randomly generated value. 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. security.wssecurity.WSEC7002W=CWWSS7002W: The following parse error occurred: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.VerifiedPartChecker.s02=CWWSS5721E: A required nonce is not found in the message part [{0}]. The policy expected the specified message part to contain a Nonce element, which is a randomly generated value. Verify that the policies on both the client and the server specify that a Nonce is required for the specified message part. security.wssecurity.VerifiedPartChecker.s01=CWWSS5720E: A required message part [{0}] is not signed. The policy expected the specified message part to be signed. Verify that the policies on both the client and the server specify the same SignedParts and SignedElements. security.wssecurity.WSTrustCallbackHandler.clientCushionAndSCT=CWWSS7222E: Security context token lifetime is lower than the WS- SecureConversation client cache cushion Newly issued security context token should have more lifetime than the WS-SecureConversation client cache cushion Either lower the client cache cushion setting or increase the lifetime of the security context token security.wssecurity.WSEC0116W=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. The specified value for the Nonce cache timeout is less than the minimum value that is required. The Nonce is a randomly generated value. 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. security.wssecurity.WSSecurityGeneratorHandler.s02=CWWSS7061E: Unable to process outbound SOAP message. Unexpected object {0} in PolicyTypeBinding. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSecurityGeneratorHandler.s01=CWWSS7060E: Unable to process outbound SOAP message. Exception retrieved from PolicyTypeLoader: This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7001W=CWWSS7001W: The builder.getDocumentElement method returns a null value. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC5206E=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}. The clocks on the client and server might not be synchronized. Ensure that the date, time, and time zone are synchronized for both the client and the server. security.wssecurity.WSSConsumer.s51=CWWSS5535E: The SAML sender-vouches assertion whose ID is [{0}] is not signed by the sender or protected with an SSL client certificate authentication. The SAML sender-vouches assertion must be signed by the sender or protected with an SSL client certificate authentication. Verify the SAML sender-vouches assertion is signed with a SOAP message. security.wssecurity.WSSConsumer.s50=CWWSS5534E: The SAML holder-of-key assertion whose ID is [{0}] is not used for signing or endorsing a request. The SAML holder-of-key assertion must be used for message signing or endorsing a request. Verify the SAML token is configured as a protection token for message signing or endorsing a request. security.wssecurity.WSEC0115W=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. The format for the value for the Nonce cache timeout is not an integer. The Nonce is a randomly generated value. 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. security.wssecurity.WSEC5205E=CWWSS5205E: The time stamp in the message has expired. 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. 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. security.wssecurity.WSSConsumer.s49=CWWSS7310E: XML encryption information exists in the security header, however an inbound XML encryption configuration is not present. The SOAP message that has been received by the consumer or provider contained XML encryption information in the security header. However, the application that is receiving the message is not configured for inbound XML encryption. The security header in the inbound SOAP message contained a mustUnderstand attribute with a value of 1. Therefore, an exception has been created. Complete one of the following tasks: - Add inbound XML encryption configuration to the application that is receiving the SOAP message. - Remove outbound XML encryption configuration from the application that is sending the SOAP message. - Configure the application that is sending the SOAP message to not add the mustUnderstand attribute to the SOAP security header. security.wssecurity.WSSConsumer.s48=CWWSS7309E: An XML digital signature exists in the security header. Hoowever an inbound signature configuration is not present. The SOAP message that has been received by the consumer or provider contained an XML digital signature in the security header. However, the application that is receiving the message is not configured for inbound XML digital signature. The security header in the inbound SOAP message contained a mustUnderstand attribute with a value of 1. Therefore, an exception has been created. Complete one of the following tasks: - Add an inbound XML digital signature configuration to the application that is receiving the SOAP message. - Remove the outbound XML Digital signature configuration from the application that is sending the SOAP message. - Configure the application that is sending the SOAP message to not add the mustUnderstand attribute to the SOAP security header. security.wssecurity.WSSConsumer.s47=CWWSS7284E: The Value type of the token is {0}, but {1} is found in the token consumer configuration. The token consumer specified enforceTokenVersion. The token Value type must match the token consumer configuration. Verify that the token generator and consumer configuration is correct. Removing enforceTokenVersion will allow the token with a different Value type to be consumed. security.wssecurity.WSSConsumer.s46=CWWSS5532W: A SignatureConfirmation element found, but it is not required. It will not be verified. This might be a configuration error. The RequireSignatureConfirmation policy assertion might be specified in the service policy but not in the client policy. Verify that the RequireSignatureConfirmation policy assertion is not needed in the client policy. security.wssecurity.WSSConsumer.s45=CWWSS5531E: An EncryptedHeader element with mustUnderstand equal 1 was misunderstood while processing the security header for a Web service. An EncryptedHeader element with mustUnderstand equal 1 was not decrypted while processing the security header for a Web service. Verify that the EncryptedHeader element was targeted to the correct role or actor. security.wssecurity.WSSConsumer.s44=CWWSS5530E: The response message did not contain the expected signature confirmation element with no Value attribute. The RequireSignatureConfirmation policy assertion might not be specified in the policies for the client or the server. Verify that the RequireSignatureConfirmation policy assertion has been specified in the policies for both the client and the server. security.wssecurity.WSSConsumer.s43=CWWSS5529E: Expected {0} signature confirmation elements in the response and found {1}. The RequireSignatureConfirmation policy assertion might not be specified in the policies for the client or the server. Verify that the RequireSignatureConfirmation policy assertion has been specified in the policies for both the client and the server. security.wssecurity.SCTConsumeLoginModule.invalidValueType=CWWSS7213E: Unsupported Value Type. Expecting this [{0}], but found [{1}]. The Value Type specified in the token configuration is not correct Check and correct the Value Type information in the bindings for the token consumer configuration security.wssecurity.WSSConsumer.s42=CWWSS5528E: The signature confirmation value on the response does not match a signature value from the request. The RequireSignatureConfirmation policy assertion might not be specified in the policies for the client or the server. Verify that the RequireSignatureConfirmation policy assertion has been specified in the policies for both the client and the server. security.wssecurity.WSSConsumer.s41=CWWSS5527E: The response message did not contain the expected Value attribute on the signature confirmation element. The RequireSignatureConfirmation policy assertion might not be specified in the policies for the client or the server. Verify that the RequireSignatureConfirmation policy assertion has been specified in the policies for both the client and the server. security.wssecurity.WSSConsumer.s40=CWWSS5526E: The server cannot find the security header for a Web service with the actor: {0} The SOAP message might not have the security constraints defined, or the actor on the server and the client do not match. Verify that the client has security configured for Web services and that the actor matches on both the client and the server. security.wssecurity.PolicyOutboundConfig.encorder=CWWSS7245E: Order is a required attribute for encryption information on outbound bindings. The attached WS-PolicySet binding file is not valid. Regenerate the binding file. security.wssecurity.WSSConsumer.s39=CWWSS5525E: The server cannot find the security header for a Web service with no actor. The SOAP message might not have the security constraints defined, or the actor on the server and the client do not match. Verify that the client has security configured for Web services and that the actor matches on both the client and the server. security.wssecurity.WSSConsumer.s38=CWWSS5524W: The server cannot find the security header for a Web service with the actor: {0} The SOAP message might not have the security constraints defined, or the actor on the server and the client do not match. Verify that the client has security configured for Web services and that the actor matches on both the client and the server. security.wssecurity.WSSConsumer.s34=CWWSS5520E: An exception occurred during token processing. The exception is: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSConsumer.s33=CWWSS5519W: A valid X509 Certificate is not found in the token. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSConsumer.s32=CWWSS5518W: Unable to obtain the X509 certificate from a token. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS7516E=CWWSS7516E: {0} failed to locate token: {1} for key id: {2} A SAML token cannot be located for the provided ID. Provide a valid SAML ID. security.wssecurity.TokenManager.finalizeSubject05=CWWSS6545E: The invocation subject was not set correctly to the ContextManager. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.TokenManager.finalizeSubject04=CWWSS6544E: The caller subject was not set correctly to the ContextManager. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.TokenManager.finalizeSubject03=CWWSS6543E: The invocation subject was not obtained from the ContextManager. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.TokenManager.finalizeSubject02=CWWSS6542E: The caller subject was not obtained from the ContextManager. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.TokenManager.finalizeSubject01=CWWSS6541E: The instance of ContextManager was not obtained. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSConsumer.s23=CWWSS5514E: An exception while processing WS-Security message: {0} An exception while processing WS-Security message. Turn on trace to collect more debug information. Refer to the information center to collect trace data. security.wssecurity.WSSConsumer.s21=CWWSS5512E: Unable to cast to the appropriate SecurityToken {0} into {1}. The securitytoken provided in policy or binding is not supported or valid. Verify the Token information in the policy and binding. security.wssecurity.WSSecurityBindingLoaderImpl.s13=CWWSS7057E: No policy set attachment type found. Cannot determine if policy set is for client, application or system/trust. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSecurityBindingLoaderImpl.s12=CWWSS7056E: Policy set attachment type {0} not valid. Valid policy set attachment types are client, application, or system/trust. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSecurityBindingLoaderImpl.s11=CWWSS7055E: Exception retrieved from PolicyTypeLoader: This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSecurityBindingLoaderImpl.s10=CWWSS7054E: Problem found while loading WSSecurity policy. Expected {0}, found {1}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSTrustCallbackHandler.expiredSCT=CWWSS7221I: Security context token is expired and is not renewable after expiration This is informational message only. Runtime will automatically request for a new SC token Informational message security.wssecurity.CWWSS7515E=CWWSS7515E: Wrong token type: {0} The token type must be SAML, which is the only token type processed by this login module. Provide a SAML token type. security.wssecurity.WSEC6809E=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}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSConsumer.s16=CWWSS5511E: An exception occurred during the decryption of a message. The exception is {0} Error during message decryption. For more information on error turn on trace to collect more debug information. Refer to the information center to collect trace data. security.wssecurity.WSSecurityBindingLoaderImpl.s09=CWWSS7053W: No web services security custom bindings were found. Default bindings will be used. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSConsumer.s15=CWWSS5510E: An exception occurred during the signature verification. The exception is {0} Error during signature verification. For more information on error turn on trace to collect more debug information. Refer to the information center to collect trace data. security.wssecurity.WSSecurityBindingLoaderImpl.s08=CWWSS7052E: Policy set not found for application. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSConsumer.s14=CWWSS5509E: A security token whose type is [{0}] is required. Expected Security Token missing. Verify the valuetype information of the Token in the binding. security.wssecurity.WSSecurityBindingLoaderImpl.s07=CWWSS7051E: No web services security custom bindings or default bindings were found. Loading of default and custom bindings failed. It is impossible to complete configuration. Check trace and FFDC logs for problems logged during loading of custom and default bindings and take appropriate action. security.wssecurity.WSSConsumer.s13=CWWSS5508E: All the attempts based on each TokenConsumer failed. The last exception is {0} The provided TokenConsumer is corrupted or not valid. Verify TokenConsumer information in the binding. security.wssecurity.WSSecurityBindingLoaderImpl.s06=CWWSS7050E: Null returned from jaxb for the web services security custom bindings. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSConsumer.s12=CWWSS5507E: All the attempts based on each EncryptionInfo failed. The last exception is {0} The provided EncryptionInfo is corrupted or not valid. Verify EncryptionInfo information in the binding. security.wssecurity.WSSecurityBindingLoaderImpl.s05=CWWSS7049E: Exception received while loading the web services security custom bindings: This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSConsumer.s11=CWWSS5506E: All the attempts based on each SigningInfo failed. The last exception is {0} The provided SigningInfo is corrupted or not valid. Verify SigningInfo information in the binding. security.wssecurity.WSSecurityBindingLoaderImpl.s04=CWWSS7048E: Could not load ws-security.xml file. There was a problem loading the ws-security.xml file. It could have been moved, deleted or corrupted. Verify that the ws-security.xml file is present and intact in the WebSphere installation. security.wssecurity.WSSecurityBindingLoaderImpl.s03=CWWSS7047E: No web services security default bindings were found. Default bindings were not found. Check logs and trace to see if default bindings were found in the filesystem or if there were any loading errors, and take appropriate action. security.wssecurity.WSSecurityBindingLoaderImpl.s02=CWWSS7046E: Null returned from jaxb for the web services security default bindings. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSecurityBindingLoaderImpl.s01=CWWSS7045E: Exception received while loading the web services security default bindings. The exception is [{0}]. There was an exception received while loading default bindings. The exception will contain the specific problem found. Refer to the exception thrown for details and take appropriate action. security.wssecurity.WSEC7069E=CWWSS7069E: Cannot get valid Lifetime information for Security Context Token. Either the createdDate or expiredDate is null. Both createdDate and expiredDate are required when renewing a Security Context Token. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS7514E=CWWSS7514E: The propagation token is not valid for this request. The propagation token is not valid for this request. Provide a valid propagation token for this request. security.wssecurity.WSEC6808E=CWWSS6808E: There is no X509 certificate in request message. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSConsumer.s06=CWWSS5505E: There are different namespaceURIs for WS-Security {0}. There is mismatch of WS-Security Namespace URI versions. Verify in binding approrpriate WS-Security Namespace URI versions are specified. security.wssecurity.WSSConsumer.s05=CWWSS5504E: The namespace URI {0} is diffrent than expected. Unexpected Namespace URI. Verify the namespace URI is correct. security.wssecurity.PolicyOutboundConfig.sigorder=CWWSS7246E: Order is a required attribute for signing information on outbound bindings. The attached WS-PolicySet binding file is not valid. Regenerate the binding file. security.wssecurity.WSSConsumer.s04=CWWSS5503E: Unknown child element {0} in the {1} parent element. Unexpected child element. To get more information on the error, turn on trace to collect more debug information. Refer to the information center to collect trace data. security.wssecurity.WSSConsumer.s03=CWWSS5502E: The target element: {0} was not expected. The target element: {0} was not expected. To get more information on the error, turn on trace to collect more debug information. Refer to the information center to collect trace data. security.wssecurity.WSSConsumer.s02=CWWSS5501E: All tokens in the message must be consumed. The message contained tokens that could not be consumed. This could be a problem with the token consumer bindings. Verify that the token consumer bindings in the application security bindings are correct. security.wssecurity.STRReferenceContentConsumer.getReferenceURI02=CWWSS6032E: The URI attribute is not found. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.STRReferenceContentConsumer.getReferenceURI01=CWWSS6031E: The Reference Element was not processed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7068E=CWWSS7068E: The Securtiy Context Token is not cancelled. Exception is. The Security Context Token is not cancelled because of an exception. Look at the exception and see if the security token service (STS) configuration needs to be modifed to support SCT cancel. security.wssecurity.CWWSS7513E=CWWSS7513E: Exception from WS-Trust client call: {0} The SAML token issue request to the STS failed. The SAML token issue request to the STS failed. security.wssecurity.CWWSS7549E=CWWSS7549E: There is more than one validation result from a token validation request to the security token service. A token validation request was sent to the security token service and multiple results were returned. This is not supported. Configure the security token service to return a single result on a token validation request. security.wssecurity.WSEC5200E=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} The clocks on the client and server might not be synchronized. Ensure that the date, time, and time zone are synchronized for both the client and the server. security.wssecurity.EncryptionConsumer.s14=CWWSS5604W: An exception occurred while decrypting an EncryptedHeader that had a mustUnderstand attribute not equal to true. 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. No action is required. security.wssecurity.EncryptionConsumer.s13=CWWSS5603E: Null is not allowed as the target element. An enc:EncryptedKey or enc:ReferenceList element was expected when decrypting the message. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.EncryptionConsumer.s12=CWWSS5602E: The EncryptedKey/EncryptionMethod {0} not found. If using symmetric bindings, data encryption must be used instead of key encryption. Verify that the bindings are configured to use data encryption if symmetric bindings are used in the policy. security.wssecurity.EncryptionConsumer.s11=CWWSS5601E: The following exception occured while decrypting the message: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.ConfigUtil.s29=CWWSS6736E: The Application Server cannot load the keystore with reference {0}. A keystore with the specified reference could not be loaded. Verify that the keystore reference in the bindings is correct. security.wssecurity.ConfigUtil.s28=CWWSS6731E: The Application Server cannot load the keystore with the reference {0}. The following exception occurred: {1} A keystore with the specified reference could not be loaded. Verify that the keystore reference in the bindings is correct. security.wssecurity.ConfigUtil.s27=CWWSS5312E: The Application Server cannot retrieve the {0} key from the {1} keystore. The following exception occurred: {2} The key could not be recovered. The password for recovering the key might be wrong. Verify that the password to retrieve the key from the keystore is correct. security.wssecurity.ConfigUtil.s26=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} There has been a problem creating a Certificate Revocation List from the CRL file. Verify that the CRL file contents are correct. security.wssecurity.ConfigUtil.s25=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} A Certificate Revocation List file cannot be found in the filesystem. Verify that the file is located on the specified location. security.wssecurity.ConfigUtil.s24=CWWSS5020E: The X509 certificate cannot be created from the following X509 certificate file: {0}. Error: {1} The certificate file cannot be parsed. Verify that the certificate file format is a supported certificate type. security.wssecurity.ConfigUtil.s23=CWWSS5019E: The following X509 certificate file cannot be opened: {0}. Error: {1} The certificate file cannot be accessed because I/O errors occured. Verify that you specified the correct certificate file path and the appropriate file system permissions. security.wssecurity.WSEC0146E=CWWSS0146E: The Application Server cannot add the {0} pluggable algorithm factory. Algorithm mapping is not supported when the Application Server is in FIPS mode. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SCTGenerateLoginModule.invalidSCT=CWWSS7205E: Invalid Security Context Token Security Context Token is expired. When using WSSAPIs, user can try to renew the token and retry the request security.wssecurity.WSEC7067E=CWWSS7067E: The Security Context Token is not canceled. The exception is: The AxisService from the BindingProvider object may not be correct for this Security Context Token. Make sure the BindingProvider object specified on the cancel operation is correct. security.wssecurity.CWWSS7512E=CWWSS7512E: Unknow Confirmation Method or KeyType: {0} The confirmation method or type for this request is not recognized. The subject confirmation method can be either holder-of-key (HOK) or sender-vouches (SV). security.wssecurity.CWWSS7548E=CWWSS7548E: There is no token validation result from a token validation request to the security token service. A token validation request was sent to the security token service but no results were returned. The security token service must be configured to return a result on a token validation request. security.wssecurity.KeyStoreKeyLocator.generateIdentifier04=CWWSS6096E: An Exception occured during the generation of the Key Identifier. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyStoreKeyLocator.generateIdentifier03=CWWSS6095E: Value type must be {0}, but {1} is found. bindings have the information related to Value Type of the token Check the Value Type of the token configuration in the bindings security.wssecurity.SCTConsumeLoginModule.verifyDKT=CWWSS7212E: Cannot verify security context token using the reference information from the derived key token element This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyStoreKeyLocator.generateIdentifier02=CWWSS6094E: A null value is not allowed in the value type field. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6806E=CWWSS6806E: An exception occurs while validating the certificate owned by {0}: {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyStoreKeyLocator.generateIdentifier01=CWWSS6093E: Invalid algorithm for Identifier generation. KeyIdentifier element does not have the correct Algorithm specified If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.EncryptionConsumer.s01=CWWSS5600E: Required DataReference/@URI attribute was not specified. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.ConfigUtil.s17=CWWSS5013E: The {0} class must be a subclass of {1} class. The instantiated class is not a subclass of the required class type. Verify that the class implementation extends the required base class or implements the required interfaces. security.wssecurity.ConfigUtil.s11=CWWSS5009E: The default constructor for the {0} class cannot be accessed. The class default constructor does not exist or not public. Verify that the class public default constructor exists. security.wssecurity.ConfigUtil.s10=CWWSS5008E: The {0} class cannot be instantiated. 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. 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. security.wssecurity.CWWSS7511E=CWWSS7511E: No SAML assertion found. The assertion token cannot be retrieved because the assertion ID is missing from the requesting message context. Ensure that the assertion ID is generated for the SAML assertion. security.wssecurity.WSEC0144W=CWWSS0144W: The Application Server cannot parse the {0} value for the timestamp cache timeout. The default value of {1} seconds was used instead. The format of the value for the timestamp cache timeout is not an integer. 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. security.wssecurity.CWWSS7547E=CWWSS7547E: The ValueType of the exchanged token cannot be identified. The ValueType of the token received from the security token service cannot be identified. The security token service must be configured to return a ValueType for the exchanged token. security.wssecurity.WSEC6805E=CWWSS6805E: The certificate owned by {0} has expired: {1} The certificate is expired. Check keystore, and make sure certificate is not expired. security.wssecurity.BSTokenLoginModule.s01=CWWSS6650E: Failed to handle the callback handler and the reason is : [{0}] This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.ConfigUtil.s09=CWWSS5007E: The {0} class cannot be located. The system cannot locate the Java class that you specified in the class path. Verify that the class name is correct and exists in the appropriate class path. security.wssecurity.ConfigUtil.s08=CWWSS5800E: The KeyStoreRef attribute for the configured key store is not valid. The KeyStoreRef attribute name must be valid. Verify that the KeyStoreRef attribute exists in the binding and valid. security.wssecurity.ConfigUtil.s06=CWWSS5004E: The {0} key store cannot be loaded, due to {1}: {2} 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. 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. security.wssecurity.ConfigUtil.s05=CWWSS5003E: The {0} key store cannot be read because an IOException error occurred. 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. Verify that you specified the correct key store type and password in the binding. security.wssecurity.ConfigUtil.s04=CWWSS5002E: The {0} key store cannot be opened because a FileNotFoundException error occurred. The key store path is incorrect, or the key store does not exist. Verify the path to the key store in the binding does exist on the machine. security.wssecurity.ConfigUtil.s03=CWWSS5001E: There was no password specified for the {0} key store. A password is required to load the Java key store. This password does not exist in the binding. Specify the key store password in the binding. security.wssecurity.CWWSS7510E=CWWSS7510E: Fail to acquire SAML assertion A SAML assertion cannot be issued. Ensure that the required assertion elements are specified. security.wssecurity.WSEC0143W=CWWSS0143W: The Application Server cannot parse the {0} value for the timestamp clock skew. The default value of {1} seconds was used instead. The format of the value for the timestamp clock skew is not an integer. 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. security.wssecurity.CWWSS7546E=CWWSS7546E: A token exchange with the security token service is required. No token was received. A returned token is expected when a token validation request is made to the security token service. The security token service must be configured to return a token when it handles a token validation request. security.wssecurity.CWWSS8009E=CWWSS8009E: The IssueInstant attribute of the SAML response is required. The IssueInstant attribute of the SAML response is required. Check with your SAML identity provider, and ensure it emits the IssueInstant attribute. security.wssecurity.WSEC6804E=CWWSS6804E: The {0} identifier type is unknown. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SecureConversationImpl.s02=CWWSS7349W: RM Sequence inactivity timeout interval is greater than the SCT lifetime. SCT lifetime should be equal or greater than the RM Sequence inactivity timeout. SCT lifetime is less than the RM sequence timeout. Message would not be able to be recovered as SCT will have expired before the RM sequence timeout time. It is recommended that SCT lifetime is equal or greater than the RM sequence timeout. Adjust RM and/or SCT timeouts so SCT lifetime is equal or greater than the RM inactivity timeout. security.wssecurity.SecureConversationImpl.s01=CWWSS7044E: No SCT found in the client side cache with uuid [{0}]. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC0142W=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. The specified value for the timestamp clock skew is not within the valid range. 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. security.wssecurity.CWWSS7545E=CWWSS7545E: A token consumer configuration was not found for the received token type. There was no token consumer configured for the token type received. Configure a token consumer for the received token type so it can be processed. security.wssecurity.CWWSS8008E=CWWSS8008E: The time of the response is a future time. The time of the response must be a current time. Synchronize the system clocks between your SAML identity provider and WebSphere Application Server service provider. Ensure the time of the response is not in the future. security.wssecurity.WSEC6803E=CWWSS6803E: The 0x{0} is not a BIT STRING. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.config.s09=CWWSS7237E: The Application Server was unable to configure the security token service (STS). A problem was encountered when attempting to configure the STS. Verify that the STS configuration files have not been corrupted or removed. security.wssecurity.config.s08=CWWSS7236E: The {0} configuration file contains invalid settings. The Application Server encountered not valid settings while loading the configuration file. Verify that the configuration files contain valid settings. security.wssecurity.config.s07=CWWSS6907E: The Application Server failed to obtain the instance of the security token service. This instance of the security token service is required for normal operation. Verify that the instance of the security token service exists. security.wssecurity.config.s06=CWWSS6906W: The Application Server cannot create the Uniform Resource Identifier (URI) for wildcard mapping. There is a syntax problem for the URI specifying the wildcard mapping. Verify that the installation image has not been corrupted. security.wssecurity.WSEC0141W=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. The specified value for the timestamp max age is not within the valid range. 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. security.wssecurity.CWWSS7544E=CWWSS7544E: The [{0}] token type is not supported and cannot be parsed. The received token is not supported. The token provider must be configured to send only supported token types. See the Information Center for list of supported token types. security.wssecurity.config.s05=CWWSS6905W: The Application Server cannot create a mapping for the default token type. This issue causes errors for messages that are targeted for an unconfigured endpoint. Verify that the configuration file for the security token service targets specifies a default token type. security.wssecurity.config.s04=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. There is a syntax problem for the URIs specifying the SCT token type, the SCT get request, or the SCT put request type. Verify that the installation image has not been corrupted. security.wssecurity.config.s03=CWWSS6903E: The Application Server cannot load the targets configuration file for the security token service. The targets configuration file for the security token service is needed for normal operation. Verify that the file has not been moved or become corrupted. security.wssecurity.config.s02=CWWSS6902E: The Application Server cannot load the plugins configuration file for the security token service. The plugins configuration file for the security token service is needed for normal operation. Verify that the file has not been moved or become corrupted. security.wssecurity.config.s01=CWWSS6901E: The Application Server cannot load the configuration file for the security token service. The configuration file for the security token service is needed for normal operation. Verify that the file has not been moved or become corrupted. security.wssecurity.CWWSS8007E=CWWSS8007E: The version of this response must be 2.0. The identifier for the version of SAML defined in this specification is 2.0. Check with your SAML identity provider, and ensure it emits the correct version number. security.wssecurity.WSEC6802E=CWWSS6802E: The {0} causes integer overflow. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6838E=CWWSS6838E: All caller login failed. The last exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SecureConversationCacheConfigImpl.s01=CWWSS7121W: Failed to load WS-SecureConversation client cache configuration. Using default values. WS-SecureConversation client cache configuration file, WSSCCache.xml, could not be loaded by using JAXB. Verify the WSSCCache.xml is in Cell name directory. If WSSCCache.xml existed and problem still persists, contact your service representative. security.wssecurity.TimestampGenerator.s03=CWWSS5642E: A Timestamp was specified to be added to a Timestamp. That is not allowed. A Timestamp cannot be added to a Timestamp. Modify the policy to only add a Timestamp to message parts that are not a Timestamp. Multiple signed parts can be specified to achieve this. security.wssecurity.TimestampGenerator.s02=CWWSS5641E: More than one Timestamp element was found. Cannot move the Timestamp. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.TimestampGenerator.s01=CWWSS5640E: A Timestamp header could not be added to the message when processing security for a Web service because a Timestamp header already existed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateConsumerConfig.s42=CWWSS7282E: Token Consumer token type [{0}] does not match encryption token type defined in the policy. The Token Consumer token type in the bindings file must match the encryption token type in the policy file. Correct the policy or binding file and regenerate the file. security.wssecurity.PrivateConsumerConfig.s41=CWWSS7281E: Token Consumer token type [{0}] does not match signature token type defined in the policy. The Token Consumer token type in the bindings file must match the signature token type in the policy file. Correct the policy or binding file and regenerate the file. security.wssecurity.WSEC0140W=CWWSS0140W: The Application Server cannot parse the {0} value for the timestamp max age. The default value of {1} seconds was used instead. The format for the value of the timestamp max age is not an integer. 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. security.wssecurity.CWWSS7543E=CWWSS7543E: The [{0}] SAML confirmation method is not supported. The SAML token specifies a confirmation method that is not supported. The SAML token provider must be configured to not send SAML tokens with the unsupported confirmation method. security.wssecurity.SCTGenerateLoginModule.getConfigurationContext=CWWSS7039E: Unable to get ConfigurationContext. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.TokenManager.subjectIsNull=CWWSS6540E: A subject in the context is null. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS8006E=CWWSS8006E: InResponseTo must not be present for IdP-Initiated unsolicited responses. InResponseTo is not allowed for IdP-Initiated unsolicited responses. Check with your SAML identity provider, and ensure its response is generated properly. security.wssecurity.WSEC6801E=CWWSS6801E: The {0} encoded key is unknown. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SCTGenerateLoginModule.DKG=CWWSS7203E: Derived Key generation fails with an exception: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6837E=CWWSS6837E: The caller login failed. The exception is {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateConsumerConfig.s36=CWWSS5386E: Missing a MessagePart that needs to be signed and/or encrypted. 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. 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. security.wssecurity.PrivateConsumerConfig.s32=CWWSS5382E: The trustanchor cannot be Null. trustanchor is not available. Verify that trustanchor information is provided in the binding. security.wssecurity.PrivateConsumerConfig.s31=CWWSS5381E: Unable to resolve the expected reference: {0}. The expected reference is not available. Turn on trace to collect more debug information. Refer to the information center to collect trace data. security.wssecurity.PrivateConsumerConfig.s30=CWWSS5380E: Expecting TokenConsumer with QName: {1} received Unmatched QName: {0}. Not valid or Unexpected QName for the TokenConsumer. Verify that valid QName for the TokenConsumer is provided. security.wssecurity.CWWSS7542E=CWWSS7542E: The [{0}] SAML issuer name or signer SubjectDN of the certificate are not trusted. The SAML issuer name or signer SubjectDN are not defined in the trusted issuer list that is defined in the bindings. Check your bindings to make sure the issuer name and the signer SubjectDN of the certificate are trusted. security.wssecurity.CWWSS8005E=CWWSS8005E: The Issuer format must be omitted or have a value of urn:oasis:names:tc:SAML:2.0:nameid-format:entity. The Issuer format must be omitted or have a value of urn:oasis:names:tc:SAML:2.0:nameid-format:entity. Check with you SAML identity provider and ensure it emits Issuer format properly. security.wssecurity.load.server.wssecurity.xml=CWWSS0007W: The binding loader cannot load {0} from the repository. The file is a server-level configuration file for Web services security. The system cannot load the server-level ws-security.xml configuration file. The file might be corrupted, missing, or in the wrong location. 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. security.wssecurity.WSEC6800E=CWWSS6800E: The entry with alias {0} of keystore {1} cannot be found: {2} The specified key alias is not in keystore. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6836E=CWWSS6836E: The certificate of initial sender is not in message. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateConsumerConfig.s27=CWWSS5376E: The Application Server cannot find an XPath expression for the XPath transform. An XPath transform was specified in the signing information but an XPath expression was not provided. Verify that the application bindings do provide an XPath expression in the signing information. security.wssecurity.PrivateConsumerConfig.s26=CWWSS5375E: The key information configuration has a null type. The current key information configuration string representation is {0}. A key information configuration must have a type. A probable reason could be that there is an error in the key bindings. Verify that the key bindings information in the application security bindings are correct. security.wssecurity.PrivateConsumerConfig.s25=CWWSS5374E: The key information configuration has a null class instance. The current key information configuration string representation is {0}. A key information configuration must have a class instance. A probable reason could be that there is an error in the key bindings. Verify that the key bindings configuration is correct for the application security bindings. security.wssecurity.PrivateConsumerConfig.s24=CWWSS5373E: The key consumer configuration has a null content consumer list. The current key consumer configuration string representation is {0}. 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. Verify that the key bindings configuration is correct for the application security bindings. security.wssecurity.PrivateConsumerConfig.s23=CWWSS5372E: The token consumer configuration has a null type. The current token consumer configuration string representation is {0}. 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. Verify that the token consumer binding information in the application security bindings is correct. security.wssecurity.PrivateConsumerConfig.s22=CWWSS5371E: The token consumer/generator configuration has a null class instance. The current token consumer/generator configuration string representation is {0}. 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. Verify that the token/consumer generator binding information in the application security bindings are correct. security.wssecurity.PrivateConsumerConfig.s21=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} Reference to message parts are required in order to retrieve the encryption algorithms from the policy. In this case there are none. Verify that there are message parts to be encrypted in the application security bindings. security.wssecurity.PrivateConsumerConfig.s20=CWWSS5369E: Configuration information about the encryption consumer key is missing. The current configuration for this encryption consumer is: {0}. There is no configuration found for the encryption consumer key. There might be key bindings information missing in the application security bindings. Verify that the key bindings for the encryption consumer in the application security bindings are correct. security.wssecurity.CWWSS7541E=CWWSS7541E: The SAML AudienceRestriction validation failed. The SAML token contains an AudienceRestriction assertion that cannot be verified. Do not configure the AudienceRestriction assertion in the SAML token provider, or set the validateAudienceRestriction binding option to false. security.wssecurity.CWWSS8004E=CWWSS8004E: An identifier for the response is required. The SAML Response must contain an identifier. Check with your SAML identity provider, and ensure it emits an identifier. security.wssecurity.PolicyInOutboundConfig.s33=CWWSS7345E: Can not find default bindings for creating configuration. The original error that prevented default bindings creation was [{0}]. An attempt to use default bindings failed. Default bindings creation failed earlier. Inspect original error that prevented default bindings creation and take appropriate action. security.wssecurity.PolicyInOutboundConfig.s32=CWWSS7344E: Can not fill missing supporting token bindings, as no default bindings were found. The original error that prevented default bindings creation was [{0}]. An attempt to fill missing supporting token information in custom bindings by loading missing information from default bindings failed. Default bindings creation failed earlier. Inspect original error that prevented default bindings creation and take appropriate action. security.wssecurity.PolicyInOutboundConfig.s31=CWWSS7343E: Can not fill missing signature bindings, as no default bindings were found. The original error that prevented default bindings creation was [{0}]. An attempt to fill missing signature information in custom bindings by loading missing information from default bindings failed. Default bindings creation failed earlier. Inspect original error that prevented default bindings creation and take appropriate action. security.wssecurity.PolicyInOutboundConfig.s30=CWWSS7342E: Can not fill missing encryption bindings, as no default bindings were found. The original error that prevented default bindings loading was [{0}]. An attempt to fill missing encryption information missing in custom bindings by loading missing information from default bindings failed. Default bindings loading failed earlier. Inspect original error that prevented default bindings loading and take appropriate action. security.wssecurity.PrivateConsumerConfig.s19=CWWSS5368E: A data encryption method is required in the configuration, but none was found. The current configuration for this encryption consumer is: {0}. There was no data encryption method found in the configuration. The Algorithm Suite assertion in the policy might not be valid. Verify that a valid Algorithm Suite is specified in the application security policy. security.wssecurity.PrivateConsumerConfig.s18=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} Reference to message parts are required in order to retrieve the signature algorithms from Policy. This could be an error in the bindings. Verify that there are message parts to be signed on the application security bindings. security.wssecurity.PrivateConsumerConfig.s17=CWWSS5366E: Configuration information about the signing key is missing. The current configuration for this signature consumer is: {0}. There is no configuration found for the signing key. There might be key bindings information missing in the application security bindings. Verify that the key bindings configuration for signing key on the application security bindings are correct. security.wssecurity.PrivateConsumerConfig.s16=CWWSS5365E: The Caller identity for the Caller configuration is null. The caller configuration is: {0} 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. Verify that the application security bindings are correct for Caller configuration. security.wssecurity.PrivateConsumerConfig.s15=CWWSS5364E: The {0} key encryption method is not valid. An unsupported key encryption method was specified. Possible causes are that the application security policy has specified a not valid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies. Check the security policy for both server and client applications and ensure that the Algorithm Suite assertions are valid and compatible. security.wssecurity.WSSContextManagerImpl.s02=CWWSS7036E: [{0}] :: is not supported on Websphere Server. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateConsumerConfig.s14=CWWSS5363E: The {0} data encryption method is not valid. An unsupported encryption method was specified. Possible causes are that the application security policy has specified a not valid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies. Check the security policy for both server and client applications and ensure that the Algorithm Suite assertions are valid and compatible. security.wssecurity.WSSContextManagerImpl.s01=CWWSS7035E: [{0}] :: is not supported on Thinclient environment. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateConsumerConfig.s13=CWWSS5362E: The key information content consumer type is unknown. The current configuration of the key information content consumer is {0}. The key information content consumer type is unknown. A probable reason could be that there is an error in the key bindings. Verify that key bindings for the application security bindings are correct. security.wssecurity.PrivateConsumerConfig.s12=CWWSS5361E: The {0} transform is not valid. An unsupported transform method was specified. Possible causes are that the application security policy has specified a not valid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies. Check the security policy for both server and client applications and ensure that the Algorithm Suite assertions are valid and compatible. security.wssecurity.PrivateConsumerConfig.s11=CWWSS5360E: The {0} digest method is not valid. An unsupported digest method was specified. Possible causes are that the application security policy has specified a not valid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies. Check the security policy for both server and client applications and ensure that the Algorithm Suite assertions are valid and compatible. security.wssecurity.CWWSS7540E=CWWSS7540E: The OneTimeUse or DoNotCacheCondition assertions are not supported. The SAML token contains OneTimeUse or DoNotCacheCondition assertions; however, these assertions are not supported. The SAML token provider must be configured to not include the OneTimeUse or the DoNotCacheCondition assertions, or set the validateOneTimeUse binding option to false. security.wssecurity.WSTrustCallbackHandler.renewSCT=CWWSS7223E: Renew of security context token fails with an exception : {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS8003E=CWWSS8003E: The SAML Response must contain a valid <Assertion>. The SAML Response must contain a valid <Assertion>. Check with your SAML identity provider, and ensure it emits a valid <Assertion>. security.wssecurity.CWWSS8039E=CWWSS8039E: No realm was defined in the SAML attributes. A realm is required but was not found in the SAML attributes. Define a SAML Attribute as realm in TAI. security.wssecurity.PolicyInOutboundConfig.s29=CWWSS7333E: Found more than one supporting UsernameToken of type [{0}], used as trusted identity, in a policy paired with default bindings. Only two UsernameTokens, one configured as trusted identity and the other as a caller identity are allowed when using default bindings. Regenerate policy to use 2 UsernameTokens as caller identity and trusted identity. security.wssecurity.WSEC6834E=CWWSS6834E: The Java Authentication and Authorization Service (JAAS) login configuration name is not defined in the configuration: {0}. JAAS login configuration name is not defined. Check binding file and security.xml file for JAAS login name. security.wssecurity.PolicyInOutboundConfig.s28=CWWSS7332E: Found more than one supporting UsernameToken of type [{0}], used as caller identity, in a policy paired with default bindings. Only two UsernameTokens, one configured as trusted identity and the other as a caller identity are allowed when using default bindings. Regenerate policy to use 2 UsernameTokens as caller identity and trusted identity. security.wssecurity.PolicyInOutboundConfig.s27=CWWSS7330E: Can not locate signature bindings for the required integrity with reference name {0}. After looking at bindings, no signature bindings were found for the integral part with the specified reference name in the policy. Regenerate bindings so this integral part specified in the policy has a correctly defined signature binding. security.wssecurity.PolicyInOutboundConfig.s26=CWWSS7329E: Can not locate encryption bindings for the confidential part with reference name {0}. After looking at bindings, no encryption bindings were found for the confidential part with the specified reference name in the policy. Regenerate bindings so this confidential part specified in the policy has a correctly defined encryption binding. security.wssecurity.PolicyInOutboundConfig.s25=CWWSS7324E: Found more than one supporting token of type [{0}] in policy using default bindings. This is not allowed. In default bindings, we allow only a single supporting token of this type in the policy. Regenerate the policy so only one supporting token of this type is in the policy. security.wssecurity.PolicyInOutboundConfig.s24=CWWSS7305E: More than 2 UsernameToken assertions of type[{0}] were found in the policy when using default bindings. A maximum of 2 UsernameTokens of the same type are allowed in the policy when using default bindings. The maximum of 2 is only allowed when setting up one UsernameToken as a trustedId, and another one as a callerId. Correct the policy so a maximum of 2 SupportingToken UsernameToken assertions of the same type are found in the policy. security.wssecurity.PolicyInOutboundConfig.s23=CWWSS7286W: Cannot sign SignatureConfirmation element because nothing else on the message is signed. The policy file specifies no parts to be signed. The SignatureConfirmation element will not be signed. Correct the policy file and regenerate the file. security.wssecurity.PolicyInOutboundConfig.s22=CWWSS7285W: Cannot encrypt SignatureConfirmation element because nothing else on the message is encrypted. The policy file specifies no parts to be encrypted. The SignatureConfirmation element will not be encrypted. Correct the policy file and regenerate the file. security.wssecurity.PolicyInOutboundConfig.s21=CWWSS7278E: Token with type [{0}] was already defined. The policy file contains more than one token with the same type. Duplicate tokens are not allowed. Correct the policy file and regenerate the file. security.wssecurity.PolicyInOutboundConfig.s20=CWWSS7277E: The token consumer with type [{0}] must define a JAAS configuration. The token consumer did not define a JAAS configuration. Define a JAAS configuration for the token consumer in the binding file and regenerate the file. security.wssecurity.TimestampDialectElementSelector.s01=CWWSS5700E: There is no wsu:Timestamp to be moved. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateConsumerConfig.s09=CWWSS5358E: The {0} signature method is not valid. An unsupported signature method was specified. Possible causes are that the application security policy has specified a not valid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies. Check the security policy for both server and client applications and ensure that the Algorithm Suite assertions are valid and compatible. security.wssecurity.PrivateConsumerConfig.s08=CWWSS5357E: The {0} canonicalization method is not valid. An unsupported canonicalization method was specified. Possible causes are that the application security policy has specified a not valid Algorithm Suite assertion, or that the client and server have incompatible Algorithm Suite assertions in their policies. Check the security policy for both server and client applications and ensure that the Algorithm Suite assertions are valid and compatible. security.wssecurity.WSEC6833W=CWWSS6833W: Unknown element {0} in the {1} element. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateConsumerConfig.s05=CWWSS5354E: The {0} dialect value is unknown. This dialect value exists in the following configuration string: {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateConsumerConfig.s04=CWWSS5353E: Null is not allowed for the XPath expression in the {0} assertion. No XPath expression was specified on an XPath element in the specified assertion in the policy. Verify that all XPath elements in the specified assertion in the policy contain valid XPath expressions. security.wssecurity.SCTConsumeLoginModule.missingDKT=CWWSS7211E: Cannot find derived key token with id [{0}] in the subject This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateConsumerConfig.s03=CWWSS5352E: The {0} keyword is used, but it is unknown. The keyword is used in the following expression: {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PrivateConsumerConfig.s01=CWWSS5350E: The following configuration is not valid: {0} The security configuration for this service is not valid. Check that the specified policy and bindings for this service are correct. security.wssecurity.WSEC5189W=CWWSS5189W: The certificate, which is owned by {0}, uses the {1} alias, and is located in the {2} keystore,expires in {3} days. A certificate is about to expire in the keystore. Open the keystore and validate the expiration dates for all of the certificates in the keystore. Generate new certificates, if necessary. security.wssecurity.CWWSS8002E=CWWSS8002E: The StatusCode element with value of [{0}] is invalid. A "Success" StatusCode value is required. Check with your SAML identity provider, and ensure it emits the Success StatusCode element in the Status element in the corresponding SAML Response. security.wssecurity.CWWSS8038E=CWWSS8038E: TAI custom property realmNameRange is required if TAI custom property realmName is configured. TAI custom property realmNameRange is required if TAI custom property realmName is configured. Add TAI custom property realmNameRange if TAI custom property realmName is configured. security.wssecurity.PolicyInOutboundConfig.s19=CWWSS7276E: The Value Type for the token consumer [{0}] is null. A null value is not allowed for the Value Type for the token consumer. Specify a valid Value Type and regenerate the binding file. security.wssecurity.PolicyInOutboundConfig.s18=CWWSS7275E: The assertion [{0}] is not valid with already specified assertion [{1}]. The two specified assertions are not valid together. Only one of them should be specified in the policy. Correct the policy file and regenerate the file. security.wssecurity.PolicyInOutboundConfig.s17=CWWSS7274E: The token generator with type [{0}] must define a JAAS configuration. The token generator did not define a JAAS configuration. Define a JAAS configuration for the token generator in the binding file and regenerate the file. security.wssecurity.PolicyInOutboundConfig.s16=CWWSS7273E: The security token with type [{0}] references a token generator with type [{1}]. The token types need to match. Correct the token type in either the policy file or binding file and regenerate the file. security.wssecurity.PolicyInOutboundConfig.s15=CWWSS7272E: The Value Type for the token generator [{0}] is null. A null value is not allowed for the Value Type for the token generator. Specify a valid Value Type and regenerate the binding file. security.wssecurity.PolicyInOutboundConfig.s14=CWWSS7271E: The Trust13 policy assertion [{0}] is not valid or is not supported. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInOutboundConfig.s13=CWWSS7270E: Protection Token assertion found when a Encryption Token assertion or Signature Token assertion was already defined. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInOutboundConfig.s12=CWWSS7269E: Signature Token assertion found when a Protection Token assertion was already defined. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInOutboundConfig.s11=CWWSS7268E: Encryption Token assertion found when a Protection Token assertion was already defined. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInOutboundConfig.s10=CWWSS7267W: Duplicate XPath element in encryptedElements will be ignored: [{0}] The policy file contains multiple XPath elements in encryptedElements that are identical. The element will only be encrypted once. No user action is required. security.wssecurity.CWWSS8037W=CWWSS8037W: WebSphere Application Server Dynamic Cache is required for replay detection. WebSphere Application Server Dynamic Cache is configured to prevent replay detection, however Dynamic Cache could not be created. Verify that the WebSphere Application Server Dynamic Cache is enabled. security.wssecurity.CWWSS8001E=CWWSS8001E: The response does not have a StatusCode element. A StatusCode element is a required element that represents the status of the activity carried out in the response to the corresponding request. Check with your SAML identity provider, and ensure it emits the StatusCode element in the Status element in the corresponding SAML Response. security.wssecurity.PolicyInOutboundConfig.s09=CWWSS7266W: Duplicate XPath element in signedElements will be ignored: [{0}] The policy file contains multiple XPath elements in signedElements that are identical. The element will only be signed once. No user action is required. security.wssecurity.WSEC6832E=CWWSS6832E: More than one wsse:Security elements to be processed. Only one wsse:Security element is allowed. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PolicyInOutboundConfig.s08=CWWSS7256E: Policy assertion [{0}] is not allowed. More than one token reference assertion was specified for a token. Only one of the following token reference assertions may be specified for a token: RequireKeyIdentifierReference, RequireEmbeddedTokenReference, RequireIssuerSerialReference, RequireThumbprintReference. Regenerate the policy file. security.wssecurity.PolicyInOutboundConfig.s07=CWWSS7252E: GSS Kerberos Version 5 AP-REQ token assertion found when Kerberos Version 5 AP-REQ was already defined. Two Kerberos version assertions have been defined in the policy. Remove one of the assertions from the policy and use only one Kerberos version. security.wssecurity.PolicyInOutboundConfig.s06=CWWSS7251E: Kerberos Version 5 AP-REQ token assertion found when GSS Kerberos Version 5 AP-REQ was already defined. Two Kerberos version assertions have been defined in the policy. Remove one of the assertions from the policy and use only one Kerberos version. security.wssecurity.PolicyInOutboundConfig.s05=CWWSS7250W: Unsupported assertion for Kerberos, [{0}], found. An unsupported assertion has been added to the Kerberos Token assertion. Remove the unsupported assertion from the Kerberos Token assertion. security.wssecurity.PolicyInOutboundConfig.s04=CWWSS7249E: Wss11 policy assertion [{0}] is not supported. The attached WS-PolicySet policy for web services security is not valid. Regenerate the policy file. security.wssecurity.PolicyInOutboundConfig.s03=CWWSS7248E: Wss10 policy assertion [{0}] is not supported. The attached WS-PolicySet policy for web services security is not valid. Regenerate the policy file. security.wssecurity.PolicyInOutboundConfig.s02=CWWSS7247E: Target namespace [{0}] is not supported for service policy. The attached WS-PolicySet policy for web services security is not valid. Regenerate the policy file. security.wssecurity.PolicyInOutboundConfig.s01=CWWSS7037W: Token Assertion for token of type [{0}] not supported. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyStoreManager.noKeyStoreRefAndStorePath=CWWSS7064E: Both KeyStore Reference and KeyStore Path are null. Incomplete keystore configuration was found, either KeyStore Reference or KeyStore Path must be specified, but not both at the same time. Check the keystore configuration in the binding and make sure either KeyStore Reference or KeyStore Path is specified. security.wssecurity.WSEC6831W=CWWSS6831W: The {0} milliseconds token cushion is less than the minimum. The minimum token cushion {1} milliseconds is used. The token cushion is less than the minimum. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.trust.client.rstc.action=CWWSS7526E: The specified request security token action [{0}] must match the existing action [{1}] in the request security token collection. The request security token cannot be added to the collection because the token action does not match the action of the existing requests in the collection. Ensure that the request security token action matches the action of existing requests in the collection. security.wssecurity.CWWSS8000E=CWWSS8000E: The response does not have a Status element. The response Status element contains a code that represents the status of the corresponding SAML request. The Status element is a required element in a response. Check with your SAML identity provider, and ensure it emits the Status element in the SAML Response. security.wssecurity.WSSFactorySOAPImpl.s04=CWWSS5494E: Unexpected error during the instantiation of {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSFactorySOAPImpl.s03=CWWSS5493E: Unable to obtain the classpath used for instantiation for {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS8036E=CWWSS8036E: A SAML assertion with ID [{0}] has already been received and processed. A SAML assertion should not be replayed. The current request has a SAML assertion that has already been found in a previous request. Ensure the Identity Provider does not generate a SAML assertion with a duplicated ID or resend the same SAML assertion more than once. security.wssecurity.WSSFactorySOAPImpl.s02=CWWSS5492E: Unsupported type of WS-Security component: {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSSFactorySOAPImpl.s01=CWWSS5491E: Unable to obtain the object type {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.trust.client.soapnamespace=CWWSS7517E: Invalid SOAP namespace [{0}]. The SOAP namespace specified in the trust client request is not valid. Specify a SOAP namespace that is supported by the trust client. security.wssecurity.STRDereferenceTransformer.s05=CWWSS5674E: The processing of the STR-Transform failed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.STRDereferenceTransformer.s04=CWWSS5673E: There was an unsupported type of URI: {0}, during the processing of the STR-Transform. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.STRDereferenceTransformer.s03=CWWSS5672E: Null is not allowed for the ID resolver during the processing of the STR-Transform. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC5187E=CWWSS5187E: The Application Server cannot instantiate the {0} class. The following exception occurred: {1} An internal class could not be instantiated. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.STRDereferenceTransformer.s02=CWWSS5671E: There was an unknown canonicalization method: {0}, during the processing of the STR-Transform. The AlgorithmSuite specified in the client policy and the server policy might not be compatible. Verify that the AlgorithmSuite specified in the client policy and the server policy are compatible. security.wssecurity.STRDereferenceTransformer.s01=CWWSS5670E: Null is not allowed for the canonicalization method during the processing of the STR-Transform. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6830W=CWWSS6830W: The token cache size {0} is not a valid integer. The default token cache size {1} is used. Use integer value as cache size. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS8035E=CWWSS8035E: Cannot convert the IP string [{0}] to an IP address. Conversion error occurred while converting the IP string to an IP address. Validate the IP string provided. security.wssecurity.WSSPolicy.s05=CWWSS7265E: The specified assertion [{0}] is not valid or not supported. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.WSSPolicy.s04=CWWSS7264E: Element [{0}] is not a valid policy assertion. The policy file contains an element that is not a known policy assertion. Verify that the policy file is correct. security.wssecurity.WSSPolicy.s03=CWWSS7263E: Policy namespace [{0}] is not valid because policy namespace [{1}] was already found. The policy file contains multiple namespaces. Only one namespace is allowed. Verify that the policy file is correct. security.wssecurity.WSSPolicy.s02=CWWSS7258E: The policy assertion [{0}] is not a valid SecureConversationToken assertion. The policy file contains a not valid SecureConversationToken assertion. Regenerate policy file with a valid SecureConversation token type. security.wssecurity.WSSPolicy.s01=CWWSS7257E: The policy assertion [{0}] is not a valid X509Token, Kerberos or UsernameToken assertion. The policy file contains a not valid X509Token, Kerberos or UsernameToken assertion. Regenerate policy file with a valid token type. security.wssecurity.PkiPathCallbackHandler.s02=CWWSS6621E: Decoding the binary token data that is sent in the message resulted in null. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PkiPathCallbackHandler.s01=CWWSS6620E: An exception occured during the handling of a Public Key Infrastructure (PKI) path. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.trust.client.wstnamespace=CWWSS7519E: Invalid WS-Trust namespace [{0}]. The WS-Addressing namespace specified is not a valid namespace. Specify a WS-Trust namespace that is supported by the trust client. security.wssecurity.WSEC5185W=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} The certificate could not be mapped to a valid user in the registry. 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. security.wssecurity.unsupport.callback=CWWSS0049E: The {0} CallbackHandler class does not support the {1} callback object. The CallbackHandler class does not support the specified Callback implementation. Verify the configuration specifies the correct CallbackHandler class and that the class is implemented correctly. security.wssecurity.CWWSS8034E=CWWSS8034E: Unknown host exception raised for IP address [{0}]. Could not obtain IP address. Validate the IP address range specified. security.wssecurity.WSEC6865E=CWWSS6865E: The specified context token cannot be renewed. Some context tokens cannot be renewed. Obtain a new context token. security.wssecurity.CWWSS8033E=CWWSS8033E: Malformed IP range specified. Found [{0}] rather than a wildcard. Bad IP range specfied. Must contain only wildcards after the first range. Ensure everything after the first range specified is a wildcard. security.wssecurity.WSEC6864E=CWWSS6864E: The provided context token has expired. The context token has expired. If the token is renewable, renew the context token. Otherwise, obtain a new context token. security.wssecurity.KeyInfoConsumer.getKey04=CWWSS6017E: The Key extraction fails because of an exception occurred during the key extraction. The exception is: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyInfoConsumer.getKey03=CWWSS6012E: All the attempts to resolve the key based on each Key Information failed. The last exception is: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.trust.client.serverresponse=CWWSS7534E: The response received from the trust service provider is invalid. The trust client received a response from the trust service provider that is not valid. Verify that the trust service provider address is correct, and the trust client is configured correctly for the specified trust service provider. security.wssecurity.CWWSS8032E=CWWSS8032E: The filter operator should be one of ''=='', ''!='', ''%='', ''>'' or ''<''. Operator used was [{0}]. The filter operator for SAML Web SSO is not valid. Check the WebSphere Application Server SAML TAI configuration, and ensure the filter operator is valid. security.wssecurity.WSEC6863E=CWWSS6863E: The specified source for the derivation is unknown. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.CWWSS8031E=CWWSS8031E: This TAI could not uniquely identify one Single-Sign-On partner for this request [{0}]. There are multiple Single-Sign-on partners configured for the request. Check the WebSphere Application Server SAML TAI configuration, and ensure the filter condition uniquely identifies one Single-Sign-On partner. security.wssecurity.PolicyInboundConfig.s43=CWWSS7348E: A total number of [{0}] protection tokens of the type [{1}] were configured in the policy. Only one and exactly one is required when specifying it as the caller. When a protection token type is specified as a caller, one and exactly one protection token of that type is allowed. Correct the policy and ensure that your policy has exactly one token of that protection token type. security.wssecurity.PolicyInboundConfig.s42=CWWSS7298E: Bindings with namespace [{0}] cannot support the specified configuration [{1}]. The specified configuration is not supported with the bindings version thats used Migrate bindings to a level that supports the configuration security.wssecurity.WSEC6862E=CWWSS6862E: Not all of the values that are associated with the security context token (SCT) are supported. Some of the values in the request that are associated with the security context token (SCT) are not supported. Refer to the information center for information on the supported values. security.wssecurity.PolicyInboundConfig.s41=CWWSS7337E: Can not find encryption bindings for specified confidential parts for an inbound message in the default bindings. Confidential parts were specified for inbound messages in the policy, but there was no matching encryption information on the inbound section of the default bindings. Regenerate the default bindings, so there are encryption bindings for the specified integral parts. security.wssecurity.PolicyInboundConfig.s40=CWWSS7336E: Can not find token consumer for encryption token in default bindings. Default bindings are missing the token consumer for the encryption token. Regenerate the default bindings, so there is a token consumer for the encryption token. security.wssecurity.WSEC5182E=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} The certificate is not valid. Verify that the certificate is a valid one and obtain a valid certificate if necessary. security.wssecurity.PolicyInboundConfig.s39=CWWSS7335E: Can not find signature bindings for specified integral parts for an inbound message in the default bindings. Integral parts were specified for inbound messages in the policy, but there was no matching signing information on the inbound section of the default bindings. Regenerate the default bindings, so there are signature bindings for the specified inbound integral parts. security.wssecurity.PolicyInboundConfig.s38=CWWSS7334E: Can not find token consumer for signing token in default bindings. Default bindings are missing the token consumer for the signing token. Regenerate the default bindings, so there is a token consumer for the signing token. security.wssecurity.PolicyInboundConfig.s37=CWWSS7331E: Two UsernameTokens of type [{0}], one used as a trustedId and the other as a callerId, were configured in policy and bindings, but they are not being used as caller. When using default bindings, we allow 2 UsernameTokens of the same type, only when being used as callers. Correct the default bindings, so these 2 UsernameTokens are used as callers, or to not use 2 UsernameTokens. security.wssecurity.PolicyInboundConfig.s36=CWWSS7327E: Did not find a token consumer for the supporting token of type [{0}]. A token consumer was not found in the bindings for the supporting token of this type. Correct the bindings so a token consumer for the supporting token in the policy is defined. security.wssecurity.CWWSS8030E=CWWSS8030E: The SAML response to [{0}] is not configured for this service provider. There is no AssertionConsumerService URL configured for the incoming SAML Response. Check the WebSphere Application Server SAML TAI configuration, and ensure it has the AssertionConsumerService URL configured. security.wssecurity.PolicyInboundConfig.s35=CWWSS7325E: Found two UsernameToken Token consumers, one configured as trusted id and the other as a caller id, of UsernameToken type [{0}] in the default bindings, but only one UsernameToken SupportingToken assertion in the policy. Do not know which consumer to chose. Two UsernameToken token consumers, one configured as trusted id and the other as a caller id were found, but do not know which one to use, as only one UsernameToken assertion was found in the policy. This is an ambiguous situation. Correct the policy so two Usernametoken SupportingToken assertions are in the policy, or remove one of the two UsernameToken token consumers from the default bindings. security.wssecurity.PolicyInboundConfig.s34=CWWSS7316E: More than one supporting token consumer of the same type found on the default bindings. Only one token consumer per supporting token type is allowed. Only one token consumer per supporting token type is allowed. Correct the default bindings so only one token consumer for each supporting token type is configured. security.wssecurity.WSEC6861E=CWWSS6861E: The requested context elements are not sufficient or not supported. The context token does not contain the required information. Refer to the information center for information on the required context information. security.wssecurity.PolicyInboundConfig.s31=CWWSS7303E: More than one supporting token consumer of the type [{0}] found on the default bindings. Only one token consumer per supporting token type is allowed. Only one token consumer per supporting token type is allowed. Correct the default bindings so only one token consumer for each supporting token type is configured. security.wssecurity.PolicyInboundConfig.s30=CWWSS7302E: More than one idAssertion UsernameToken consumer was found in the default bindings. In default bindings only one idAssertion UsernameToken consumer is allowed. Correct the bindings and ensure that it has exactly one idAssertion UsernameToken consumer. security.wssecurity.WSEC5181E=CWWSS5181E: The following certificate, which is owned by {0} with the {1} alias from the {2} keystore, has expired: {3} The certificate has expired. Verify the expiration date of the certificate and obtain a valid new certificate. security.wssecurity.PolicyInboundConfig.s29=CWWSS7301E: More than one trustedId UsernameToken consumer was found in the default bindings. In default bindings only one trustedId UsernameToken consumer is allowed. Correct the bindings and ensure that it has exactly one trustedId UsernameToken consumer. security.wssecurity.PolicyInboundConfig.s28=CWWSS7300E: A total number of [{0}] supporting tokens of the type [{1}] were configured in the policy. Only one and exactly one is required. When a supporting token type is specified as a caller, one and exactly one supporting token of that type is allowed. Correct the policy and ensure that your policy has exactly one token of that type. security.wssecurity.PolicyInboundConfig.s27=CWWSS7299E: A total number of [{0}] UsernameToken Supporting tokens were found in the policy. When using Username Tokens as a trusted id and an idAssertion, two and only two are required. Two and only two UsernameTokens Supporting tokens are allowed in policy when being used as a trusted id and an id assertion Correct the policy and ensure that your it has exactly two UsernameTokens. security.wssecurity.PolicyInboundConfig.s22=CWWSS7283E: The caller [{0}] does not have a matching protection or supporting token in the policy. A caller was defined that does not have a matching token in the policy. Remove the caller from the bindings, or add a supporting or protection token of the same type to the policy. security.wssecurity.WSEC6860E=CWWSS6860E: The requested renewal failed. The Application Server cannot renew the security token. Obtain a new security token. security.wssecurity.PolicyInboundConfig.s21=CWWSS7033E: An exception was caught formatting the following LDAP port number:{0} The format of the LDAP port number is wrong. Check the LDAP port number and make sure it is correct. security.wssecurity.PolicyInboundConfig.s20=CWWSS7032E: The policy assertion [{0}] is not a valid Trust10 QName assertion. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s19=CWWSS7031E: The policy assertion [{0}] is not a valid WSS11 QName assertion. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s18=CWWSS7030E: The policy assertion [{0}] is not a valid WSS10 QName assertion. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s17=CWWSS7029E: The policy assertion [{0}] is not a valid Supportingtoken QName assertion. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s16=CWWSS7028E: The policy assertion [{0}] is not a valid SymmetricBinding QName assertion. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s15=CWWSS7027E: Recipient Encryption Token assertion found when a Recipient Token assertion was already defined. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s14=CWWSS7026E: Initiator Encryption Token assertion found when an Initiator Token assertion was already defined. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s13=CWWSS7025E: Recipient Signature Token assertion found when a Recipient Token assertion was already defined. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s12=CWWSS7024E: Initiator Signature Token assertion found when an Initiator Token assertion was already defined. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s11=CWWSS7023E: Recipient Token assertion found when a Recipient Signature Token assertion was already defined. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s10=CWWSS7022E: Recipient Token assertion found when a Recipient Encryption Token assertion was already defined. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s09=CWWSS7021E: Initiator Token assertion found when an Initiator Token assertion was already defined. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s08=CWWSS7020E: Initiator Token assertion found when an Initiator Encryption Token assertion was already defined. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s07=CWWSS7019E: The policy assertion [{0}] is not a valid AsymmetricBinding QName assertion. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s06=CWWSS7018E: The policy assertion [{0}] is not a valid sign/encrypt part/element. The policy file contains an assertion that is not valid or not supported. Refer to the documentation to determine the valid and supported assertions. security.wssecurity.PolicyInboundConfig.s05=CWWSS7017E: Actor URI validation failed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PolicyInboundConfig.s04=CWWSS7016E: Exception received from FileInputStream. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PolicyInboundConfig.s03=CWWSS7015E: Exception received from JAXB. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PolicyInboundConfig.s02=CWWSS7014E: No WS-Security Bindings found. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.PolicyInboundConfig.s01=CWWSS7013E: PolicyInboundConfig(String bindFilename, String policyFilename, boolean isRequest, ClassLoader appClassLoader,WSSecurityDefaultConfiguration defaultConfiguration): [{0}] This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyStoreKeyLocator.getKey02=CWWSS6092E: Unknown key usage type: key type={0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.DOMUtil.sconf11=CWWSS5048E: One of the {0} elements is required. None of required elements with the specific namespaces exist in the SOAP message. 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. security.wssecurity.DOMUtil.sconf10=CWWSS5047E: {0}/@{1} attribute is required. The required attribute does not exist in the XML element. 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. security.wssecurity.WSSInboundBinding.s01=CWWSS7306E: Order is a required attribute for callers in the binding namespace [{0}]. A caller was configured without an order attribute in a namespace requiring its use. Regenerate the binding file with correct caller order attributes set. security.wssecurity.DOMUtil.sconf09=CWWSS5046E: One or more {0} elements are required. One or more of the XML elements with a specific namespace do not exist in the SOAP message. 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. security.wssecurity.SCTGenerateLoginModule.getAxisService=CWWSS7200E: Unable to create AxisService from ServiceEndpointAddress : {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.DOMUtil.sconf03=CWWSS5043E: One {0} element is required. The XML element with a specific namespace does not exist in the SOAP message. 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. security.wssecurity.EncryptionGenerator.s15=CWWSS5615E: Null is not allowed as the parent element of the enc:EncryptedKey or the enc:EncryptedData element. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.EncryptionGenerator.s14=CWWSS5614E: Constructing the EncryptionMethod element produced the following exception: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.EncryptionGenerator.s13=CWWSS5613E: Encrypting the key for data encryption produced the following exception: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.EncryptionGenerator.s12=CWWSS5612E: Encrypting the data produced the following exception: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.EncryptionGenerator.s11=CWWSS5611E: Generating the key for data encryption produced the following exception: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.EncryptionGenerator.s01=CWWSS5610E: Unable to create the {0} element. The exception is: {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.KeyIdContentConsumer.getEncodingType02=CWWSS6052E: The EncodingType attribute is not found. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.load.collectioncertstore.failed=CWWSS0021E: The Application Server failed to load the {0} CollectionCertStore configuration. The exception is: {1} 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. The CollectionCertStore configuration might be corrupted or missing. Verify that the collection certificate store is configured properly in the binding. security.wssecurity.X509ConsumeLoginModule.s01=CWWSS7346E: The trust anchor path is null. It is required when trustAnyCertificate is not specified. The trust anchor could not be loaded because the path is null. Verify the trust anchor path is specified in the bindings, or specify trustAnyCertificate. security.wssecurity.TokenSerialize.s03=CWWSS7233E: The security subject is not returned from login process. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.TokenSerialize.s02=CWWSS7232E: The WS-Security SelfManagedData de-serialization fails. The exception is {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.TokenSerialize.s01=CWWSS7231E: The WS-Security SelfManagedData serialization fails. The exception is {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7243E=CWWSS7243E: The security token service (STS) must only return 1 response. It returned {0} responses. The Application Server encountered an incorrect number of responses from the STS. No user action is required. security.wssecurity.WSEC0139W=CWWSS0139W: The timestamp timeout value of {0} seconds is less than the minimum. The minimum value of {1} seconds is used instead. The specified value for the timestamp timeout is less than the minimum value that is required. 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. security.wssecurity.WSEC7242E=CWWSS7242E: The RequestSecurityToken element is missing the required {0} header element. The Application Server could not successfully process the RequestSecurityToken because of a missing header element. Specify the missing header element in the RequestSecurityToken and resubmit the request. security.wssecurity.SecureConversationCacheHelper.s03=CWWSS7120E: EndpointReference is null. WS-Address might be not enabled. It is required for Secure Conversation. WS-Address might not be enabled. It is required for Secure Conversation. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SecureConversationCacheHelper.s02=CWWSS7119E: ConfigurationContext in MessageContext is null. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SecureConversationCacheHelper.s01=CWWSS7118E: AxisConfiguration in MessageContext is null. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.X509IssuerContentConsumer.getX509Data01=CWWSS6081E: The X509Data Element was not processed. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC7241E=CWWSS7241E: The RequestSecurityToken element contains an invalid {0} element. The Application Server encountered a not valid element while processing the RequestSecurityToken. Remove the not valid element from the RequestSecurityToken and resubmit the request. security.wssecurity.RequestReceiverConfig.sconf02=CWWSS5042E: Two or more {0} elements exist. Multiple XML elements exist in the SOAP message, where only one XML element with a specific namespace is expected. 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. security.wssecurity.WSEC7240E=CWWSS7240E: The Application Server encountered multiple {0} elements in the token request. The element can only occur once in the token request. Remove the extra elements from the token request and resubmit the request. security.wssecurity.LTPAConsumeLoginModule.invalidValueType=CWWSS7307E: Unsupported Value Type. Expecting the following Value Type [{0}], but found [{1}]. The Value Type on the token in the message does not match the token consumer configuration. Check and correct the Value Type information in the bindings. The token consumer and token generator configuration must both specify valid Value Types that are compatible. security.wssecurity.CWWSS7539E=CWWSS7539E: The issued token uses the [{0}] confirmation method. This method is different from the [{1}] method that is specified in the policy. The WS-PolicySet policy for Web services security that is attached to the service specifies a SAML confirmation method that is different from the method used by the issued token. Revise your configuration to ensure the confirmation method for the attached WS-PolicySet corresponds to the issued token. security.wssecurity.cannot.load.resource=CWWSS0009W: The Application Server configuration utilities cannot load the resource file for the error messages. The exception is {0} 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. Verify that the message catalog exists in the correct location. security.wssecurity.TimestampChecker.s02=CWWSS5731E: A required timestamp is not found in the message part [{0}]. The policy expected the specified message part to contain a Timestamp element. Verify that the policies on both the client and the server specify that a Timestamp is required for the specified message part. security.wssecurity.TimestampChecker.s01=CWWSS5730E: A required timestamp is not found. The policy expected a Timestamp header to be found in the message. Verify that the policies on both the client and the server specify that a Timestamp is required on the message. security.wssecurity.EmbeddedContentConsumer.getEmbeddedToken02=CWWSS6042E: The Id attribute is not found. The Embedded key id is missing If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.ConfidentialDialectElementSelector.s03=CWWSS5697E: Null is not allowed as the value when selecting elements. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.ConfidentialDialectElementSelector.s02=CWWSS5696E: Null is not allowed as the node. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.ConfidentialDialectElementSelector.s01=CWWSS5695E: The encrypting data object must contain the timestamp or nonce: {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SignatureConsumer.s12=CWWSS5625E: All the attempts based on each Reference failed. The last exception is: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SignatureConsumer.s11=CWWSS5624E: Null is not allowed as the target element. The {0} element was expected when consuming the message. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC0133E=CWWSS0133E: WSSecurityPlatformContextFactory.setServer() is already initialized. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6829W=CWWSS6829W: The {0} token cache size is less than the allowed minimum {1}. The default token cache size {2} is used. The token cache size is less than the allowed minimum. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.SignatureConsumer.s02=CWWSS5621E: There is an unsupported signed part: URI={0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.NonceUtil.s08=CWWSS5327E: A null value is not allowed for the created time of the time stamp. The Application Server expected the wsu:Created element. The time stamp must have a wsu:Created element indicating the time of message creation. 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. security.wssecurity.SignatureConsumer.s01=CWWSS5620E: Signature verification failed: {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.NonceUtil.s07=CWWSS5326E: A null value is not allowed for the timestamp. The Application Server expected the wsu:Timestamp element. A time stamp was expected in the message but it was not found. Verify that the security policies and bindings for the application sending the message are configured so a time stamp is added to its messages. security.wssecurity.NonceUtil.s06=CWWSS5325E: A null value is not allowed for the nonce. The Application Server expected the wsse:Nonce element. A nonce was expected in the message but it was not found. Verify that the security policies and bindings for the application sending the message are configured so a nonce is added to its messages. security.wssecurity.CWWSS7535E=CWWSS7535E: {0} Failed to load SAML Issuer Config Data property file: {1} The SAML issuer configuration data property file did not load. Verify that a valid SAML property file exists at the specified location. security.wssecurity.NonceUtil.s05=CWWSS5324E: The {0} time stamp type is not supported. The expected type is {1}. A check for the time stamp type has determined that the type is not supported. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.NonceUtil.s04=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}. 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. 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. security.wssecurity.NonceUtil.s03=CWWSS5322E: The Application Server cannot parse the time stamp value. The following exception occurred: {0} There has been a problem parsing a time stamp value found in the message. Could be timestamp is in an incorrect format. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.NonceUtil.s02=CWWSS5321E: A duplicate nonce, which is a randomly generated value, has been found. A nonce value should be unique on each message. The current message has a nonce that has already been found in a previous message. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.NonceUtil.s01=CWWSS5320E: The Application Server cannot hex decode the nonce, which is a randomly generated value. The following exception occurred: {0}. There was a problem parsing a nonce value. The nonce in the message is in an incorrect format. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC0168E=CWWSS0168E: No WebSphere Credential (WSCredential) was found in the Lightweight Third-Party Authentication (LTPA) propagation token. A WebSphere Credential is expected in the Lightweight Third-Party Authentication (LTPA) propagation token and none is found. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6828W=CWWSS6828W: The {0} seconds token cache timeout is less than the minimum. The minimum token cache timeout {1} seconds is used. The token cache timeout is less than the minimum. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.trust.client.key=CWWSS7525E: The specified trust client settings key [{0}] is invalid. The trust client settings key is not one of the predefined keys required for the trust client. Specify a trust client settings key from the list of predefined trust client keys. security.wssecurity.WSEC0131E=CWWSS0131E: The {0} CallbackHandler is not allowed to prompt on the Application Server. 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. Use a CallbackHandler that is supported for the Application Server. security.wssecurity.WSEC6719E=CWWSS6719E: The Qualified Name (QName) {0} was not found. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC6827W=CWWSS6827W: The certificate cache size {0} is not a valid integer. The default cache size {1} is used. Use integer number as cache size. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . security.wssecurity.WSEC0130W=CWWSS0130W: The {0} prompt CallbackHandler without specifying basic authentication information in the binding is not supported for an application running on the Application Server. 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. Use a CallbackHandler that is supported for the Application Server.