[ 
https://issues.apache.org/jira/browse/CXF-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693883#comment-13693883
 ] 

Colm O hEigeartaigh commented on CXF-4457:
------------------------------------------


Ok I have committed a fix along the lines of Dan's suggestion. So the service 
configuration should now work without having to add any ".sct" configuration 
values. You still need to add ".sct" for the client "ws-security.sts.client" 
configuration though. This is due to the fact that we need to separate the 
STSClient objects used to communicate with the STS (inner) and to orchestrate 
SecureConversation (outer).

Colm.
                
> Extend WS-SecureConversation to support SAML Assertions for authentication
> --------------------------------------------------------------------------
>
>                 Key: CXF-4457
>                 URL: https://issues.apache.org/jira/browse/CXF-4457
>             Project: CXF
>          Issue Type: Improvement
>          Components: WS-* Components
>            Reporter: Glen Mazza
>            Assignee: Colm O hEigeartaigh
>         Attachments: cxf-tutorial.patch
>
>
> Hi, as shown for GlassFish Metro:
> https://gist.github.com/3191480 
> Support the following authentication mechanism:
> 1.) The WSC gets a SAML assertion from the STS.
> 2.) The WSC sends that SAML assertion to the WSP to get the SCT from the WSP
> 3.) All subsequent real calls for doubled numbers between WSC and WSP use the 
> SCT and not the SAML assertion.
> Here is a Netbeans-generated WSDL for this scenario:
> https://github.com/gmazza/blog-samples/blob/master/cxf_sts_tutorial/service/src/main/resources/DoubleItSecrConv.txt
> A sample testcase that can be used (steps to use: update WSP WSDL with the 
> one above, run mvn clean install tomcat7:redeploy from base folder, then mvn 
> exec:exec from client folder): 
> https://github.com/gmazza/blog-samples/tree/master/cxf_sts_tutorial

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to