SSO for both CAS and SAML

[Peters C.L.]

Hmm, I figured that they should use the same session. My idp.properties file is configured such that both idp.session.StorageService and idp.cas.StorageService are set to shibboleth.MemcachedStorageService. I can see sessions appearing in memcached, so it looks like that's working, but alas still getting prompted.
________________________________________
From: users [users-bounces at shibboleth.net] on behalf of Kevin Foote [kevin.foote at colorado.edu]
Sent: 08 March 2017 16:06
To: Shib Users
Subject: Re: SSO for both CAS and SAML

They should be using the same session if you configured the backend storage correctly. Make sure your idp.properties file is indicating what to use for CAS.

- sent from mobile

> On Mar 8, 2017, at 9:02 AM, Peters C.L. <C.L.Peters at soton.ac.uk> wrote:
>
> Hi all,
>
> I've got Shibboleth 3.3 configured with both CAS and SAML endpoints configured and everything there seems to be working fine, but we'd like it so that when you sign-in to something using CAS, it uses the same user for any future SAML sessions too.
>
> For example, if I log in to an app with SAML using Shib, and then go to another app and log in with SAML using Shub, I don't get prompted to enter a username again and it signs me in with the same user automatically. However, when I log in to an app with CAS using Shib and then log in to another app with SAML using Shib, I get prompted for a username again, despite the fact that a Shibboleth session already exists.
>
> Is there any way for the CAS endpoints to use the same session details as the SAML endpoints to negate this second login? Or is this not possible?
>
> Thanks,
>
> Clayton
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net