Re: [cas-user] Re: making an extra LDAP attribute visible via CAS

2018-11-14 Thread Baron Fujimoto
We achieve this with 5.0.x with the equivalent of the following in our service registy entry: "attributeReleasePolicy" : { "@class" : "org.apereo.cas.services.ReturnMappedAttributeReleasePolicy", "allowedAttributes" : { "@class" : "java.util.TreeMap", "udcid" :

Re: [cas-user] Re: making an extra LDAP attribute visible via CAS

2018-11-13 Thread Matthew Uribe
Zach, Looking at the docs for 5.0 I see that it doesn't seem to support multiple LDAP servers, so the cas.authn.attributeRepository.ldap[0].attributes.udcid=UDC_IDENTIFIER that you see in other posts here would actually be more like this:

Re: [cas-user] Re: making an extra LDAP attribute visible via CAS

2018-11-13 Thread Zach Tackett
This is the data we are getting back externally array(7) { ["samlAuthenticationStatementAuthMethod"]=> string(39) "urn:oasis:names:tc:SAML:1.0:am:password" ["isFromNewLogin"]=> string(4) "true" ["authenticationDate"]=> string(47) "2018-11-13T09:47:56.786-05:00[America/New_York]"

Re: [cas-user] Re: making an extra LDAP attribute visible via CAS

2018-11-13 Thread Zach Tackett
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, >

Re: [cas-user] Re: making an extra LDAP attribute visible via CAS

2018-11-13 Thread Matthew Uribe
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

Re: [cas-user] Re: making an extra LDAP attribute visible via CAS

2018-11-13 Thread Daniel Widrick
note that the attributeRepository is part of a services JSON file. not the cas.properties file. Ours looks as as follows because of some weirdness with attribute names previously. { "@class" : "org.apereo.cas.services.RegexRegisteredService", "serviceId" : "https://.*;, "name" : "HTTPS",

Re: [cas-user] Re: making an extra LDAP attribute visible via CAS

2018-11-13 Thread Zach Tackett
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 >

Re: [cas-user] Re: making an extra LDAP attribute visible via CAS

2018-11-13 Thread Mac Reid
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