We're finally getting up to CAS 5.3.x, and for a variety of reasons, we
built a new server with a different host name. As part of the transition,
we'll be updating the "Third-party identity provider" settings in Google
Apps with the new URL and keys.
As I'm sure others have gone through this, so I
Colin,
Perhaps this approach can work (I assume on the login page, user is selecting a
profile):
1. Redirect from /login to CAS, /cas?service=serviceURL?param=...
2. CAS sends ST to serviceURL
3. ST validation happens, authenticated principal is returned
4. how does spring know where to redirect
None. It disables embedded tomcat auto configuration which creates an API
conflict when deploying to external tomcat with versions less than used in
distributed CAS versions if present.
D.
From: William Jojo
Reply: cas-user@apereo.org
Date: January 8, 2020 at 9:49:59 AM
To: CAS Community
Cc
Dmitriy,
Late to the party on this one. This solution worked for me on Ubuntu 18.04
with distro packaged Tomcat 9.0.16. Thank you!
What are the ramifications of setting this value?
Bill
On Wednesday, November 13, 2019 at 8:58:43 AM UTC-5, Dmitriy Kopylenko
wrote:
>
> For what it's worth - if
Hello,
Ray, Andy, thansks a lot for your responses, I study them quietly.
Regards
Ibrahima
Le mer. 8 janv. 2020 à 02:44, Andy Ng a écrit :
> Hi,
>
> I would highly recommend following
> https://dacurry-tns.github.io/deploying-apereo-cas/introduction_overview.html
> and
> read through it so
