yes
From: cas-user@apereo.org on behalf of Bryan Wooten
Sent: Monday, June 15, 2020 4:30:15 PM
To: cas-user@apereo.org
Subject: Re: [cas-user] CAS 6 Attribute release not working
Thanks for the hint.
So to clarify, cas.authn.ldap[0].principalAttributeList
Thanks for the hint.
So to clarify, cas.authn.ldap[0].principalAttributeList is the superset of
attributes that may be released. The service registry json defines the
attributes (subset) allowed to be released to the service?
-Bryan
On Mon, Jun 15, 2020 at 3:08 PM Jason Everling
wrote:
> I
I didnt think CAS pulls attributes from ldap based on the service
definition? You have to add all attributes you expect to fetch from ldap,
so in your config
cas.authn.ldap[0].principalAttributeList=unid,cn,psrole,mail,uuemployee,uustudent,uuaffiliate,uudept,almail,sn,givenName
Change it to
Hi all,
We are unable to get attributes to release (CAS 6 Master).
Java client 3.6.1
We have a json service registry entry:
{
"@class" : "org.apereo.cas.services.RegexRegisteredService",
"serviceId" : "^https://cas6test.go.utah.edu/.*;,
"name" : "cas6testGoUtahEdu",
"id" : 2020052801,
I added those log settings...
We also tried changing our gradle.properties from SNAPSHOT to RC5 and that
just broke the Duo login flow...
I added this to cas.properties: #Attribute Release
cas.authn.authenticationAttributeRelease.enabled=true
And I also change the JSON service registry
Bryan,
Maybe these loggers can help.
Ray
On Mon, 2020-06-01 at 08:34 -0600, Bryan Wooten wrote:
We are doing a POC with CAS 6. We are building using the war overlay. Are build
is from the CAS 6 Master branch.
I have a simple Java client app configured for
We are doing a POC with CAS 6. We are building using the war overlay. Are
build is from the CAS 6 Master branch.
I have a simple Java client app configured for SAML1.1. This app is running
on the same Tomcat as CAS 6 itself. This is its JSON service registry entry:
{
"@class" :
