[
https://issues.apache.org/jira/browse/WSS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710891#action_12710891
]
Todd Michael commented on WSS-146:
----------------------------------
I have finally had a chance to work on this (sorry for the delay). I have
added support for SAML v1.1 and v2.0 Authorization decision statements, and
re-factored the SAML callback to provide a single point within the library to
perform all application-specific, SAML-related raw data setup. The SAML
callback implementation must be provided by each implementing application and
is essentially identical (in concept) to the password callback that was already
being used by WSS4J. SAML callback implementation allow the host application
to set the subject name qualifier, and all raw data associated with the
creation of SAML v1.1 and v2.0 attribute and authorization decision statements.
I will provide an example of this class along with the patch.
I have also removed all compile and run time dependencies on the OpenSaml v1.x
library (I am currently using OpenSaml 2.2.3). I see that WSS4J is up to
v1.5.7, so I will post a patch tomorrow that includes all of this functionality
that is based on WSS4J 1.5.7 (I'm still finishing up the documentation on the
new features). I hope that you will still have time to take a look at this.
> Upgrade opensaml dependency to 2.x line
> ---------------------------------------
>
> Key: WSS-146
> URL: https://issues.apache.org/jira/browse/WSS-146
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Bob Jacoby
> Assignee: Colm O hEigeartaigh
> Priority: Minor
> Fix For: 1.6
>
> Attachments: wss4j_opensaml2.1.0.patch,
> wss4j_opensaml2.1.0_correct.patch, wss4j_opensaml2.2.3.patch
>
>
> WSS4J has a dependency on opensaml 1.1. OpenSAML 1.1 is, for the most part,
> no longer supported (https://spaces.internet2.edu/display/OpenSAML/OS1Status).
> 2.1 has been out for a while, and 2.2 was released in Oct. '08. The 2.x line
> is not backwards compatible with 1.1 so unfortunately it's not as simple as
> dropping in the newer jar.
--
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]
