In a mean time, I found a way to configure wss4j to accept the per request
SAML Subject name.
No changes in cxf are required.
Pawel
--
View this message in context:
http://www.nabble.com/per-request-SAML-assertion-tp20578502p20584851.html
Sent from the cxf-dev mailing list archive at Nabble.com.
JAXRS runtime will be updated independently.
on 2.2-SNAPSHOT, 2.1.x - the documentation to be updated shorlty. In short, if you're on Jetty and do JAXRS you can rely on CXF
Continuations API, with/without JAXWS involed at the same time.
Apart from doing few usual typos :-), I've also forgot
Hi,
Continuations support for HTTP and JMS is on the trunk now, updates to the
2.1.x/2.0.x branches will be done next.
It's on 2.1.x and 2.0.x now
JAXRS runtime will be updated independently.
on 2.2-SNAPSHOT, 2.1.x - the documentation to be updated shorlty. In short, if you're on Jetty and
hi,
cxf together with wss4j does not allow for SAML assertion with dynamic
subject name (different subject name for each invocation).
I have made modification to wss4j to accept the extra parameter. I am stuck
at the cxf. WSS4JOutInterceptor is the place where the arguments have to be
added, but
