The CAS server is working, we are using 5.0. Currently getting CAS to map
the employeeID to the UDC_IDENTIFIER internally, but it is not mapping it
externally in our test data being dumped after logging in.
On Tuesday, November 13, 2018 at 10:28:31 AM UTC-5, Matthew Uribe wrote:
>
> Hi Zach,
>
> I think you're leaving everyone here in the position of having to assume
> which version of CAS you're using, as well as what you currently have in
> place. Do you have a working CAS server now? What version are you working
> on?
>
> Thanks,
> Matt
>
> On Tuesday, November 13, 2018 at 8:08:08 AM UTC-7, Zach Tackett wrote:
>>
>> I tried what you mentioned and everytime I rebuild the CAS server it
>> breaks because it doesn't like the .attributeRepository part of the
>> attribute
>>
>> On Tuesday, November 13, 2018 at 9:54:57 AM UTC-5, Mac Reid wrote:
>>>
>>> Assuming a working ldap attribute repository, we added the following
>>> line to our cas.properties:
>>>
>>> cas.authn.attributeRepository.ldap[0].attributes.udcid=UDC_IDENTIFIER
>>>
>>> In the above line, the udcid is the ldap attribute and the
>>> UDC_IDENTIFIER is the CAS name for the attribute.
>>> In our Banner service file, we have the following:
>>>
>>> attributeReleasePolicy: {
>>> @class: org.apereo.cas.services.ReturnAllowedAttributeReleasePolicy
>>> allowedAttributes: ["java.util.ArrayList", ["UDC_IDENTIFIER"]]
>>> }
>>>
>>> For reference:
>>> https://apereo.github.io/cas/5.1.x/installation/Configuration-Properties.html#ldap
>>>
>>> - Mac
>>>
>>
--
- 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/0cea9b7e-f247-40d2-a65a-d7c179d633b3%40apereo.org.
