Different SSO behaviour in CAS 5.0.4?

68 views
Skip to first unread message

Manfredo Hopp

unread,
Apr 11, 2017, 5:21:44 PM4/11/17
to Cas
Hi,

I recently installed cas 5.0.4 and tested SSO with 2  web applications which are running under version 4.0.1 installed in production.

The test sequence was the same as for 4.0.1 e.g. ( in chronological order):

1. Login to casified application A requires cas login
2. Redirect to casified application B with SSO enabled does NOT require signing in.

but on 5.0.4 step 2. requires login in again.

Through cas-management I can see that services have SSO enabled by default.

I made a revision of properties used but found no reason for this different behaviour.

Regards Manfredo


Andrew Tillinghast

unread,
Jun 16, 2017, 7:40:13 AM6/16/17
to cas-...@apereo.org
I'm seeing the same effect in CAS 5.1.0 I have checked the properties for TGC and I have made sure that enable SSO is set in the service manager but every service still requires login.

--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscribe@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAB623R_ShsHHJjObJ_9Bi0opwVRqLya-8SB8_xjQyAxNMaLCTQ%40mail.gmail.com.



--
Andrew Tillinghast
Sr. Web Developer
270 Mohegan Avenue
New London, CT 06320-4196
P Think before you print
CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system.

Castang

unread,
Jun 27, 2017, 2:29:49 PM6/27/17
to CAS Community
Were you ever able to find a solution to this? We're experiencing the same issue on 5.1.1


On Friday, June 16, 2017 at 7:40:13 AM UTC-4, atilling wrote:
I'm seeing the same effect in CAS 5.1.0 I have checked the properties for TGC and I have made sure that enable SSO is set in the service manager but every service still requires login.
On Tue, Apr 11, 2017 at 5:21 PM, Manfredo Hopp <mhopp....@gmail.com> wrote:
Hi,

I recently installed cas 5.0.4 and tested SSO with 2  web applications which are running under version 4.0.1 installed in production.

The test sequence was the same as for 4.0.1 e.g. ( in chronological order):

1. Login to casified application A requires cas login
2. Redirect to casified application B with SSO enabled does NOT require signing in.

but on 5.0.4 step 2. requires login in again.

Through cas-management I can see that services have SSO enabled by default.

I made a revision of properties used but found no reason for this different behaviour.

Regards Manfredo


--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.

Richard Frovarp

unread,
Jun 28, 2017, 3:36:16 PM6/28/17
to cas-...@apereo.org
Have you verified that you're getting the right cookies? Kind of sounds like the cookies are being issued for a different domain and/or path than where CAS is being requested.
Reply all
Reply to author
Forward
0 new messages