|
| |
| Sun Java System Application Server 8.1 Enterprise Edition 2005Q1 Error Message Reference | |
A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X - Y - Z
Chapter 14
WSS Error MessagesThis chapter describes messages for errors with a WSS prefix.
WSS0126Message
Unsupported algorithm type. Only RSA supported.
Solutions/Workarounds
Check that the signature algorithm is RSA
WSS0129Message
Malformed message ds:Signature element missing from the wsse:Security header block
Solutions/Workarounds
Check proper signature was generated while signing
WSS0134Message
Unable to Initialize XMLCipher with the given Key
Solutions/Workarounds
Check that the XMLCipher was initialized properly
WSS0137Message
An appropriate JCE provider is not configured in the JRE
Solutions/Workarounds
Look at root exception for more clues
WSS0144Message
Base64Decoding exception is the root cause
Solutions/Workarounds
Check that the data is valid base64 encoded
WSS0147Message
TransformationConfiguration exception while trying to use stylesheet to pretty print
Solutions/Workarounds
Make sure style sheet is valid
WSS0148Message
Exception while trying to pretty print using transform
Solutions/Workarounds
Make sure the original SOAP Message and style sheet are both correct
WSS0156Message
Error in certificate used for validation
Solutions/Workarounds
Check that the token contains a valid Certificate
WSS0165Message
XPath does not correspond to a DOM element
Solutions/Workarounds
Check that the node represented by the XPath is a valid DOM element
WSS0167Message
Invalid signature; verification failed
Solutions/Workarounds
Make sure the signature was not tampered with in transit
WSS0168Message
Unable to generate a random symmetric key
Solutions/Workarounds
Verify that the KeyGenerator has been properly initialized
WSS0169Message
Value of FilterParameterConstants.BINARY_SEC_TOKEN is not set
Solutions/Workarounds
Check that direct referencestrategy is set before exporting the certificate
WSS0181Message
Subject not authorized; validation failed
Solutions/Workarounds
Check that the user is authorized
WSS0182Message
FilterParameterConstants.REFERENCE_LIST parameter has a null value
Solutions/Workarounds
The reference list that needs to be decrypted usually set by ImportEncryptedKeyFilter
WSS0183Message
Could not locate a valid symmetric key needed for decryption.
Solutions/Workarounds
Value of symmetric key seems to be null. Check its value.
WSS0184Message
Could not retrieve security domain from the Securable SOAP message
Solutions/Workarounds
Make sure the SecurityEnvironment factory has set the right security environment.
WSS0185Message
Could not find the certificate associated with the direct reference strategy
Solutions/Workarounds
Check that the URI is valid and subjectkeyidentifier parameter is set in configuration
WSS0189Message
Data decryption algorithm has to be either Triple-DES, AES128-CBC, AES256-CBC
Solutions/Workarounds
Check that the encryption algorithm used is either 3DES, AES128_CBC, AES256_CBC
WSS0190Message
The number of elements encrypted is less than required/allowed
Solutions/Workarounds
Check that the data references for encryption (in message) match the requirements
WSS0191Message
Solutions/Workarounds
Check that ExportEncryptedKeyFilter is called before. Check that a valid KeyStore URL is used to instantiate the SecurityEnvironment and it contains a matching SecretKey
WSS0192Message
At least one target needs to be specified for encryption
Solutions/Workarounds
Check that a non-null target list is used to instantiate the filter
WSS0193Message
Target specified does not correspond to a valid message part
Solutions/Workarounds
Check that a valid XPath/QName/wsuId are specified
WSS0194Message
Solutions/Workarounds
Check that a valid XPath/QName/wsuId are specified complying to the spec.
WSS0195Message
ReferenceListBlock not set on the calling thread
Solutions/Workarounds
Check that ExportEncryptedKeyFilter is called before. Check that ExportReferenceListFilter is called before
WSS0196Message
An instance of SecurityEnvironment class for the operating environment was not set on SecurableSoapMessage
Solutions/Workarounds
Check that SetSecurityEnvironmentFilter processed the message before
WSS0198Message
Only RSA_SHA1 Signature algorithm is supported
Solutions/Workarounds
Check that RSA_SHA1 signature algorithm is specified
WSS0199Message
Timestamp creation time can not be null
Solutions/Workarounds
Check that non-null creation time is used to instantiate the filter
WSS0203Message
Header block corresponding to the desired requirement not found
Solutions/Workarounds
Check that the message meets the security requirements
WSS0204Message
Illegal security header block found in the security header
Solutions/Workarounds
Check that the message is SOAP Security specification compliant
WSS0205Message
Requirement for wsu:Timestamp has not been met
Solutions/Workarounds
Check that the message meets the security requirements
WSS0206Message
Not all receiver requirements for security have been met
Solutions/Workarounds
Check that the message meets the security requirements
WSS0208Message
Extra security than required by the receiver side policy found in the message
Solutions/Workarounds
Check that the message strictly meets the security requirements
WSS0209Message
The message filter is in-correctly configured to process an inbound msg
Solutions/Workarounds
Check that the filters are correctly configured to process inbound messages
WSS0210Message
Only RSAv1.5 Key Encryption Algorithm is supported
Solutions/Workarounds
Check that the Key Encryption Algorithm used in the inbound msg is RSAv1.5
WSS0212Message
Receiver requirement for digested password in UsernameToken not met
Solutions/Workarounds
Check that the message meets the security requirements
WSS0213Message
Receiver requirement for nonce in UsernameToken not met
Solutions/Workarounds
Check that the message meets the security requirements
WSS0215Message
handle() call for a PropertyCallback on the handler threw exception
Solutions/Workarounds
Check the handler implementation
WSS0216Message
handle() call on the handler threw exception
Solutions/Workarounds
Check the handler implementation
WSS0217Message
handle() call on the handler threw exception
Solutions/Workarounds
Check the handler implementation
WSS0218Message
handle() call on the handler failed to set the Callback
Solutions/Workarounds
Check the handler implementation for SignatureKeyCallback.DefaultPrivKeyCertRequest
WSS0219Message
handle() call on the handler failed to set the Callback
Solutions/Workarounds
Check the handler implementation for SignatureKeyCallback.DefaultPrivKeyCertRequest
WSS0220Message
handle() call on the handler failed to set the Callback
Solutions/Workarounds
Check the handler implementation for DecryptionKeyCallback.AliasSymmetricKeyRequest
WSS0221Message
handle() call on the handler failed to set the Callback
Solutions/Workarounds
Check the handler implementation for SignatureKeyCallback and/or EncryptionKeyCallback, check keystores and truststores
WSS0222Message
handle() call on the handler failed to set the Callback
Solutions/Workarounds
Check keystore path and ensure that the right keys are present
WSS0301Message
Data malformed. Base 64 decoding error
Solutions/Workarounds
Check data is base64 encoded
WSS0302Message
Certificate parsing problem
Solutions/Workarounds
Data stream used to create the x509 certificate maybe corrupted
WSS0303Message
Certificate encoding exception
Solutions/Workarounds
Check that the x509 data is valid. Could not extract raw bytes from it.
WSS0306Message
Invalid password type
Solutions/Workarounds
Password type must match that specified by the WSS specification
WSS0307Message
Nonce encoding namespace check failed
Solutions/Workarounds
Nonce encoding type namespace seems invalid
WSS0310Message
NoSuchAlgorithmException: Invalid algorithm
Solutions/Workarounds
Check that the algorithm passed to SecureRandom is valid
WSS0311Message
Password digest could not be created
Solutions/Workarounds
Check that the algorithm passed to MessageDigest is valid
WSS0316Message
BinarySecurity token's Encoding type is invalid
Solutions/Workarounds
Check that encoding value for BinarySecurity token is valid as per spec.
WSS0317Message
Could not find X.509 certificate
Solutions/Workarounds
Ensure certificate path is not empty and certificate type is correct
WSS0318Message
Error while parsing and creating the KeyInfo instance
Solutions/Workarounds
Check values passed to KeyInfo constructor
WSS0319Message
Could not add key name to KeyInfo Header block
Solutions/Workarounds
Check KeyInfo and KeyName have been instantiated without exceptions
WSS0320Message
Could not get KeyName from KeyInfo
Solutions/Workarounds
Make sure the KeyName exists in the KeyInfo
WSS0321Message
Could not retrieve element from KeyInfo or could not import the node
Solutions/Workarounds
Check the element to be converted to SOAPElement
WSS0322Message
Exception while parsing and creating the Signature element
Solutions/Workarounds
Check that a fully initialized XML Signature was passed
WSS0323Message
Exception while trying to sign
Solutions/Workarounds
Check the key used to sign
WSS0324Message
Exception while adding a Reference with URI, transforms and Digest algorithm URI to SignedInfo
Solutions/Workarounds
WSS0327Message
Could not retrieve element from Signature or could not import the node
Solutions/Workarounds
Check the element to be converted to SOAPElement
WSS0328Message
Error parsing date.
Solutions/Workarounds
Check date format is in UTC. Check it is yyyy-MM-dd'T'HH:mm:ss'Z' or yyyy-MM-dd'T'HH:mm:ss'.'sss'Z'
WSS0329Message
Expecting UsernameToken Element
Solutions/Workarounds
Check that the next element is UsernameToken
WSS0330Message
Username not first child of UsernameToken
Solutions/Workarounds
Make sure first child of wsse:UsernameToken is Username in wsse namespace
WSS0331Message
Element may not be a proper UsernameToken
Solutions/Workarounds
Check that the UsernameToken matches the token schema
WSS0332Message
Username was null
Solutions/Workarounds
Check UsernameToken contains a valid Username
WSS0333Message
Keystore URL is null
Solutions/Workarounds
Check that the property javax.net.ssl.keyStore is set properly
WSS0334Message
KeyIdentifier holds invalid ValueType
Solutions/Workarounds
Check KeyIdentifier ValueType's value
WSS0335Message
KeyReference type not supported
Solutions/Workarounds
KeyReference type should be one of KeyIdentifier, Reference, X509Data
WSS0336Message
Can't locate public key
Solutions/Workarounds
Check public key retrieved should not be null
WSS0337Message
Could not resolve URI
Solutions/Workarounds
Check DirectReference's ValueType, it is not supported
WSS0338Message
Key Reference Mechanism not supported
Solutions/Workarounds
Check reference is one of X509IssuerSerial, DirectReference, KeyIdentifier
WSS0339Message
Support for processing information in the given ds:KeyInfo is not present
Solutions/Workarounds
Check ds:KeyInfo matches schema
WSS0340Message
Creation time cannot be ahead of current UTC time
Solutions/Workarounds
Check system time and ensure it is correct
WSS0341Message
Creation time is very old
Solutions/Workarounds
Check system time and ensure it is correct
WSS0342Message
BinarySecurity Token's Value type is invalid
Solutions/Workarounds
Check that valueType for BinarySecurity token is valid as per spec.
WSS0343Message
Error in creating the BST due to {0}
Solutions/Workarounds
Check that all required values are set on the Binary Security Token, including TextNode value.
WSS0344Message
The binary data in the Security Token can not be decoded, expected Base64 encoding
Solutions/Workarounds
Check to see that the encoding format of the Binary Security Token is Base64Binary
WSS0345Message
Error creating SOAPElement for EncryptedDataHeaderBlock
Solutions/Workarounds
If SOAPElement is used to create EncryptedData HeaderBlock, check to see that it is valid as per spec.
WSS0346Message
Invalid SOAPElement passed to EncryptedDataHeaderBlock constructor
Solutions/Workarounds
Check that the SOAPElement passed to EncryptedDataHeaderBlock is valid as per spec.
WSS0347Message
Solutions/Workarounds
Check to see SOAPElement used to initialize EncryptedType has CipherData. Check to see setCipherData() is called on the EncryptedType
WSS0348Message
Error creating SOAPElement for EncryptedKeyHeaderBlock
Solutions/Workarounds
If SOAPElement is used to create EncryptedKeyHeaderBlock, check to see that it is valid as per spec.
WSS0349Message
Invalid SOAPElement passed to EncryptedKeyHeaderBlock()
Solutions/Workarounds
Check that the SOAPElement passed to EncryptedKeyHeaderBlock() is valid as per spec.
WSS0350Message
Error creating/updating CipherData SOAPElement (in EncryptedKeyHeaderBlock)
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0351Message
Error creating EncryptionMethod SOAPElement
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0352Message
Error creating javax.xml.soap.Name for CipherValue
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0353Message
No CipherValue element(s) are present in CipherData
Solutions/Workarounds
Check to see if setCipherValue() is called on EncryptedType
WSS0354Message
An error may have occurred creating javax.xml.soap.Name for EncryptionMethod
Cause
An error may have occurred creating javax.xml.soap.Name for KeyInfo. An error may have occurred creating javax.xml.soap.Name for CipherData. An error may have occurred creating javax.xml.soap.Name for EncryptionProperties
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0355Message
Solutions/Workarounds
Check that a non-null SOAPElement is passed to addXXXKeyValue()
WSS0356Message
Error creating com.sun.org.apache.xml.security.keys.content.X509Data
Solutions/Workarounds
Check that a non-null SOAPElement is passed to addX509Data()
WSS0357Message
Error getting KeyValue from KeyInfo for the given index
Solutions/Workarounds
Check that the ds:KeyInfo element has ds:KeyValue elements. Check that the index (beginning with 0) used to refer the ds:KeyValue element is valid
WSS0358Message
Error getting X509Data from KeyInfo for the given index
Solutions/Workarounds
Check that the ds:KeyInfo element has ds:X509Data elements. Check that the index (beginning with 0) used to refer the ds:X509Data element is valid
WSS0359Message
Error adding com.sun.org.apache.xml.security.keys.content.X509Data to KeyInfo
Solutions/Workarounds
Check that a valid com.sun.org.apache.xml.security.keys.content.X509Data (as per specs.) is passed to addX509Data()
WSS0360Message
An error may have occurred creating javax.xml.soap.Name for ReferenceList
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0361Message
An error may have occurred creating org.w3c.dom.Element for ReferenceList
Cause
The org.w3c.dom.Document object passed ReferenceListHeaderBlock() may be null
Solutions/Workarounds
Check that the Namespace specified does not contain any illegal characters as per XML 1.0 specification. Check that the QName specified is not malformed (Refer to J2SE Documentation for more information). Check that a non-Null Document is passed to the ReferenceListHeaderBlock()
WSS0362Message
Invalid SOAPElement passed to ReferenceListHeaderBlock()
Solutions/Workarounds
Check that the SOAPElement passed to ReferenceListHeaderBlock() is valid as per spec.
WSS0363Message
Error creating javax.xml.soap.SOAPElement for xenc:DataReference
Cause
Error adding xenc:DataReference (SOAPElement) as child element of xenc:DataReference (SOAPElement). Error setting URI attribute on javax.xml.soap.SOAPElement for xenc:DataReference
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0365Message
Error creating javax.xml.soap.SOAPElement for namespace node
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0368Message
Error getting SOAPEnvelope from SOAPPart
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0369Message
Error getting SOAPHeader from SOAPEnvelope
Cause
Error creating SOAPHeader
Solutions/Workarounds
Refer to your SAAJ API Documentation
WSS0371Message
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0376Message
Error importing the SOAPElement representing the header block to the document corresponding to the SOAPMessage to which the header is being added
Solutions/Workarounds
Check that the SecurityHeaderBlock can be transformed to a valid SOAPElement. Refer J2SE Documentation for more
WSS0377Message
Error creating javax.xml.soap.SOAPElement for SecurityTokenReference
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0378Message
Error creating javax.xml.soap.SOAPElement for SecurityTokenReference
Solutions/Workarounds
Check that the org.w3c.dom.Document object passed to SecurityTokenReference() is non-null. Refer your SAAJ API Documentation
WSS0379Message
SOAPElement passed to SecurityTokenReference() is not a valid SecurityTokenReference element as per spec.
Solutions/Workarounds
Check that a valid SOAPElement as per spec. is passed to SecurityTokenReference()
WSS0380Message
The ds:Reference would already have been set using the constructors
Solutions/Workarounds
Check that a SOAPElement with ds:Reference (child element) is not used to instantiate SecurityTokenReference
WSS0381Message
Error in setting the passed ReferenceElement on SecurityTokenReference
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0382Message
Error appending ds:Object element to ds:Signature
Solutions/Workarounds
Check that a valid ds:Object SOAPElement (as per spec.) is passed to appendObject(). Check that a non-null SOAPElement is passed to appendObject()
WSS0383Message
Owner document of ds:Signature SOAPElement is null
Solutions/Workarounds
Check that the Document used to instantiate SignatureHeaderBlock() is not null
WSS0384Message
Error creating javax.xml.soap.Name for Timestamp
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0385Message
The SOAPElement used to instantiate Timestamp() is not valid (as per spec.)
Solutions/Workarounds
Check that the Localname and NamespaceURI of the SOAPElement used to create Timestamp() are correct as per spec.
WSS0386Message
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0387Message
Username is not set
Solutions/Workarounds
Check that a Username has been passed through the configuration file or through the callback handler
WSS0388Message
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0389Message
Base64 nonce encoding type has not been specified
Solutions/Workarounds
Check that the nonce encoding type used to create UsernameToken is Base64
WSS0390Message
UTF-8 Charset is unsupported for byte-encoding (a string)
Solutions/Workarounds
Refer your J2SE Documentation
WSS0391Message
Invalid Localname and NamespaceURI of the SOAPElement used for creating the token
Solutions/Workarounds
Check that the Localname and NamespaceURI of the SOAPElement used to create X509SecurityToken are valid (as per spec.)
WSS0393Message
The expiration time in Timestamp cannot be before current UTC time
Solutions/Workarounds
Check system time and ensure it is correct
WSS0394Message
Error parsing date.
Solutions/Workarounds
Check date format is in UTC. Check it is yyyy-MM-dd'T'HH:mm:ss'Z' or yyyy-MM-dd'T'HH:mm:ss'.'sss'Z'
WSS0500Message
Classname not a recognized class name for a MessageFilter
Solutions/Workarounds
Check that the class implements MessageFilter
WSS0502Message
Element encountered does not match element expected
Solutions/Workarounds
Check that the XML file follows schema for defining configuration
WSS0503Message
Element encountered does not match valid element expected
Solutions/Workarounds
Check that the XML file follows schema for defining configuration
WSS0508Message
Default settings can not be specified after custom settings are specified
Solutions/Workarounds
Check that no sender operations or receiver requirements are specified in a config. file. Check that no sender or receiver settings are programmatically added
WSS0509Message
Custom settings can not be specified after default settings are specified
Solutions/Workarounds
Check that no default settings are programmatically added
WSS0511Message
Non-permissible boolean value string - valid strings are true and false
Solutions/Workarounds
Check that the boolean value strings are either true or false
WSS0512Message
Non-permissible attribute on a Security Configuration element
Solutions/Workarounds
Check that the configuration file is consistent with the security configuration schema
WSS0513Message
Non-permissible element on xwss:SecurityConfiguration
Solutions/Workarounds
Check that the configuration file is consistent with the security configuration schema
WSS0514Message
Non-permissible child element in a Security Configuration element
Solutions/Workarounds
Check that the configuration file is consistent with the security configuration schema
WSS0515Message
Impermissible value for key reference string
Solutions/Workarounds
Check that the configuration file is consistent with the security configuration schema
WSS0516Message
Non-permissible duplicate element on a Security Configuration Element
Solutions/Workarounds
Check that the configuration file is consistent with the security configuration schema
WSS0517Message
Non-permissible duplicate element on a Security Configuration Element
Solutions/Workarounds
Check that the configuration file is consistent with the security configuration schema
WSS0519Message
Non-permissible/missing attribute value
Solutions/Workarounds
Check that the configuration file is consistent with the security configuration schema
WSS0520Message
xwss:SymmetricKey is not permitted along with xwss:X509Token
Solutions/Workarounds
Check that the configuration file is consistent with the security configuration schema
WSS0600Message
A Key can not be located in SecurityEnvironment for the Token Reference
Solutions/Workarounds
Check that the certificate referred to is valid and present in the Keystores
WSS0601Message
A Key can not be located in SecurityEnvironment for the KeyValue
Solutions/Workarounds
Check that the certificate referred to is valid and present in the Keystores
WSS0602Message
A Key can not be located in SecurityEnvironment for the X509Data
Solutions/Workarounds
Check that the certificate referred to is valid and present in the Keystores
WSS0603Message
XPathAPI TransformerException in finding element with matching wsu:Id/Id/SAMLAssertionID
Solutions/Workarounds
Refer your XPathAPI documentation
WSS0606Message
Input Node Set to STR Transform is empty
Solutions/Workarounds
Check that the Referenced Node (to be STR transformed) in ds:SignedInfo is valid
WSS0608Message
The Reference Mechanism in the SecurityTokenReference is not supported
Solutions/Workarounds
Check that the Reference Mechanism is either Direct/KeyIdentifier/X509IssuerSerial
WSS0609Message
The referenced security token is neither an XML token nor a raw binary token
Solutions/Workarounds
Check the referenced security token
WSS0650Message
Username/Password data file not found
Solutions/Workarounds
Check that the system property com.sun.xml.wss.usersFile is set
WSS0654Message
Error creating javax.xml.soap.Name for wsu:Id
Solutions/Workarounds
WSS0656Message
Solutions/Workarounds
Check that the keystoreFile attribute is specified on SSL Coyote HTTP/1.1 Connector element in server.xml and is valid. Check that a keystore file exists in $user.home
WSS0700Message
An instance of SecurityEnvironment is not set on SecurableSoapMessage
Solutions/Workarounds
Check that setSecurityEnvironment() is called on the SecurableSoapMessage. Check that SetSecurityEnvironmentFilter is applied on SecurableSoapMessage
WSS0701Message
No X509v3 Certificate can be located for the alias in Keystore
Cause
If no alias has been specified for signing, no default certificate is available
Solutions/Workarounds
Check that a default certificate is available and/or a valid alias is used
WSS0702Message
The X509v3 Certificate for the given alias does not contain a subject key identifier
Solutions/Workarounds
Check that a valid X509v3 Certificate is present in Keystores
WSS0704Message
Agreement name: SESSION-KEY-VALUE, has not been set on the SecurityEnvironment instance
Solutions/Workarounds
Check that the agreement name: SESSION-KEY-VALUE, is set on SecurityEnvironment using setAgreementProperty()
WSS0750Message
Error creating javax.xml.soap.SOAPElement
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0751Message
Solutions/Workarounds
Check that a SOAPElement conformant to spec. is passed
WSS0752Message
Solutions/Workarounds
Check that a SOAPElement conformant to spec. is passed
WSS0753Message
An embedded token in wsse:Embedded element is missing
Solutions/Workarounds
Check that the token element is conformant to WSS spec.
WSS0754Message
Token on EmbeddedReference has already been set
Cause
A SOAPElement representation of EmbeddedReference containing the Token is used to create the EmbeddedReference instance
WSS0756Message
Error creating SOAPElement for wsse:KeyIdentifier
Solutions/Workarounds
Check your SAAJ API Documentation
WSS0757Message
Error adding KeyIdentifier value to wsse:KeyIdentifer
Solutions/Workarounds
Check your SAAJ API Documentation
WSS0758Message
Error creating javax.xml.soap.Name
Solutions/Workarounds
Refer your SAAJ API Documentation
WSS0759Message
An X509IssuerSerial instance can not be created
Solutions/Workarounds
Check that the SOAPElement passed to the constructor is conformant to spec. (and has X509IssuerSerial child elements)
WSS0800Message
ds:KeyInfo in the message is not a valid one
Solutions/Workarounds
Check if the ds:KeyInfo in the message is valid