Hello C Ryan,
I'm struggle with it long time and i would like ask you like in other
topic ,have you digged solloution, could you share it if it is no problem
for you ? Documentaion is like is ;) you know.
In my instastane i have 3 AD handlers and i would like to have control
over it
an exception.
Thanks,
Tom
From: cas-user@apereo.org On Behalf Of Colin Ryan
Sent: Friday, October 23, 2020 2:42 PM
To: cas-user@apereo.org
Subject: [EXT] Re: [cas-user] Strict Authentication Source Policy with newer
Authentication Policy approach - CAS 6.2.3 - still.
CAUTION: This email originated from
So this is the current format of this configuration, I'm using the
wildcard and the /cas/login page itself to simply verify things.
{
"@class" : "org.apereo.cas.services.RegexRegisteredService",
"serviceId" : "^(https|imaps)://.*",
"name" : "HTTPS and IMAPS",
Ray,
That's where I picked up the configurations for what I've been trying
but it seems like it's still falling through past the Handler I want to
be required.
Was just wondering if I'm misinterpreting the need for or the context
of using the criteria configurations as well.
The
Colin,
Could this be what your are looking for,
https://apereo.github.io/cas/6.2.x/services/Configuring-Service-AuthN-Policy.html
Ray
On Tue, 2020-10-20 at 14:24 -0400, Colin Ryan wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious
Folks,
I have 2 authentication sources. I have services that I want strictly
to only accept success via a specific source. Even if the same
credential pair could succeed in either.
I've been trying to user the "newer"? authenticationPolicy approaches
as the logs in my 6.2.3 builds were
