Ray,
I had already set the attribute release directive in the basic HTTPIMAP
all access service definition.
You've helped my brain tweak on the concept that only principal
attributes are automatically released while all others must be
explicitly added to defaults or service definitions. But your example
below is for LDAP auth. I'm trying to use RADIUS auth - which is
releasing Framed Protocol and Service Type - and using LDAP to fill out
the attribute set, via cas.authn.attribute-repository.ldap[].....
I set the debug to what you suggested and Logged in to the CAS default
Login page and just see the RADIUS attribute, and no reference in the
logs to AbstractRegisteredServiceAttributeReleasePolicy.
Is the "Click here to view attributes resolved and retrieved for "
expected to show all the native and resolved attributes, I want to make
sure I'm using the right test instrument.
My service definition is:
{
"@class" : "org.apereo.cas.services.RegexRegisteredService",
"serviceId" : "^(https|imaps)://.*",
"name" : "HTTPS and IMAPS",
"id" : 10000001,
"attributeReleasePolicy" : {
"@class" : "org.apereo.cas.services.ReturnAllAttributeReleasePolicy"
}
}
Sorry for my naivete..
Colin
On 2019-10-29 12:40 p.m., Ray Bon wrote:
You can set attributes to be released by default (normally no
attributes are released),
cas.authn.ldap[1].principalAttributeList=mail, \
cn, \
sn
--
- 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 "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/64ed2a6b-46c7-d2f2-129d-64f116e62b84%40caveo.ca.
