Express (Distributed operating systems), v8.0 > Reference > Messages
WSEC
WSEC0001E: Error trying to find Security Server. The exception is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0002E: Error trying to initial naming context. The exception is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0003E: Unable to expand string {0}.
Explanation The variable used in cannot be expanded, this may be due to the variable is not defined in the variables.xml. Action Check the variables.xml to make sure that the variable used is defined.
WSEC0004E: Cannot obtain the process type during initialization.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0005E: Web Services Security runtime service failed to start. The exception is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0006W: Cannot load cell level Web Services Security configuration file {0} from repository.
Explanation This exception is unexpected. The cause is not immediately known. Action The cell level Web Services Security configuration document might be corrupted or missing. Contact your service representative.
WSEC0007W: Server level Web Services Security configuration file {0} is not found.
Explanation The server level Web Services Security configuration document might be corrupted or missing. The file provides the default binding configuration for Web Services Security. Action If you would like to use the default bindings information, copy ws-security.xml from the ${USER_INSTALL_ROOT}/config/templates directory.
WSEC0008E: Cannot obtain LoginMapping object from the configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0009W: Cannot load resource file for messages. The exception is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0010E: Cannot obtain TrustedIDEvaluator object from the configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0011E: Cannot obtain KeyLocator object from the configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0012E: Cannot obtain LdapCertStore object from the configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0013E: Cannot obtain LdapServer object from the configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0014E: Cannot obtain CollectionCertStore object from the configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0015E: Cannot obtain X509Certificates object from the configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0016E: Failed to load LoginMapping {0}. The exception is {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action The LoginMapping in configuration document might be corrupted or missing. Contact your service representative.
WSEC0017E: Failed to load TrustAnchor {0}. The exception is {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action The TrustAnchor in configuration document might be corrupted or missing. Contact your service representative.
WSEC0018E: Failed to load TrustedIDEvaluator {0}. The exception is {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action The TrustedIDEvaluator in configuration document might be corrupted or missing. Contact your service representative.
WSEC0019E: Failed to load KeyLocator {0}. The exception is {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action The KeyLocator in configuration document might be corrupted or missing. Contact your service representative.
WSEC0020E: Failed to load LDAPCertStore {0}. The exception is {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action The LDAPCertStore in configuration document might be corrupted or missing. Contact your service representative.
WSEC0021E: Failed to load CollectionCertStore {0}. The exception is {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action The CollectionCertStore in configuration document might be corrupted or missing. Contact your service representative.
WSEC0022E: The certificate path name of CollectionCertStore {0} is null.
Explanation This exception is unexpected. The cause is not immediately known. Action The CollectionCertStore in configuration document might be corrupted or missing. Contact your service representative.
WSEC0023E: Security Service is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0024E: Request Receiver Configuration is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0025E: Request Sender Configuration is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0026E: Response Sender Configuration is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0027E: Response Receiver Configuration is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0028E: was.install.root is not defined.
Explanation JVM System properties was.install.root is not defined. Action Specify the JVM System properties and try again.
WSEC0029E: Web Services Security client runtime service failed to start. The exception is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0030E: Cannot load client Web Services Security configuration from location: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action The client Web Services Security configuration document might be corrupted or missing.
WSEC0031E: Can not get ContextManager (ContextManager is null).
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0032E: There is no WSPrincipal in the initial sender subject.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0033W: More than one WSPrincipal found in the initial sender Subject, use the first one.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0034E: No initial sender found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0035E: No validated DN found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0036W: More than one WSCredential found in the authenticate Subject, use the first one.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0037W: More than one WSPrincipal found in the authenticate Subject, use the first one.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0038E: There is no WSCredential found in the authenticated subject.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0039E: There is no WSPrincipal found in the authenticated subject.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0040E: Inconsistent state, the login is not successful in the commit phase.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0041W: Committed state is true in commit phase, re-commit the changes again.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0042W: No Canonicalization / Transform algorithm defined for digital signature binding.
Explanation This is not a problem if AuthMethod is IDAssertion and IDType is X509Certificate. Action Verify your bindings.
WSEC0043W: No Signature algorithm defined for digital signature bindings.
Explanation This is not a problem if AuthMethod is IDAssertion and IDType is X509Certificate. Action Verify your bindings.
WSEC0044W: No Digest algorithm defined for digital signature bindings.
Explanation This is not a problem if AuthMethod is IDAssertion and IDType is X509Certificate. Action Verify your bindings.
WSEC0045E: Could not get path to the client ws-security.xml configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0046W: Client could not load default configuration {0}.
Explanation The client Web Services Security configuration document might be corrupted or missing. The file provides the default binding configuration for client Web Services Security. Action More info at:
WSEC0047E: Exception loading config: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0048W: Incomplete EncryptionInfo: {0} is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0049E: {0} does not support {1} callback.
Explanation The CallbackHandler implementation does not support the Callbcak. Action More info at:
WSEC0050W: {0} can not be expanded. The exception {1}.
Explanation The variable is not defined could be the possible cause. Action Check the variable is defined in the command line as JVM System Properties. If problem still persist after the variable is defined as JVM System Properties, contact your service representative.
WSEC0051E: RequiredIntegrity ref part invalid: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0052E: RequiredConfidentiality conf part invalid: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0053E: Integrity ref part invalid: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0054E: Confidentiality conf part invalid: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0055E: IDAssertion IDType invalid: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0056E: IDAssertion TrustMode invalid: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0057E: P[Cc]Binding Scope invalid: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0058E: CertPathSettings: If TrustAnyCertificate is not set, then TrustAnchor must be set.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0059E: CertPathSettings are required for receiver SigningInfo.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0060E: Name attribute must be set for SigningKey.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0061E: LocatorRef attribute must be set for SigningKey.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0062E: SigningKey is required for sender SigningInfo.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0063E: Unable to open keystore for Trust Anchor Ref {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0064E: Trust Anchor Ref {0} not found in TrustAnchors.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0065E: CollectionCertStore: name attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0066E: CollectionCertStore: provider attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0067E: CollectionCertStore: must contain at least one X509Certificate.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0068E: LDAPCertStore: name attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0069E: LDAPCertStore: provider attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0070E: LDAPCertStore: LDAPServer must be specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0071E: LDAPServer: host attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0072E: LDAPServer: port attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0073E: Cert Store Ref {0} not found in CertStoreList.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0074E: EncryptionInfo: name attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0075E: EncryptionInfo: EncryptionKey must be specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0076E: EncryptionInfo: DataEncryptionMethod must be specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0077E: EncryptionKey: LocatorRef must be specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0078E: KeyLocator: classname attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0079E: Key Locator Ref {0} not found in KeyLocators.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0080E: Unable to open keystore {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0081E: Key: alias attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0082E: Key: keypass attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0083E: Key: name attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0084E: LoginMapping: AuthMethod must be specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0085E: LoginMapping: AuthMethod {0} is not valid.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0086E: LoginMapping: TokenValueType must be specified when AuthMethod is not one of the special types. The special types are "Signature", "IDAssertion" and "BasicAuth".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0087E: TokenValueType: URI attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0088E: TokenValueType: localName attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0089E: LoginMapping: ConfigName must be specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0090E: LoginMapping: CallbackHandlerFactory must be specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0091E: CallbackHandlerFactory: classname attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0092E: TrustedIDEvaluatorRef: ref attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0093E: TrustedIDEvaluator: classname attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0094E: TrustedIDEvaluator: name attribute is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0095E: Canonicalization algorithm {0} is not supported.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0096E: Digest algorithm {0} is not supported.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0097E: Signature algorithm {0} is not supported.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0098E: DataEncryption algorithm {0} is not supported.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0099E: KeyEncryption algorithm {0} is not supported.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0100E: LoginBinding: AuthMethod must be specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0101E: LoginBinding: AuthMethod {0} is not valid.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0102E: LoginBinding: TokenValueType must be specified when AuthMethod is "{0}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0103E: LoginBinding: CallbackHandler must be specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0104E: LoginConfig: AuthMethod must be specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0105E: LoginConfig: AuthMethod {0} is not valid.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0106W: Your application may have Web Services Security enabled. If it does, go to the Enterprise Application Management panels to configure the binding information for Web Services Security. The binding information for Web Services Security is not collected during application deployment. If it is not properly configured, the application may not start or be usable.
Explanation The Web Services Security binding information is not collected during application deployment. Action If the application is Web Services Security enabled, go to the Enterprise Application Management panels or using wsadmin with scripting to configure the bindings.
WSEC0107E: If RequiredConfidentiality or Confidentiality is specified in the deployment descriptor file, EncryptionInfo must be specified in the bindings file.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0108E: If RequiredIntegrity or Integrity is specified in the deployment descriptor file, SigningInfo must be specified in the bindings file.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0109E: If RequiredIntegrity or Integrity is specified in the deployment descriptor file, at least one SigningInfo element in the bindings file must specify all 3 algorithms (CanonicalizationMethod, DigestMethod and SignatureMethod).
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0110E: Refresh is not supported for client.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0111E: Failed to activate WebServicesSecurityAdmin MBean
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0112E: certStores.get( {0} ) returned a {1}, expected a CollectionCertStore or an LDAPCertStore.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0113W: Nonce (randomly generated value) is not supported for "{0}" authentication method(s).
Explanation Nonce (randomly generated value) is not supported for authentication method(s) other than "BasicAuth". Action Remove the nonce (randomly generated value) constraint or change the authentication method to "BasicAuth".
WSEC0114W: Nonce (randomly generated value) timestamp is not supported when nonce (randomly generated value) is disabled.
Explanation Nonce (randomly generated value) timestamp is only used when Nonce (randomly generated value) is enabled. Action Enabled Nonce (randomly generated value) constraint or remove Nonce (randomly generated value) timestamp constraint.
WSEC0115W: Exception occurred during parsing the Nonce (randomly generated value) cache timeout value {0}, default value {1} seconds is used instead.
Explanation The format of the Nonce (randomly generated value) cache timeout value is not an integer Action Change the Nonce (randomly generated value) cache timeout value to an integer. If problem still persist, contact your IBM services representative.
WSEC0116W: The Nonce (randomly generated value) cache timeout value {0} seconds is less than the minimum, the minimum value {1} seconds is used instead.
Explanation The specified Nonce (randomly generated value) cache timeout value is less than the minimum. Action Change the Nonce (randomly generated value) cache timeout value within the valid range. If problem still persist, contact your IBM services representative.
WSEC0117W: Exception occurred during parsing the Nonce (randomly generated value) max age value {0}, default value {1} seconds is used instead.
Explanation The format of the Nonce (randomly generated value) max age value is not an integer Action Change the Nonce (randomly generated value) max age value to an integer. If problem still persist, contact your IBM services representative.
WSEC0118W: The Nonce (randomly generated value) max age value {0} seconds is not within the valid range of minimum {1} seconds and maximum {2} seconds, the minimum value {3} seconds is used instead.
Explanation The specified Nonce (randomly generated value) max age value is not within the valid range Action Change the Nonce (randomly generated value) max age value wihtin the valid range. If problem still persist, contact your IBM services representative.
WSEC0119W: The Nonce (randomly generated value) clock skew value {0} seconds is not within the valid range of minimum {1} seconds and maximum {2} seconds, the minimum value {3} seconds is used instead.
Explanation The specified Nonce (randomly generated value) clock skew value is not within the valid range Action Change the Nonce (randomly generated value) clock skew value wihtin the valid range. If problem still persist, contact your IBM services representative.
WSEC0120W: Exception occurred during parsing the Nonce (randomly generated value) clock skew value {0}, default value {1} seconds is used instead.
Explanation The format of the Nonce (randomly generated value) clock skew value is not an integer Action Change the Nonce (randomly generated value) clock skew value to an integer. If problem still persist, contact your IBM services representative.
WSEC0121E: The Nonce (randomly generated value) is null or zero length.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0122E: The Nonce (randomly generated value) cache is null or not initialized
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0123E: The Nonce (randomly generated value) cache is not available on the standalone managed client.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0124W: The specified Nonce (randomly generated value) cache size {0} is less than the allowed minimum {1}, the default {2} is used.
Explanation The specified Nonce (randomly generated value) cache size is less than the minimum. Action Specify the cache size greater the minimum.
WSEC0125E: The Nonce (randomly generated value) Manager is not initialized.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0126E: Error in initializing the Nonce (randomly generated value) Manager, exception {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0127W: The specified Nonce (randomly generated value) length {0} is less than the allowed minimum {1}, the default {2} is used.
Explanation The specified Nonce (randomly generated value) length is less than the minimum. Action Specify the nonce (randomly generated value) length greater the minimum.
WSEC0128W: There is no basic authentication data in the binding file and no run as identity, hence LTPA token could not be obtained.
Explanation LTPA token cannot be obtained because there is no basic authentication data in the IBM extension application binding file and no run as identity in the current security context. Either make sure an identity is established or the basic authentication data is specified in the binding file. If basic authentication data is specified, the LTPA CallbackHandler will use it to create the LTPA token rather than obtaining the LTPA token from the run as identity. Action Either make sure an identity is established or the basic authentication data is specified in the IBM extension application binding file.
WSEC0129W: {0} CallbackHandler implementation is not supported for Java Client.
Explanation The CallbackHandler is not supported for Java Client, if this is used in Java Client, it may not function properly. Action Use a CallbackHandler that is supported for Java Client.
WSEC0130W: Prompt {0} CallbackHandler with no basic authentication information specified in the binding is not supported for application running on application server.
Explanation The CallbackHandler with prompt behavior is not supported for application running on application server. If this is used in an application server, it may cause application server to hang. Action Use a CallbackHandler that is supported for application server.
WSEC0131E: {0} CallbackHandler is not allowed to prompt on application server.
Explanation The CallbackHandler with prompt behavior is not supported for application running on application server. If this is used in an application server, it may cause application server to hang. Action Use a CallbackHandler that is supported for application server.
WSEC0132E: Fail to update SOAP message, exception {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0133E: WSSecurityPlatformContextFactory.setServer() is already initialized.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0134E: Cannot obtain CRLs object from the configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0135E: The configuration loader is unable to load the default generator configuration, exception message: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0136E: The configuration loader is unable to load the default consumer configuration, exception message: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0137E: The WSSecurityDefaultGeneratorConfig constructor is unable to load the keystore file, exception message: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0138W: The WSSecurityDefaultGeneratorConfig constructor is unable to retrieve a certificate from the keystore file, exception message: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0139W: The timestamp timeout value {0} seconds is less than the minimum, the minimum value {1} seconds is used instead.
Explanation The specified timestamp timeout value is less than the minimum. Action Change the timestamp timeout value within the valid range. If problem still persist, contact your IBM services representative.
WSEC0140W: Exception occurred during parsing the timestamp max age value {0}, default value {1} seconds is used instead.
Explanation The format of the timestamp max age value is not an integer Action Change the timestamp max age value to an integer. If problem still persist, contact your IBM services representative.
WSEC0141W: The timestamp max age value {0} seconds is not within the valid range of minimum {1} seconds and maximum {2} seconds, the minimum value {3} seconds is used instead.
Explanation The specified timestamp max age value is not within the valid range Action Change the timestamp max age value wihtin the valid range. If problem still persist, contact your IBM services representative.
WSEC0142W: The timestamp clock skew value {0} seconds is not within the valid range of minimum {1} seconds and maximum {2} seconds, the minimum value {3} seconds is used instead.
Explanation The specified timestamp clock skew value is not within the valid range Action Change the Nonce timestamp clock skew value wihtin the valid range. If problem still persist, contact your IBM services representative.
WSEC0143W: Exception occurred during parsing the timestamp clock skew value {0}, default value {1} seconds is used instead.
Explanation The format of the timestamp clock skew value is not an integer Action Change the timestamp clock skew value to an integer. If problem still persist, contact your IBM services representative.
WSEC0144W: Exception occurred during parsing the timestamp cache timeout value {0}, default value {1} seconds is used instead.
Explanation The format of the timestamp cache timeout value is not an integer Action Change the timestamp cache timeout value to an integer. If problem still persist, contact your IBM services representative.
WSEC0145E: Failed to activate the WebServicesSecurityAlgorithmHelper MBean
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0146E: Unable to add pluggable algorithm factory {0}. Algorithm mapping is not supported when WAS is in FIPS mode.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0147E: Unable to add pluggable algorithm factory {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0148E: The WAS is in FIPS mode and an algorithm that is not FIPS compliant was found in the default configuration (file ws-security.xml). The algorith method type is {0} and the algorith URI is {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0149W: The WAS is in FIPS mode and an algorithm that is not FIPS compliant was found in the web services security configuration for application {0}. The module name is {1} and the web services port name is {2}. The algorithm is of type {3} and the algorithm URI is {4}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0150E: An error occurred trying to read the FIPS compliant algorithms, so no FIPS algorithm validation will be performed during application deployment. The exception received was {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0151W: The {0} callback handler with no basic authentication information specified in the binding may fail to obtain an LTPA token unless one can be obtained from the run-as identity.
Explanation This callback handler will try first to obtain an LTPA token using the basic authentication information specified in the binding file. If none was specified, it will then try to obtain the LTPA token from the run-as identity. Action If it is expected that the run-as identity will contain the proper LTPA token, no action is required. Otherwise, specify the proper basic authentication information in the binding file for the application.
WSEC0152E: Namespace {0} is not supported
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0153E: Unsupported callback
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0154E: {0} CallbackHandler implementation is not supported for Java Client.
Explanation The CallbackHandler is not supported for Java Client. If this is used in Java Client, it may not function properly. Action Use a CallbackHandler that is supported for Java Client.
WSEC0155E: Received CertificateEncodingException while trying to retrieve the byte array representation of an X.509 Certificate. The exception is: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0156E: Received exception while trying to get the expiration of a WSCredential. The exception is: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC0157W: The {0} algorithm is not supported by this version of the JDK. This algorithm will not be available to applications running on this JDK.
Explanation The RSA-OAEP algorithm is only supported by JDK 1.5 and later. Action 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 //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.w3.org/2001/04/xmlenc#rsa-1_5 algorithm instead.
WSEC0158I: Hardware Crypto Acceleration is enabled: {0}
Explanation Information only Action Information only
WSEC0159I: Hardware KeyStore is used: {0}
Explanation Information only Action Information only
WSEC0160E: The [{0}] token value type, which is specified in the Token Generator configuration is not valid. The valid token type or token types for the Token Generator [{1}] are [{2}].
Explanation The token value type specified in the Token Generator configuration is not a valid type for the Token Generator. Action Correct the Token Generator configuration with the valid token value type.
WSEC0161E: A Lightweight Third Party Authentication (LTPA) token is not found.
Explanation A Lightweight Third Party Authentication (LTPA) token is not found in the current security context. The possible causes are that an invocation Subject does not exist in the security context or a basic authentication is not specified in the LTPA Token Generator configuration. Action Make sure security is enabled and either there is an invocation subject established in the security context or basic authentication is specified in the Lightweight Third Party Authentication (LTPA) Token Generator configuration.
WSEC0162E: The [{0}] token value type, which is specified in the Token Consumer configuration is not valid. The valid token type or token types for the Token Consumer [{1}] are [{2}]
Explanation The token value type specified in the Token Consumer configuration is not a valid type for the Token Consumer. Action Correct the Token Consumer configuration with the valid token value type.
WSEC0163E: A Lightweight Third Party Authentication (LTPA) token is not found in the binary security token.
Explanation A Lightweight Third Party Authentication (LTPA) token is not found in the binary security token. The possible cause is that the client sent a null or zero length LTPA token. Action Make sure that the client LTPA Token Generator is properly configured and security is enabled on the client.
WSEC0164E: A value type is not found in the binary security token. The expected value type is [{0}]
Explanation There is a missing value type in the binary security token. Action Make sure that the client Token Generator is specified with the valid token value type.
WSEC0165E: The [{0}] token value type in the binary security token is not valid. The valid token type or token types for the Token Generator [{1}] are [{2}]
Explanation The token value type in the binary security token configuration is not a valid type for the Token Generator. Action Make sure that the client Token Generator is specified with the valid token value type.
WSEC0166E: Global security must be enabled in order to use the Web services security token propagation feature.
Explanation An attempt was made to use the Web services security token propagation feature, but global security was not enabled in the Application Server. Action Enable global security in the Application Server.
WSEC0167W: A username and password were configured together with the token propagation token type. The username and password will be used to login and token propagation will not be performed.
Explanation The login module can authenticate the user using the username/password supplied or perform token propagation, but not both. Action Configure the token generator to specify username/password or the token propagation token type, but not both.
WSEC0168E: No WSCredential was found in the LTPA token wrapper object.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5001I: Please input the keystore password for {0}.
Explanation None. This is information only. Action None. This is information only.
WSEC5002E: Unable to open the keystore file: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5003E: Unable to read the keystore file: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5004E: Unable to load the keystore file {0} due to {1}: {2}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5005E: Unable to get the key "{0}" from the keystore "{1}" due to {2}: {3}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5006E: TrustMode must be either "Signature" or "BasicAuth": {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5007E: Class "{0}" not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5008E: Unable to instantiate the class "{0}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5009E: Unable to access to the default constructor of the class "{0}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5010E: Invalid keystore. Check the keystore file is suitable for the parameter to PKIXBuilderParameters.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5011E: Unable to get the certificate "{0}" from the keystore "{1}" due to {2}: {3}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5012E: Option "{0}" must be specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5013E: Class "{0}" must be a subclass of "{1}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5014E: Unknown key usage name: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5015E: Invalid port number for LDAP server: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5016E: Algorithm "{0}" is not supported by CertStore.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5017E: Invalid algorithm parameter: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5018E: No such provider: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5019E: Unable to open an X509 certificate file: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5020E: Unable to create an X509 certificate factory: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5021E: Invalid OID(s) in {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5022E: "{0}" is not allowed as "{1}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5023E: None of X509Data elements in the Signature element is valid. Generated exceptions are as follows: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5024E: LoginMapping element for AuthMethod "{0}" not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5025E: AuthMethod is "Signature" but no Integrity element found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5026E: IDType must be either "Username" ,"DN" or "X509Certificate": {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5027E: AuthMethod is "IDAssertion" but IDType is empty.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5028E: CallbackHandler is not specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5029E: AuthMethod contains "Signature" but RequiredIntegrity is empty.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5030E: TrustedIDEvaluator is null while TrustMode is not null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5031E: Internal error: Invalid LoginMapping object.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5032E: ConfigName is not specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5033E: CallbackHandlerFactory is not specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5034E: TokenValueType is not specified for custom AuthMethod.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5035E: Unable to retrieve the key from KeyLocator:
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5037I: Configuration objects are null, trying to read them from the file.
Explanation None. This is information only. Action None. This is information only.
WSEC5038I: Ignoring exception:
Explanation None. This is information only. Action None. This is information only.
WSEC5039I: URN of the target service found:
Explanation None. This is information only. Action None. This is information only.
WSEC5040I: Configuration object is as follows: {0}
Explanation None. This is information only. Action None. This is information only.
WSEC5041E: mustUnderstand does not match: existing value="{0}", new value="{1}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5042E: There are two or more "{0}" elements.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5043E: One "{0}" element is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5044E: AddCreateTimestamp/@expires has invalid format string: "{0}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5046E: One or more "{0}" elements required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5047E: "{0}/@{1}" attribute required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5048E: One of "{0}" elements required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5049E: The value of "part" attribute must be "body", "timestamp" or "securitytoken": {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5050E: "actorURI" attribute must be set if AddReceivedTimestamp/@flag is true.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5052E: Internal Error: Body request.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5053E: No URI attribute in "Reference" element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5054E: Unrecognizable Reference: URI="{0}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5055E: Unrecognizable Transform: Reference/@URI="{0}" Transform/@Algorithm="{1}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5056E: Unrecognizable XPath: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5057E: Unsupported signed part: URI="{0}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5058E: No valid keys or certificates.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5059E: No support for SecurityTokenReference pointing an external resource: URI="{0}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5060E: No valid token indicated by "#{0}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5061E: The SOAP Body is not signed.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5069E: Timestamp element is not signed.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5070E: All the attempts based on each SigningInfo failed. The last exception is: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5071E: No configuration for authentication.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5072E: No valid Signature on the token while TrustMode is "Signature".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5073E: UsernameToken has no Id attribute.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5074E: No valid signature by the trusted signer on UsernameToken while TrustMode is "Signature".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5075E: No security token found which satisfies any one of AuthMethods.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5076E: Password type "PasswordDigest" is not supported.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5077E: An exception in instantiating LoginContext: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5078E: Login failed: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5079E: No configuration for BinarySecurityToken.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5080E: No EncodingType found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5081E: HexBinary encoding is not implemented.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5082E: "{0}" encoding is not supported.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5083E: No ValueType found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5084E: Unable to decode the certificate: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5085E: Unable to build a valid CertPath: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5086E: An exception in processing X509v3 certificate: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5087W: BinarySecurityToken of ValueType "{0}" is not configured to be accepted.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5089E: Unable to instantiate CallbackHandler: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5090I: Enter your name:
Explanation None. This is information only. Action None. This is information only.
WSEC5091I: Enter your password:
Explanation None. This is information only. Action None. This is information only.
WSEC5092E: Unable to collect authentication information by CallbackHandler: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5093E: An exception in mapping credentials.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5094E: No UsernameToken of trusted user was found or the login failed for the user while TrustMode is "BasicAuth".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5095W: An X.509 <BinarySecurityToken> was ingored because of the absence of its verification settings.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5100E: Failed to obtain UserRegistry object.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5101W: Failed to obtain user name from X.509 certificate: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5102W: Failed to obtain default realm name.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5103E: No configuration for XML token.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5104W: XML token of "{0}" is not configured to be accepted.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5105W: UsernameToken is not configured to be accepted.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5107E: SOAP Body element not found
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5108E: Unknown encrypted part: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5109E: DataReference/@URI attribute not specified
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5110E: "EncryptionMethod/@Algorithm" attribute not specified
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5111E: Not allowed encryption method: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5112E: Not resolved ID: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5113E: EncryptionMethod element not specified
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5114E: Not EncryptedData element: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5115E: All the attempts based on each EncryptionInfo failed. The last exception is: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5116E: SOAP Body is not encrypted.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5117E: At least one UsernameToken is not encrypted.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5118E: The message was expired at {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5119E: Two or more Timestamp headers.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5120E: Unable to add wsu:Created because wsu:Timestamp header already exists.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5121E: No wsu:Received though the configuration requests to sign timestamp.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5122E: An exception while creating WS-Security configuration object: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5125E: Unexpected exception while initializing the receiver configuration: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5126E: WS-Security configuration has invalid item(s): {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5127E: Unable to extract XML document from SOAP message object. {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5128I: Although signature validation failed, ignoreing this because signature is not configured to be mandatory. The exception is: {0}
Explanation None. This is information only. Action None. This is information only.
WSEC5129E: An exception occurred while processing WS-Security message for target address {0}. The exception is {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5130W: An exception while processing SOAP fault message: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5131W: The server cannot find the Web service security header with actor: {0}
Explanation The SOAP message might not have security constraints defined, or the actor on the server and client do not match. Action Verify that the client has Web services security configured and that the actor matches on both client and server.
WSEC5132E: Unexpected exception while initializing the sender configuration: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5133E: An exception while verifying the signature.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5136E: An exception while verifying X.509 certificate: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5140W: Unknown key type: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5150E: Found no KeyIdentifier element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5151E: ParseException in Hex.decode(): {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5152E: An exception while locating the key from KeyLocator: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5156E: An exception while retrieving the key from "{0}" keystore object: {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5158E: An internal error while manipulating SOAP message object: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5159E: An internal error while evaluating whether the asserting ID is trusted: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5160E: Intermediary nodes cannot have IDType of "X509Certificate".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5161E: When TrustMode is "BasicAuth", a LoginMapping for "BasicAuth" is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5162E: When IDType is "X509Certificate", one or more SigningInfo (even without signature algorithms) elements are required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5163E: An exception while parsing the timestamp value: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5164E: An exception while decrypting the message: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5166E: The value of part attribute must be "bodycontent" or "usernametoken": {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5167E: The security token for authentication is not signed while RequiredIntegrity contains "securitytoken".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5168E: When AuthMethod is "Signature", the security token which is used for ths signing is not signed. Therefore, it is not possible to specify "securitytoken" for signing.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5169W: There are no allowed transform algorithms defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5170W: There are no allowed transform algorithms defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5171E: Given key name is not a well-formed Distinguished Name: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5172E: A certificate was not found in the request message.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5173E: The original fault is: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5174E: Signature verification failed; the last error message is: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5175E: Unable to hex decode Nonce (randomly generated value), exception {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5176E: Unknown encoding type: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5177E: Nonce (randomly generated value) manager not specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5178E: Repeated nonce (randomly generated value).
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5179E: Unable to parse UTC creation time.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5180E: Too old creation time: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5181E: The certificate (Owner: "{0}") with alias "{1}" from keystore "{2}" has expired: {3}
Explanation The certificate has expired, verify the date of the certifcate. Action Verify the date of the certificate and obtain a valid new certificate.
WSEC5182E: An exception while validating the certificate (Owner: "{0}") with alias "{1}" from keystore "{2}": {3}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5183E: The algorithm for recovering the key with alias "{0}" of keystore "{1}" cannot be found: {2}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5184E: The key with alias "{0}" of keystore "{1}" cannot be recovered (the password could be wrong): {2}
Explanation The key cannot be recovered, usually caused by incorrect password. Action Verify the key password. If correct password is entered and problem still persist, contact your service representative.
WSEC5185W: Unable to map "{0}" DN of X.509 certificate to security name: {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5186E: Class "{0}" not found, exception {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5187E: Unable to instantiate the class "{0}", exception {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5188E: Unable to access to the default constructor of the class "{0}", exception {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5189W: The certificate (Owner: "{0}") with alias "{1}" from keyStore "{2}" will be expired in {3} days.
Explanation A certificate is about to expire in the keystore. Action Open the keystore and validate the expiration dates on all certificates in the keystore. Prepare to generate new certificates, if necessary.
WSEC5190W: The property "{0}" contains a non-integer string value "{1}", default {2} is used instead. Correct the value specified in the property so that it is an integer number.
Explanation The value entered could not be represented as an integer number. Action Correct the value specified in the property so that it is an integer number.
WSEC5191E: Can not parse timestamp {0}, the exception is {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5192E: Nonce (randomly generated value) timestamp, "wsu:Created" element not specified in wsse:UsernameToken element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5193E: Nonce (randomly generated value) expired.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5194E: Nonce (randomly generated value), "wsse:Nonce" element not specified in wsse:UsernameToken element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5195E: Error in obtaining {0} algorithm from {1} provider, exception {2}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5196E: CipherData element not specified in the Web services security header.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5197E: CipherReference/@URI attribute not specified in the Web services security header.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5198E: XML encryption, unsupported type of URI: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5199E: Username not specified.
Explanation Username not entered within the alloted time Action Specify username
WSEC5200E: Current time on server is {0}, nonce created time is {1}.
Explanation Clocks on the client and server may not be synched Action Make sure client and server date/time/timezone are synched
WSEC5201E: Login failed {0}
Explanation User cannot be authenticated Action Check that the user exists in user registry and the correct user registry is being used
WSEC5202E: Unable to instantiate class "{0}" and exception {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5203E: Class "{0}" not found and exception {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5204E: MessageFactory is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5205E: Timestamp expired.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5206E: Current time on other party is {0}, timestamp created time is {1}.
Explanation Clocks on the client and server may not be synched Action Make sure client and server date/time/timezone are synched
WSEC5207E: No security token found which satisfies any one of the configured AuthMethods. The configured AuthMethods are: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5208E: Timestamp too far in the future.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5209E: Nonce (randomly generated value) too far in advance.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5300E: An parsing error(s) occured: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5301E: An exception while resolving a entry, publicId="{0}" and systemId="{1}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5302E: No such resource: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5303E: An exception while parsing a input source
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5304E: An exception while creating a new Document
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5310E: Unable to open an X509 CRL file: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5311E: Unable to create an X509 CRL factory: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5312E: Unable to get the key "{0}" from the keystore "{1}" due to {2}, the may cause by key is expired, the password is incorrect and so fore.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5314E: KeyStore: storepass attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5315E: Unable to obtain the SOAP header: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5320E: Unable to hex decode Nonce (randomly generated value), exception {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5321E: Repeated nonce (randomly generated value).
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5322E: An exception while parsing the timestamp value
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5323E: The message was expired: creation date of timestamp [{0}], expiration date of timestamp [{1}], and machine''s current date [{2}].
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5324E: Unsupported ValueType: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5325E: Null is not allowed as the nonce, expected wsse:Nonce element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5326E: Null is not allowed as the timestamp, expected wsu:Timestamp element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5327E: Null is not allowed as the nonce timestamp, expected wsu:Created element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5328E: Repeated identifier: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5330E: Unable to find the client deployment descriptor: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5331E: Unable to find the client binding: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5332E: Unable to cast to client deployment descrypter: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5333E: Unable to cast to client binding: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5334E: There are more than one service references defined, but can not determined which one to use.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5335E: There are more than one port qname bindings defined, but can not determined which one to use.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5336E: There is no binding defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5337E: There is no deployment descriptor defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5338E: An exception while constructing of configuration
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5350E: Invalid configuration: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5351E: Unknown usage {0}: {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5352E: Unknown WAS keyword {0}: {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5353E: Null is not allowed to the keyword with the dialect [{0}]: {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5354E: Unknown dialect {0} in {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5355E: Unsupported caller setting: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5356E: Unsupported trust method setting: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5357E: Unauthorized canonicalization method: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5358E: Unauthorized signature method: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5359E: Unknown type of KeyInfoSignature {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5360E: Unauthorized digest method: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5361E: Unauthorized transform: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5362E: Unknown type of KeyInfo: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5363E: Unauthorized data encryption method: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5364E: Unauthorized key encryption method: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5365E: Caller or TrustedMethod: type attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5366E: Consumer SigningInfo: At least one KeyInfo is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5367E: SigningInfo: At least one PartReference is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5368E: EncryptionInfo: DataEncryption is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5369E: Consumer EncryptionInfo: At least one KeyInfo is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5370E: EncryptionInfo: One PartReference is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5371E: TokenConsumer: classname attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5372E: TokenConsumer: ValueType is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5373E: Consumer SigningInfo or EncryptionInfo: At least one KeyInfo is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5374E: KeyInfo: classname attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5375E: KeyInfo: type attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5376E: XPath expression for XPath transform not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5380E: Unmatched value type: {0} and {1}.
Explanation Not valid or Unexpected Value type for the TokenConsumer. Action Verify that valid Value type for the TokenConsumer is provided in the bindings.
WSEC5381E: Unable to resolve the reference: "{0}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5382E: Null is not allowed to the trust anchor.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5383E: The usage of the part referenced by Caller or TrustMethod MUST be required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5384E: There is no TokenConsumer that has same value type defined in Caller or TrustMethod.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5385E: Both WAS keyword "dsigkey" or "enckey" and STR-Transform are set in the configuration, but corresponding KeyInfo has no reference to TokenGenerator or TokenConsumer.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5386E: To sign and/or encrypt Nonce or timestamp, specify a MessagePart that needs to be signed and/or encrypted.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5400E: algorithm attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5401E: AlgorithmMapping: factoryname attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5402E: AlgorithmMapping: At least one AlgorithmURI is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5403E: PartReference in SigningInfo: referenced message part is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5404E: PartReference in SigningInfo: DigestMethod is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5405E: PartReference in SigningInfo: At least one Transform is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5406E: (Required)Integrity or (Required)Confidentiality: At least one MessageParts is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5407E: Integrity or Confidentiality: Processing order MUST be zero or positive number: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5408E: MessageParts, Timestamp, or Nonce: dialect attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5409E: MessageParts, Timestamp, or Nonce: keyword attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5410E: KeyLocator: classname attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5411E: KeyLocator: At least one Key is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5412E: KeyStore: type attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5413E: KeyStore: path attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5415E: Key: alias attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5416E: Key: name attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5417E: KeyStore: KeyStore referenced is not valid : {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5418E: KeyStore: KeyStore should have one of the following. Either KeyStoreRef attribute or storepass, path, type attributes.
Explanation This exception is unexpected. The cause is not immediately known. Action Change the keystore element to have either KeyStoreRef or storepass,path,type attributes
WSEC5430E: Generator SigningInfo: Only one KeyInfo is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5431E: Generator EncryptionInfo: Only one KeyInfo is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5432E: TokenGenerator: classname attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5433E: TokenGenerator: ValueType is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5434E: CallbackHandler: classname attribute is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5435E: BasicAuth: User id is null, but user password is not null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5436E: Generator SigningInfo or EncryptionInfo: Only one KeyInfo is required: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5437E: The combination of secret key algorithms [{0}] and the type of key information [{1}] is not allowed.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5440W: There are no allowed transform algorithms defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5441W: There are no allowed canonicalization algorithms defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5442W: There are no allowed signature algorithms defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5443W: There are no allowed digest algorithms defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5444W: There are no allowed data encryption algorithms defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5445W: There are no allowed key encryption algorithms defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5450E: Null or empty is not allowed to the name of Integrity, Confidentiality, RequiredIntegrity, or RequiredConfidentiality.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5451E: Two Integrities or Confidentialities have same order "{0}": these name are [{1}] and [{2}].
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5452E: Null or empty is not allowed to the name of SecurityToken or RequiredSecurityToken.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5453E: AddCreateTimestamp/@expires has invalid format string: "{0}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5454E: Unable to find the default configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5455E: Null or empty is not allowed to the name of TokenGenerator or TokenConsumer.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5456E: Null or empty is not allowed to the name of KeyLocator.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5457E: Null or empty is not allowed to the name of KeyInfo.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5458E: Missing TokenGenerator reference in the KeyInfo.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5490E: Unsupported type of WS-Security factory: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5491E: Unable to obtain the object type.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5492E: Unsupported type of WS-Security component: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5493E: Unable to obtain the classpath used for instantiation.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5494E: Unexpected error during the instantiation of "{0}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5500E: Unable to obtain the SOAP envelope
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5501E: Unknown namespace URI of WS-Security specification
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5502E: Unexpected element as the target element: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5503E: Unknown element {0} in the {1} element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5504E: The namespace URI is diffrent by location: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5505E: There are different namespaceURIs for WS-Security.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5506E: All the attempts based on each SigningInfo failed. The last exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5507E: All the attempts based on each EncryptionInfo failed. The last exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5508E: All the attempts based on each TokenConsumer failed. The last exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5509E: A security token whose type is [{0}] is required.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5510E: An exception occurred during the signature verification. The exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5511E: An exception occurred during the decryption of a message. The exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5512E: Unable to cast {0} into {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5513E: An exception while creating WS-Security configuration object
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5514E: An exception while processing WS-Security message
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5515E: Unable to instantiate WSSFactory.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5516W: No signer X509 certificate was found in the request message.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5517W: Unable to specify the one of X509 certificates in the request message.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5518W: Unable to obtain the X509 certificate from a token
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5519W: valid Certificate is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5520E: An exception occurred during token processing. The exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5521W: An exception occurred during token processing. The exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5522W: An exception occurred during signature verification. The exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5523W: An exception occurred during the decryption of a message. The exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5524W: The server cannot find the Web service security header with actor: {0}
Explanation The SOAP message might not have security constraints defined, or the actor on the server and client do not match. Action Verify that the client has Web services security configured and that the actor matches on both the client and the server. If you are using a IBM JAX-RPC Client, verify that the J2EE-based Service Client (JSR-109) Programming Model is used to look up the service. For example, the service look-up process needs to use the JNDI.
WSEC5525E: The server cannot find the Web service security header
Explanation The SOAP message might not have security constraints defined, or the actor on the server and client do not match. Action Verify that the client has Web services security configured and that the actor matches on both client and server.
WSEC5526E: The server cannot find the Web service security header with actor: {0}
Explanation The SOAP message might not have security constraints defined, or the actor on the server and client do not match. Action Verify that the client has Web services security configured and that the actor matches on both client and server.
WSEC5550E: Unable to obtain the message context.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5551E: Unable to extract the XML document from a SOAP message
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5552E: Unexpected element as the parent element: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5553E: Unexpected configuration: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5554E: Unknown version of SOAP specification: versionId={0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5555E: mustUnderstand does not match: existing value="{0}", new value="{1}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5556E: Timestamp element not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5557E: More than one parent elements exists.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5600E: DataReference/@URI attribute not specified.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5601E: An exception while decrypting the message
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5602E: EncryptedKey/EncryptionMethod "{0}" not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5603E: Null is not allowed as the target element, expected enc:EncryptedKey or enc:ReferenceList element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5610E: Unable to create the {0} element: {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5611E: An exception while generating the key for data encryption
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5612E: An exception while encrypting the data
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5613E: An exception while encrypting the key for data encryption
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5614E: An exception while constructing the EncryptionMethod element
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5620E: Signature verification failed: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5621E: Unsupported signed part: URI="{0}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5623E: Expected zero or one result of key info processing.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5624E: Null is not allowed as the target element, expected ds:Signature element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5625E: All the attempts based on each Reference failed. The last exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5630W: Unknown key type: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5631E: Unknown dialect: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5632E: Unable to resolve the expression: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5633E: An exception while constructing the Signature element
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5634E: An exception while signing the message
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5635E: Null is not allowed as the parent element of the ds:Signature element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5636W: Objects to be processed not found with the dialect [{0}] and the keyword [{1}].
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5640E: Unable to add wsu:Created because wsu:Timestamp header already exists.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5641E: More than one Timestamp element found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5645E: Null is not allowed as the target element, expected wsu:Timestamp element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5650E: The "{0}" instance can''t handle DOMCryptoParameterSpec.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5660E: All the attempts based on each KeyInfoConsumer failed. The last exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5670E: Null is not allowed to the canonicalization method during the processing of STR-Transform.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5671E: Unknown canonicalization method: {0}, during the processing of STR-Transform.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5672E: Null is not allowed to the ID resolver during the processing of STR-Transform.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5673E: Unsupported type of URI: {0}, during the processing of STR-Transform.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5674E: Unable to convert secToken into Element or NodeList during the processing of STR-Transform.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5680E: Unable to transform XPath expression "{0}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5690E: Unable to cast {0} into {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5695E: Encrypting data object MUST contain the timestamp or nonce: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5696E: Null is not allowed as the node.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5697E: Null is not allowed as the keyword of WAS dialect.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5700E: There is no wsu:Timestamp to be moved.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5710E: A required message part [{0}] is not encrypted.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5711E: A required message part [{0}] is encrypted.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5720E: A required message part [{0}] is not signed.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5721E: A required nonce is not found in the message part [{0}].
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5722E: A required timestamp is not found in the message part [{0}].
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5723E: A required message part [{0}] is signed.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5724E: Null is not allowed as the target element, expected soapenv:Envelope element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5730E: A required timestamp is not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5731E: A required timestamp is not found in the part [{0}].
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC5800E: keystore is referenced by keyStoreRef that is either null or not valid {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6000E: KeyInfoContentGenerator object is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6001E: Key object is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6010E: KeyInfo Type or ValueType does not match: keyinfo type="{0}", ValueType="{1}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6011E: KeyInfoContentConsumer is not found
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6012E: All the attempts to resolve the key based on each Key Information failed. The last exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6013E: KeyInfo type is UNKNOWN.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6014E: Unable to process Reference Element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6015E: Unable to process KeyIdentifier Element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6016E: Unable to process Embedded Element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6017E: An exception occurred during key extraction. The exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6018W: An exception occurred during key extraction. The exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6020E: TokenGenerator object is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6021E: Security header is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6022E: KeyLocator object is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6023E: TokenGeneratorConfig object is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6024E: TokenLocatorComponent is not implemented: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6025E: Unexpected type of key information "{0}", we expected the type "{1}"
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6030E: Reference ID cannot be obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6031E: Unable to process Reference Element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6032E: URI attribute is not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6040E: TokenComsumer object is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6041E: Unable to process Embedded Element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6042E: Id attribute is not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6050E: Unable to process KeyIdentifier Element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6051E: Missing ValueType in the KeyIdentifier Element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6052E: EncodingType attribute is not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6053E: Unknown EncodingType.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6054E: No IdentifierType attribute.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6060E: Unable to process KeyName Element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6070E: X509 Certificate is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6080E: Received Serial Number is not valid.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6081E: Unable to process X509Data Element.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6090E: KeyStore is not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6091E: Referenced KeyName is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6092E: Unknown key usage type: key type="{0}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6093E: Invalid algorithm for Identifier generation.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6094E: Null is not allowed to the value type.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6095E: Value type must be {0}, but {1} found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6096E: valid Certificate of the alias [{0}] is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6097E: valid Certificate is not obtained.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6098E: Key cannot be recovered.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6099E: key information about [{0}] is not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6100E: cannot obtain key information
Explanation This might be due to the missing key name in the configuration Action Check and make sure that valid key name exists
WSEC6500E: There is no candidate used to login.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6501E: There are more than two candidates used to login.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6502E: Null is not allowed to the token used to specify the caller.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6503E: There are two candidates used to specify the trusted identifier.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6504E: There are two candidates used to specify the caller identifier.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6505E: There is the token that specify the trusted identifier when the <TrustMethod> configuration is not set.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6506E: Null is not allowed to the token that specify the trusted identifier when the <TrustMethod> configuration is set.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6507E: Null is not allowed to the token in the <TrustMethod> configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6508E: Null is not allowed to the token in the <Caller> configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6509E: There are more than one candidates used to login.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6510E: Failed to login
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6511E: Null credential value found for the LPTA token.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6512E: Null principal value found for the custom token.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6513E: Principal already exists in the subject.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6514E: Public Credentials already exist in the subject.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6515E: Private Credentials already exist in the subject.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6520E: Construction of the login context failed. The exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6521E: Login failed. The exception is
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6522E: Failed to encode the certificate [{0}]
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6525E: Unable to instantiate the callback handler [{0}]
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6526E: Unable to handle the callbacks by the callback handler [{0}]
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6530E: Password digest is unsupported.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6531W: The name [{0}] is not trusted.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6540E: A subject in the context is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6541E: Unable to get the instance of ContextManager.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6542E: Unable to get the caller subject from the ContextManager.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6543E: Unable to get the invocation subject from the ContextManager.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6544E: Unable to set the caller subject to the ContextManager.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6545E: Unable to set the invocation subject to the ContextManager.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6550E: Unable to generate a X509 certificate
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6551E: Failed to encode the certificate [{0}].
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6600E: Null is not allowed to the keystore info in the <CallbackHandler> configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6601E: An exception while checking <CallbackHandler> configuration
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6602E: An exception while getting X509 certificate
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6603E: An exception while getting the keystore ({0})
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6610E: An exception while handling a X509 certificate: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6620E: An exception whild handling a pki path
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6621E: Null is not allowed to the acquired binary data.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6630E: An exception whild handling a PKCS7
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6650E: Failed to handle the callback handler
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6660E: Unable to create a X509 Certificate: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6661E: Faild to check the validity of a X509 certificate: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6662E: Failed to check the cert path of a X509 certificate: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6663E: Unable to parse the serial number of its own certificate [{0}]: {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6664E: Null is not allowed to PKIXBuilderParameters. The configuration of TrustAnchor and CertStoreList are not correct.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6670E: Unable to create cert path from pki path: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6671E: Failed to check the cert path of pki path: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6680E: Unable to create cert path from PKCS7: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6681E: Failed to check the cert path of PKCS7: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6690E: Failed to check username [{0}] and password in the UserRegsitry: {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6691E: Failed to check username [{0}] in the UserRegsitry: {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6700E: Received token is not specified as the caller: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6701E: Password is not acceptable to this token consumer: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6710W: There''s a JAASConfig entry [{0}], but we don''t need this for LTPA token.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6711W: Default KeyInfoContentConsumer is not defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6712W: Default TokenConsumer is not defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6713W: Default JAAS configuration is not defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6714W: Default KeyLocator is not defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6715W: Default KeyInfoContentGenerator is not defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6716W: Default TokenGenerator is not defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6717W: Default CallbackHandler is not defined.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6718E: Namespace is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6719E: The QName {0} was not found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6720E: The Namespace {0} is not supported.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6721E: WS-Security Utility namespaces {0} and {1} do not match.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6722W: The Distributed Config Cache Factory is not initialized.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6723W: The specified key to look into Distributed Config Cache is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6724W: Distributed Config Cache instance is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6725W: There is no object linked with the specified key {0} in the Distributed Config Cache.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6726W: The specified Config object to put in Distributed Config Cache is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6727E: Exception occured getting Config object from the Distributed Config Cache. Exception is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6728E: Exception occured putting Config object in the Distributed Config Cache. Exception is {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6729E: Runtime Classloader is null, failed to load class {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6730E: Could not get a valid certificate for key [{0}], key configured in Callback Handler is [{1}] and alias value is [{2}].
Explanation Could not find a certificate that matches the given key. One of the possible causes is the key name is mismatch in Key Information, Key Locator, Callback Handler and key store. Action Make sure the key name is configured properly in Key Information, Key Locator, Callback Handler and the key store file.
WSEC6731E: Cannot load the keystore referenced by the name : {0}, exception is {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6732I: No outbound namespace defined for WS-Addressing, the default namespace [{0}] is used.
Explanation No namespace defined for the outbound request for WS-Addressing and the default namespace is used. Action None, informational only.
WSEC6733E: Multiple namespaces in the WS-Addressing headers.
Explanation Multiple conflicting WS-Addressing namespaces in the SOAP headers. Action Make sure the correct and supported WS-Addressing namespace is used.
WSEC6734E: Missing Web Service Security Generator or Consumer configuration.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6735E: Failed to login with token type {0}. The exception is: {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6736W: Caught Exception [{0}] when generating security audit events.
Explanation The WebSphere platform audit subsystem platform implementation failed generating a security audit event. Action 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.
WSEC6737E: Insufficient data to generate the specified security audit event.
Explanation The WebSphere platform audit subsystem platform implementation cannot generate a security audit event because critical data was missing. Action Contact WebSphere support for help.
WSEC6738E: The {0} Kerberos principal is not authorized to access the {1} service.
Explanation The Kerberos principal cannot be located or the principal does not have the valid Kerberos credential. Action Verify that the intended user is listed in the Key Distribution Center (KDC) registry.
WSEC6739I: The {0} Kerberos principal is authorized to access the {1} service.
Explanation The Kerberos principal has been located and validated. Action No action is required.
WSEC6740E: The Kerberos token is bad and the following processing error has occurred:
{0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6741I: The initialization process for the {0} service has started.
Explanation The process to initialize the Generic Security Service (GSS) credential for the service has started. Action No action is required.
WSEC6742I: The initialization process for the {0} service is complete.
Explanation The process to initialize the Generic Security Service (GSS) credential for the service is complete. Action No action is required.
WSEC6743E: The initialization process for the {0} service is complete, but failed.
Explanation The process to initialize the Generic Security Service (GSS) credential for the service has failed. Action Validate the Kerberos configuration.
WSEC6744E: The run time cannot match the keytab entry for the {0} Kerberos service principal name.
Explanation The Application Server cannot find the service principal name from the specified keytab. Action Validate the Kerberos configuration and the keytab.
WSEC6745I: The Kerberos Service Principal Name object has been initialized for the {0} service.
Explanation The Kerberos service principal name is validated and established. Action No action is required.
WSEC6746E: The target Kerberos service principal name property is not configured.
Explanation The property for target Kerberos service principal name cannot be found. Action Ensure that the target service principal name property is entered correctly.
WSEC6747E: An internal Kerberos configuration object cannot be found.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6748E: The following unexpected exception has been encountered: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6749E: The following Kerberos AP_REQ token has not been passed as part of the request:
Explanation The Kerberos AP_REQ token from the incoming request cannot be found. Action Check the token generator configuration for the request.
WSEC6750E: A SOAP envelope object is not available and an internal error occurred.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6751E: The {0} Kerberos data object, which is used in the {1} method, is not valid.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
WSEC6752E: A callback handler does not exist for the Kerberos login module.
Explanation A callback handler cannot be found for the Kerberos login module. Action Validate the callback handler in the token generator or token consumer configuration.
WSEC6753E: The {0} property is not properly configured for {1} to run with a Kerberos token.
Explanation The Application Server cannot process the property from the configuration. Action Validate the token generator or token consumer configuration.
WSEC6754E: The following exception has been caught during Kerberos AP_REQ token consumption: {0}
Explanation The indicated exception has been caught during Kerberos AP_REQ token consumption. Action Verify the incoming SOAP message and token consumer configuration.
WSEC6755E: The following error occurred during the handling of the {0} instance of the Kerberos AP_REQ token generation: {1}
Explanation The indicated error has been found during Kerberos AP_REQ token generation. Action Verify the token generator configuration.
WSEC6756E: Handling the {0} instance during Kerberos AP_REQ token generation caused the following exception: {1}
Explanation The indicated error has been found during Kerberos AP_REQ token generation. Action Verify the token generator configuration.