[cas-dev] SAML1.1 support in CAS3.1

[Bas Toeter]

Sorry, only have two days to proof the concept, I'll see what I can do
in the time we have left, but by all means: don't hold your breath...

I was looking at SamlCompliantUniqueTicketIdGenerator.java and noticed
that the SAML artifact is created like so:

final SAMLArtifact samlArtifact = new
SAMLArtifactType0002(this.randomStringGenerator
            .getNewStringAsBytes(), new URI(this.sourceLocation));

It uses org.opensaml.artifact.SAMLArtifactType0002. The other end (SAP)
is complaining it can't deal with Artifacts of Type2. I'll try sticking
a SAMLArtifactType0001 object in there instead and see how that goes.

I think I need help with the differences between SAML1 and SAML1.1 and
SAML2.0 myself ;-) Especially their relation to the type1 and type2
artifacts.

Thanks,
Bas.


Scott Battaglia wrote:
> It most likely could be configured to support SAML 1.0.  Would you be
> willing to help us with this?  I'm not 100% familiar with SAML so I
> would need help with the differences between SAML 1 and SAML 1.1
> 
> Thanks
> -Scott
> 
> On 2/5/07, *Bas Toeter* <b.toeter at uva.nl <mailto:b.toeter at uva.nl>> wrote:
> 
>     Hello list,
> 
>     I was looking at M1 (CAS 3.1) while doing a proof of concept to casyfy
>     SAP portal. We were able to pretty quickly, basically effortless, set up
>     CAS 3.1 and direct SAML requests at it. However our SSO target only
>     supports SAML1.1, is there a way to make /samlValidate return version 1
>     SAML artefacts?
> 
>     Thanks,
>     Bas.
>     _______________________________________________
>     cas-dev mailing list
>     cas-dev at tp.its.yale.edu <mailto:cas-dev at tp.its.yale.edu>
>     http://tp.its.yale.edu/mailman/listinfo/cas-dev
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev