--
You received this message because you are subscribed to the Google Groups "CAS Developer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-dev+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-dev/d357fe9b-401b-4173-af92-c36aa2fe6d2e%40apereo.org.
Thanks for your answer, but unfortunately they are not equal both.
I've remote debugged my IdP running 6.2.0-RC3 and Bean CasPersonDirectoryLdapConfiguration inside CasPersonDirectoryConfiguration.java (line 371) was not created, unless I changed cas.authn.attributeRepository.ldap[0].ldapUrl to cas.authn.attribute-repository.ldap[0].ldapUrl.
Cheers, Robert
CAS uses Spring Boot’s “relaxed binding”, https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config-relaxed-binding so both styles are OK.D.
On March 5, 2020 at 07:13:33, Robert (robert.k...@gmail.com) wrote:
Hi there,--yesterday I've stumbled across CasPersonDirectoryConfiguration.java in cas-server-support-person-directory, while debugging, why my LDAP configuration is not used to retrieve attributes (jdbc, json and stub were).I've found out, that CasPersonDirectoryLdapConfiguration is conditionally created when property cas.authn.attribute-repository.ldap[0].ldapUrl exists.My cas.properties was using cas.authn.attributeRepository.ldap[0].ldapUrl, as in the documentation mentions.Now I found, that there are alot more of these different usages in source code and documentation. Sometimes its cas.authn.attribute-repository and sometimes its cas.authn.attributeRepository. Should I create a PR to unify them or is that on purpose?Cheers, Robert.
You received this message because you are subscribed to the Google Groups "CAS Developer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas...@apereo.org.