The file in the WAR file I'm using is called "ldap-groups-null.xml", but
changing that still didn't fix the problem.

There are a fair # of discrepancies between the property names in the
uaa.yml file and those in the published API. Should I go with the names in
uaa.yml, which I've seen working?

On Mon, Aug 22, 2016 at 12:26 PM, Eric Promislow <eric.promislow(a)gmail.com>
wrote:

This log entry might point to the problem. Will investigate...

c-7] .... ERROR --- HomeController: Caused by: org.springframework.beans.
factory.BeanDefinitionStoreException: IOException parsing XML document
from URL [file:/usr/local/tomcat/webapps/ROOT/WEB-INF/classes/ldap/ldap-no-groups.xml];
nested exception is java.io.FileNotFoundException:
/usr/local/tomcat/webapps/ROOT/WEB-INF/classes/ldap/ldap-no-groups.xml
(No such file or directory)




On Mon, Aug 22, 2016 at 11:38 AM, Eric Promislow <eric.promislow(a)gmail.com

wrote:

I'm trying to use the UAA API to add an LDAP server dynamically, compared
to specifying one in uaa.yml and restarting uaa.

In the YAML file I had to set spring_profiles to "postgresql,ldap"

I haven't found anything analogous in the UAA API, but ensuring that the
new ldap identity-provider is active isn't sufficient.

Any suggestions?

- Eric