Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Wiki : Interrupting a CAS Login Session #196

Open
Jognu opened this issue Jul 8, 2017 · 2 comments
Open

Wiki : Interrupting a CAS Login Session #196

Jognu opened this issue Jul 8, 2017 · 2 comments

Comments

@Jognu
Copy link

Jognu commented Jul 8, 2017

Hello,

It's not an issue but the "Interrupting a CAS Login Session" page on the wiki need an update.
The structure of the CAS project with 5.* version is very different from the one of the wiki (4.*)

Except the login-webflow.xml, everything else seems to have change.

Any idea what is the new method ? @idwright maybe did you did one ?

Thanks

https://github.com/pwm-project/pwm/wiki/Interrupting-a-CAS-Login-Session
@JasonEverling
Copy link

@Jognu I wrote the one for CAS 3.x/4.x . We are still on 4.x , I briefly went over the docs for 5.x, doesn't look to be too much of a change, some of the webflow changed and it is using the templates for pages instead of jsp. If I get some time next week I'll take a look at what is needed for 5,x.

Jason

@JasonEverling
Copy link

JasonEverling commented Apr 5, 2020 •
edited
Loading

@Jognu I wanted to pass on some information to you since we finally updated our CAS instances and are now on v 6.1.x of CAS which has a built in interrupt feature for services, https://apereo.github.io/cas/6.1.x/webflow/Webflow-Customization-Interrupt.html .

So the way we now have it setup, is using the Rest interrupt configuration in CAS which then does an auto-redirect and the CAS link defined is "https://pwm.example.com/pwm/private/CommandServlet?processAction=checkAll&forwardURL=https://the.original.destination" . Since it is an auto-redirect we just put in the CAS interrupt html template <body style="display:none;"> so that the end user just sees basically a blank page for maybe 5 milliseconds

We use a second instance of pwm just for interrupts and we use the HTTP SSO Header which the remote user header is created using Apache's mod_auth_cas

This has made it so much easier than having to modify the many parts of CAS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Jognu @JasonEverling