cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Shakirin (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CXF-4668) STS: provide callback to modify AssertionWrapper before signing
Date Mon, 17 Dec 2012 09:08:12 GMT

     [ https://issues.apache.org/jira/browse/CXF-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrei Shakirin reassigned CXF-4668:
------------------------------------

    Assignee: Andrei Shakirin
    
> STS: provide callback to modify AssertionWrapper before signing
> ---------------------------------------------------------------
>
>                 Key: CXF-4668
>                 URL: https://issues.apache.org/jira/browse/CXF-4668
>             Project: CXF
>          Issue Type: Improvement
>          Components: Services
>            Reporter: Andrei Shakirin
>            Assignee: Andrei Shakirin
>
> STS issues SAML Token using WSS4J to parse SAMLCallback object into SAML Assertion.
> Actually STS issue operation doesn't provide callback to customize SAML Assertion directly.
> Due some restrictions in WSS4J SAML representation (for example ConditionsBean doesn't
support extensions, etc), it makes sense that user has possibility to modify/customize created
SAMLToken before signing.
> It can be done in method SAMLTokenProvider.createSamlToken(), callback's argument is
AssertionWrapper.
> Corresponded mail list discussion: http://cxf.547215.n5.nabble.com/Customizing-Conditions-in-CXF-STS-td5719270.html.

--
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

Mime
View raw message