m/sp/SAML/26912657608931/callback]
is not found in service registry.]>
2021-04-12 16:27:27,481 DEBUG [org.springframework.webflow.engine.support.Transi
tionExecutingFlowExecutionExceptionHandler] -
Keith Alston
Regent University
IT Department
keit...@regent.edu
757.352.4081
________
Oops, I had meant to paste this. This should allow anything with domain.com
and prefix regent-team.myfresh to authenticate against your CAS server.
^(https|http):\/\/regent-team\.myfresh.*domain\.com(:[0-9]{1,5})?\/.*$"
From: on behalf of Trenton Adams
Reply-To: "cas-user@apereo.
I’m pretty sure the serviced is supposed to be a regular expression, no?. *
after an ‘h’ means repeat the ‘h’. Put ‘.*’ and you’ll repeat anything, but
that wouldn’t be what you want either, as that would allow any domain with a
DNS prefix of ‘regent-team.myfresh’, to authenticate against
Those docs appear to imply that passivators are essentially require, or
authenticated state information gets shared, no?
From: cas-user@apereo.org on behalf of David Curry
Sent: January 10, 2020 5:15 PM
To: CAS Community
Subject: Re: [cas-user] cas 5.2.x
So, with the features we're using, CAS 5.2.x, tomcat startup takes 4 minutes on
a single core, and 1 minute on a quad core system. So, every single change I
make to the config takes a long time to try it out.
Why does it take so long? It seems like maybe it's Spring Bloat, no? I can't
