That is actually negating the whole point. The point is that the federated
services registrar is the one maintaining the services metadata. The IdP on
the other hand does not have to worry about individual services but only
has to setup a *group* service definition with a URL metadata endpoint
You can update your instance by copying in differences from
https://github.com/apereo/cas-overlay-template
Ray
On Tue, 2024-02-20 at 07:18 -0800, atilling wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious with links and sensitive infor
At least the way the documentation is written for the provided example, it
does not suggest a logical OR when evaluating the conditions (in my
interpretation).
"The principal *also* must not have an attribute role whose value matches
the pattern deny.+."
In our case it is in fact the same (multiv
Nope, I apparently erred in my testing. It does in fact seem to work as
expected. I went over the permutations once again (more meticulously this
time), and recorded the following results:
required: ABAC_attribute == "required_allow_value"
reject: ABAC_attribute != "rejected_deny_value"
desired
Test OIDC and see if it sends encrypted tokens.
Ray
On Tue, 2024-02-20 at 10:08 +0100, Lanfdetroy wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious with links and sensitive information.
Hello,
I use Redis instead of Hazelcast.
I had
We tried to follow the same posts you've linked, we were not able to get
the regular expression serviceId to function, always threw an error if we
tried to use that service. We did find we could add multiple services with
the same metadata (Like the almond and coco examples) and those are workin
The Initializr previously had a parameter that allowed you to create an
overlay for a specific version casVersion no longer seems to work and
specifying -version or -d version seems to have no effect.
I understand pushing to use the latest version of cas and cas-management
but we want an overla
Hello
We 've been using CAS 6.6 with no problems as an IdP for multiple protocols
(CAS, OIDC, SAML) while using Shibboleth for federated SAML services. We
are using a MariaDB as our service definition data store.
We are investigating the possibility of migrating federated SAML services
to CAS
