[
https://issues.apache.org/jira/browse/WSS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771394#action_12771394
]
Thilina Buddhika commented on WSS-204:
--------------------------------------
Sure, I will update the pom.xml with the corrected artifact id for OpenSAML
1.1.
Yes, I followed the same approach as SAMLTokenProcessor in SAML2TokenProcessor
as the first step. Definitely we can improve this to add token as signed and
unsigned and validate the signatures(if the token is signed). Also Hakon has
done an implementation to validate the signature of the message [1].
So shall we keep this as the first step and then improve it later ?
I will provide a modified patch with the other changes you suggested.
Thanks.
/thilina
[1] -
http://mail-archives.apache.org/mod_mbox/ws-rampart-dev/200910.mbox/%[email protected]%3e
> Support validating SAML 2.0 tokens
> ----------------------------------
>
> Key: WSS-204
> URL: https://issues.apache.org/jira/browse/WSS-204
> Project: WSS4J
> Issue Type: New Feature
> Components: WSS4J Core
> Affects Versions: 1.5.8
> Reporter: Thilina Buddhika
> Assignee: Colm O hEigeartaigh
> Fix For: 1.5.9, 1.6
>
> Attachments: wss4j.patch
>
>
> With the patch submitted for Rampart-231, SAML 2.0 support will be available
> for Rampart. That patch only generates SAML 2.0 tokens as per the SAML Token
> Profile 1.1 specification. SAML 2.0 validation support is mandatory for the
> full completion of 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
