I have the same issue and cannot find a workaround. Did you have any luck?
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are sub
Did you find a way? We're having same issue.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups
Using Elasticsearch for CAS auditing here. Filebeat agent tails the cas
audit logs and sends to logstash for parsing/field mappings then off to
Elasticsearch. Kibana web front end for pretty dashboards/reports. We
have about 15 months worth of CAS audit logs from 30k users in our
Elasticsear
Thanks, Arnold. There are options in the management app to input a Service
Provider Name Qualifier and Name Qualifier, but no option to disable it.
Providing a blank name yields the serviceId/entityID in the NameQualifier
and SPNameQualifier in the NameID portion of the SAML response by defaul
5.1.4:
covf...@maga.us
5.3.3-SNAPSHOT:
https://www.rarepepes.com";
SPNameQualifier="https://www.rarepepes.com"* >covf...@maga.us
Seeing an odd issue between CAS versions regarding SAML responses.
Specifically, I have found in 5.3.3 the NameID portion of the response
includes NameQualifier and
If I start cas.war and wait for it to complete, then start
cas-management.war - then CAS Management app starts fine without the hang
up during Tomcat start.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
-
I've deployed CAS Management 5.3.3-SNAPSHOT and its hangs during Tomcat
startup as well.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message bec
https://apereo.github.io/cas/5.2.x/integration/Attribute-Release-Policies.html#inline-groovy-attributes
We are using 5.1.4 in production and 5.2.7 in test. Noticed an issue in
5.2.7 with inline groovy attributes.
"uid" : "groovy { return attributes['uid'] + ' is great' }"
For example, this ret