cas/p3/login ?

[atilling]

I'm configuring an application that was designed to work with version 2 protocol but with the modification to release attributes.

The application has one location to add the cas context path if I set the path to /cas the application logs in fine but can't get the attributes, if I set the path to /cas/p3 the application tries to redirect to /cas/p3/login?service=xxx which fails because that path isn't right for the login page.

Is there a way to make /cas/p3/login, /cas/p3/logout etc redirect to the correct URL? It looks like I could change the URL in CasProtocolConstants but that would break other applications.

I would suggest to make the redirect or some sort of alias standard to support these applications because I believe there are a lot of them.

[Mukunthini Jeyakumar]

I've ended up with the situation same as yours when I was configuring libauth with CAS v5.  Have you find the way to solve this?

Thanks

[Misagh Moayyed]

This might help: https://apereo.github.io/2017/06/23/cas-protocol-compatibility/