Hi Maybe a complete different solution approach. Instead of extending this functionality into CXF itself you could delegate this to the STS component (running in a seperate VM) which has been introduced in CXF 2.5.
The STS allows you to implement custom security token provider and if needed custom security token validator. At the time, where your security gateway is enhanced you only have to change the tokenType in the securitypolicy of your service. Thanks Oli ________________________________________ Von: cxfnewbie [[email protected]] Gesendet: Mittwoch, 7. Dezember 2011 01:39 Bis: [email protected] Betreff: Re: cxf and saml1.0 looking into the code some more, now I realize I just needed a space between the two actions. So that is solved (yipee!). Still gotta figure out how to change the saml token to a 1.0 token. -- View this message in context: http://cxf.547215.n5.nabble.com/cxf-and-saml1-0-tp5034076p5054018.html Sent from the cxf-user mailing list archive at Nabble.com.
