[
https://issues.apache.org/jira/browse/RAMPART-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746412#action_12746412
]
Thilina Buddhika commented on RAMPART-231:
------------------------------------------
Actually there is a dependency for WSS4J other than the SAML 2 token
validation. RampartEngine stores the secret and the SAMLToken in its
TokenStorage. For this, some of the utility functions provided by WSS4J is
used. For example, in SAML 1.1 implementation, SAMLKeyInfo and SAMLUtil classes
are used for this purpose which are provided along with WSS4J. So in my
implementation, I followed the same approach to keep the code consistent and
moved that functionality to WSS4J.
Since, we are not moving ahead with a new WSS4J version for Rampart 1.5, it is
possible to take those functionalities into Rampart until a WSS4J release is
done. This is only a *TEMPORARY FIX* and it should be cleaned up as soon as we
get these functionality with WSS4J.
WDYT?
Thanks.
/thilina
> Implementing the SAML 2.0 support in Rampart
> --------------------------------------------
>
> Key: RAMPART-231
> URL: https://issues.apache.org/jira/browse/RAMPART-231
> Project: Rampart
> Issue Type: New Feature
> Components: rampart-trust
> Affects Versions: 1.4
> Reporter: Thilina Buddhika
> Assignee: Nandana Mihindukulasooriya
> Attachments: rampart-modified.patch, rampart.patch
>
>
> Currently Rampart only supports the previous versions of SAML, but not SAML
> 2.0. But having the support for SAML 2.0 is vital and it will benefit the
> Rampart users a lot. So it will be great to have SAML 2.0 support in Rampart.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
