Incorrect format of wsu:Id
Hi,
I have a setup with an Outgoing WS-Security configuration for signing and encryption.
When I send a request, the security headers are automatically created and inserted into the message, as expected.
However, the value of the wsu:Id attribute is created with an incorrect format, which causes the request to be rejected during wsdl/xsd validation.
The namespace "wsu" refers to http://docs.oasis-open.org/wss/2004/01/ ... ty-1.0.xsd
In this schema, the definition of the Id attribute states that it is of the type xsd:ID.
This refers to yet another schema, http://www.w3.org/2001/XMLSchema.xsd, where the definition of the ID type is found.
The ID type has a restriction based on the NCName type, which is described here: http://www.w3.org/TR/REC-xml-names/#NT-NCName
The restriction requires the wsu:Id attribute to start with "_" or any character.
SoapUI allows these values to start with numeric values or other symbols, which makes the format invalid.
I hope that a change to fix this will not require too much effort
Best regards
Christian
I have a setup with an Outgoing WS-Security configuration for signing and encryption.
When I send a request, the security headers are automatically created and inserted into the message, as expected.
However, the value of the wsu:Id attribute is created with an incorrect format, which causes the request to be rejected during wsdl/xsd validation.
The namespace "wsu" refers to http://docs.oasis-open.org/wss/2004/01/ ... ty-1.0.xsd
In this schema, the definition of the Id attribute states that it is of the type xsd:ID.
This refers to yet another schema, http://www.w3.org/2001/XMLSchema.xsd, where the definition of the ID type is found.
The ID type has a restriction based on the NCName type, which is described here: http://www.w3.org/TR/REC-xml-names/#NT-NCName
The restriction requires the wsu:Id attribute to start with "_" or any character.
SoapUI allows these values to start with numeric values or other symbols, which makes the format invalid.
I hope that a change to fix this will not require too much effort
Best regards
Christian
