free-ice opened a new pull request #39:
URL: https://github.com/apache/ws-wss4j/pull/39
As back as 2007 instances of incompatability between wss4j and WCF
stack can be found. Usually the IIS stack trace contained :
**The EncryptedKey clause was not wrapped with the required encryption token
'System.IdentityModel.Tokens.X509SecurityToken'**
RFC 2253 seems to provide two approaches for escaping disallowed
characters.
Java seems to support both approaches using \ or using "".
This is supported by the Unit test DmCommaDelimiterSymmetryTest
WCF seems to only support using ""
This is supported by the numerious blog and stackoverflow questions
about this error.
This patch changes the Issuers X509Principal name format to the "" delimited
format. It has simple unit tests and also another test that uses the JDK
truststore and test that Java interprets the Comma delimted RDN the
same as the \ delimited format.
This patch was originally against the 2_3_x-fixes and has mainly been tested
under Java 8,
and against both a test and production WCF system.
Originally I had considered making this change optional, because of
other untested tech stacks. At this point how to do that cleanly
alludes me but I would be happy to do so with some guidance.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
