Hello everyone,
I'm trying to get CAS up and running. Authentication works fine, but my client
application needs to get a user's ldap groups. I added a
CredentialsToLDAPAttributePrincipalResolver to my authentication manager, and
on the client side I added the Saml11TicketValidationFilter. I
CAS4 is actually using OpenSAML2. I haven't actually tested the support yet
that I wrote (I need to write unit tests tonight). *If* everything works
okay I can attempt to backport it. Though note that OpenSAML2 isn't in the
public Maven repository (other than the ones someone else put in there)
> I think that having one of a security product's dependency as
> unsupported is a pretty big deal and shouldn't be marginalized.
While you're right in theory, in practice it's hardly as dire as
marginalization. The lines of communication between the Shib and CAS
projects are open and working. (
Greetings,
On Tue, Feb 22, 2011 at 8:11 AM, Marvin Addison
wrote:
>> Now that 3.4.6 is out the door, congratulations, will we see an update
>> to the supported version of SAML? Thanks!
>
> It's certainly not reasonable to move to SAML 2 in CAS 3.4.x. While
Ok, that makes sense. I know that CAS
> Now that 3.4.6 is out the door, congratulations, will we see an update
> to the supported version of SAML? Thanks!
It's certainly not reasonable to move to SAML 2 in CAS 3.4.x. While
it may be feasible to move to the SAML 2.x libs and use the SAML 1.1
support therein, there seems marginal value
Ping. :-)
On Mon, May 3, 2010 at 5:03 PM, wrote:
>
> Thanks for the clarification. We'll also hopefully be migrating to 2 sometime
> soon.
>
> -Original Message-
> From: Brent Putman
>
> Also, be aware that as of June 30, 2010, OpenSAML 1.x will be in a
> wholly unsupported status (as
