[
https://issues.apache.org/jira/browse/CXF-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685858#comment-13685858
]
Daniel Kulp commented on CXF-4457:
----------------------------------
Colm,
One thought: we could copy all the non ".sct" values over first, then copy the
.sct values which would then override anything set the first pass. That should
keep any backwords compatibility, also allow individual control of each of the
STSClients, but also be a bit simpler if that flexibility isn't required.
Dan
> 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
