Hi Dan Could you share with us your STS configuration where the SamlTokenProvider is configured?
It also works if you haven't configured a realm. If you want to configure several logical instances within one STS runtime you can use the realm. Ex. if you connect different LDAP backends where each belongs to a security domain (equal to realm) then you need to take care about realm. A working CXF STS example can be found here: http://owulff.blogspot.com/2011/10/configure-and-deploy-cxf-25-sts-part-i.html and check Colm's blog as he got a tutorial on his blog starting here: http://coheigea.blogspot.com/2011/10/apache-cxf-sts-documentation-part-i.html HTH ------ Oliver Wulff Blog: http://owulff.blogspot.com Solution Architect http://coders.talend.com Talend Application Integration Division http://www.talend.com ________________________________________ Von: DTaylor [[email protected]] Gesendet: Montag, 16. April 2012 16:04 Bis: [email protected] Betreff: No Token Provider for Saml Token V1.1 Hi all, I'm currently attempting to acquire a SAML token from a CXF STS, but I am receiving the following error in the catalina logs: **WARNING: No token provider found for requested token type: http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1** and a SoapFault as a return to my client application. I'm assuming that the actual problem is that I don't have the realm configured correctly, and this is causing the SamlTokenProvider to reject the incoming request. Any help would be greatly appreciated, and I have attached my sts and client configuration xml files. Thanks, Dan http://cxf.547215.n5.nabble.com/file/n5643904/sts-servlet.xml sts-servlet.xml http://cxf.547215.n5.nabble.com/file/n5643904/client-config.xml client-config.xml -- View this message in context: http://cxf.547215.n5.nabble.com/No-Token-Provider-for-Saml-Token-V1-1-tp5643904p5643904.html Sent from the cxf-user mailing list archive at Nabble.com.
