Thank you Carl for your reply,
i am wondering if it s not related to SAML because i have the same config
that works fine for CAS protocol based SPs ...but for SAML bases ones
nothing,
I would be very thankful if someone can help me.
Thanks.
Le jeu. 23 sept. 2021 à 16:35, Carl Waldbieser a
We are using CAS 6.x. I have a SAML entry in my allow list that looks
similar to this:
{
"@class": "org.apereo.cas.services.RegexRegisteredService",
"serviceId": "Entity ID goes here ...",
"id": 1000,
"evaluationOrder": 1000,
"name": "SAML Provider",
"description": "Blah
hello cas community,
wish you are doing great,
i am having little issues having to work access strategy with SAML based
service
more precisely, i am trying to implement access restrictions based on
group membership but for now all users are able to logon on the app
regardless of their
I've have a working CAS 5.3.3 system with multiple services (21 using cas
protocol, 1 using saml2).
I am trying to get access strategy working with the SAML2 service. When I
log in with an authorised person, all is good. When I attempt a login
where someone is not allowed, I get the
there in a point release.
Thanks!
Tom.
From: <cas-user@apereo.org> on behalf of Travis Schmidt
<travis.schm...@gmail.com>
Reply-To: "cas-user@apereo.org" <cas-user@apereo.org>
Date: Friday, February 23, 2018 at 8:11 AM
To: "cas-user@apereo.org" <cas-user@a
Schmidt
*Sent:* Friday, February 23, 2018 10:11 AM
*To:* cas-user@apereo.org
*Subject:* Re: [cas-user] Access Strategy not working???
The property was changed in 5.2 to cas.serviceRegistry.json.location. 5.2
currently ignores unknown properties and falls back to default on this. I
got bit
The property was changed in 5.2 to cas.serviceRegistry.json.location. 5.2
currently ignores unknown properties and falls back to default on this. I
got bit by this on a deployment two weeks ago. Also the property names for
webflow and tgc encryption were changed, so check those as well.
On
CAS users,
Ok, I am on CAS 5.2 on Redhat 7.
I have created a number of services stored in json files in
/etc/cas/services. But I don’t think any of them are getting read by CAS.
The CAS-Management creates them and puts them there. But I am not sure
CAS is reading them there. My goal
