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 is
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
Okay, so I found the "problem".
First of all, I checked the CASCookiePath folder and the cookie was created
correctly and all the necessary information was there.
At this point, I knew it was just a display problem and I replaced the php
part of the secured-by-cas/index.php by this :
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,
Hrm. Sadly that doesn't seem to be working. It's so annoying that I don't
even have any indication as to why. If the logs would spit out what is
broken I could fix it but it seems like CAS isn't even aware that I've
enabled WS-FED. :c
On Wednesday, June 10, 2020 at 9:55:00 AM UTC-5, Robert
