The cas/proxy issue set us backwards to CAS 5.0.5. See my posting on the CAS developer group which I have just updated. We need cas/proxy to get our applications through the CAS login process in order to verify if the long URL issue with either of these later releases.
On Friday, August 18, 2017 at 2:42:54 PM UTC-7, Duane Booher wrote: > > We have cas.authn.ldap[0].passwordPolicy.warningDays=5 firing a password > change warning from casLoginMessageView.html > > When we press continue, then the URL fires with login?execution=... being > too long for the Windows IE/Edge browsers. > > It works for all of the other host browsers, are there any alternatives to > this? > > Duane > > > -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/c91b70d6-b548-4b5b-9923-3d2c5b07b90f%40apereo.org.
