November 19, 2018 at 10:07 pm #23902
I am running openam and opendj in two separate Docker containers and am trying to connect to the external data store on the opendj container. Do I need to do anything special in order to connect those two containers? It seems that just using the FQDN (which is actually localhost on the host machine) will not quite get the job done.
Anyone try this already?
Thanks!November 19, 2018 at 11:40 pm #23905
Trying to define the connection using the Docker service does not seem to work — users created in opendj do not show up in openam. In order to use the Docker service way, I am defining the LDAP server as
opendj:389where opendj is the name of the service started in Docker Compose.November 20, 2018 at 3:27 pm #23913
did you try use dj ip instead of fqdn?November 20, 2018 at 3:30 pm #23914
Have not tried the IP address yet. I just tried to ping
opendj(which is the service name) from the openam container and that does work so maybe this is already working and I just don’t know…November 20, 2018 at 3:32 pm #23915
well..you can use opendj user to login openam to do the testing..November 20, 2018 at 3:36 pm #23916
Good idea. That unfortunately results in an authentication failed. This is the user created in opendj prior to connecting openam to this external data store:
ou: OpenAM Administrator
cn: OpenAM Administrator
So with login
openam/passwordI should be able to log in, right?November 20, 2018 at 3:43 pm #23917
Correct. Are you sure the data store configuration is correct? like ou, user search attribute(this should be cn for you, since i didnt see uid), etc?November 20, 2018 at 3:50 pm #23918
I have tried both with cn=”Directory Manager” and cn=”OpenAM Administrator” and neither works.November 21, 2018 at 3:48 pm #23932
Following up on this thread, the cn=Directory Manager user was able to connect to the opendj instance. However, it required checking the “Load schema when finished” checkbox on the Data Stores tab.
The cn=OpenAM Administrator user still cannot connect.November 21, 2018 at 3:53 pm #23933
<service name>:<port on container>is the right way to access the opendj instance.
You must be logged in to reply to this topic.