WSEC

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


Terms and conditions for information centers | Feedback

Last updated: June 12, 2013 12:15 PM EDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.webservices.wssecurity.resources.was-wssecurity.dita
File name: com.ibm.ws.webservices.wssecurity.resources.was-wssecurity.html