I've added support for processing EncryptWith and SignWith for CXF 2.6.2: https://issues.apache.org/jira/browse/CXF-4361
There is no easy way to stop the 2.5.2 STS rejecting the request that contains EncryptWith (or any other unknown element). What you could do is to extend the RequestParser to stop it rejecting EncryptWith elements: http://svn.apache.org/viewvc/cxf/trunk/services/sts/sts-core/src/main/java/org/apache/cxf/sts/request/RequestParser.java?view=markup Then you would need to also extend the TokenIssueOperation, and @Override the "parseRequest" method of AbstractOperation to use the new RequestParser: http://svn.apache.org/viewvc/cxf/trunk/services/sts/sts-core/src/main/java/org/apache/cxf/sts/operation/AbstractOperation.java?view=markup Colm. On Tue, Jun 5, 2012 at 9:42 PM, DTaylor <[email protected]> wrote: > Is there some way to have it so that if an EncryptWith tag is found in the > main RST, the STS will still deliver the token rather than crash out due to > an unfound jaxb element for CXF 2.5.2? > > Due to workplace constraints, I am unable to upgrade past 2.5.2 at this > time. > > Thanks, > > Dan. > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/CXF-EncryptWith-and-NET-tp5709132p5709157.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
