Thanks for the help William - I'll give this all a read, see what I can
come up with. Appreciate it!
On Wednesday, November 22, 2017 at 9:53:46 AM UTC-5, William E. wrote:
>
> Resultant cas management screenshot attached.
> Full disclosure, this is our test CAS 5.1, we haven't deployed to
>
Thank you so much. I tried adding the lines you mentioned in my
cas.properties but still no luck. We've got similar setups the only
dependency I don't have in CAS is below.
org.apereo.cas
cas-server-support-saml-sp-integrations
${cas.version}
On Wednesday, November 22, 2017 at
Nope. In my cas 5.1 pom I only have:
org.apereo.cas
cas-server-webapp${app.server}
${cas.version}
war
runtime
org.apereo.cas
cas-server-support-ldap
${cas.version}
Gotcha. Do you also have these defined in your pom.xml ?
org.apereo.service.persondir
person-directory-api
${person.directory.version}
org.apereo.service.persondir
person-directory-impl
${person.directory.version}
On Tuesday, November 21, 2017 at 10:24:47 PM UTC-5,
I had to add them to mine for the username drop down in cas management to
get populated.
On Tuesday, November 21, 2017 at 2:01:09 PM UTC-6, Justin Andrews wrote:
>
> No, I do not have those in my cas.properties...
>
> On Tuesday, November 21, 2017 at 10:49:13 AM UTC-5, William E. wrote:
>>
>>
No, I do not have those in my cas.properties...
On Tuesday, November 21, 2017 at 10:49:13 AM UTC-5, William E. wrote:
>
> Do you have entries like below in your cas.properties file?
>
> cas.authn.attributeRepository.ldap[0].attributes.uid=uid
>
Do you have entries like below in your cas.properties file?
cas.authn.attributeRepository.ldap[0].attributes.uid=uid
cas.authn.attributeRepository.ldap[0].attributes.displayName=displayName
cas.authn.attributeRepository.ldap[0].attributes.cn=commonName
