I am attempting to utilize the attribute definitions feature, and I have hit a 
wall.

Reference used:

https://apereo.github.io/cas/6.3.x/integration/Attribute-Definitions.html

Implemented in my cas.properties:

cas.person-directory.attribute-definition-store.json.location=file:/etc/cas/config/attributes.json

With the contents of /etc/cas/config/attributes.json:

{
    "@class" : "java.util.TreeMap",
    "testName" : {
      "@class" : 
"org.apereo.cas.authentication.attribute.DefaultAttributeDefinition",
      "key" : "testName",
      "name" : "testName",
      "scoped" : true,
      "attribute" : "uid"
    }
}

I have turned on the following debug in log4j2.xml:

<AsyncLogger name="org.apereo" level="debug" includeLocation="true"/>


When I start up the CAS server there does not seem to be anything related to 
the attribute definitions present.  Hitting up the discovery profile actuator 
does not list the defined attributes in the "availableAttributes".  There is no 
logging in relation to the attribute definitions configuration.

I am aware that we could do custom attributes via return mapped and groovy 
inline scripting, but we want something more broadly available to all services 
instead of per service entry custom attributes.

Does anyone have any guidance/ideas on how to get attribute definition feature 
up and running?

-- 
- 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/f35d5601baaf4b2c8ce309249d0b728d%40mun.ca.

Reply via email to