Closed migace001 closed 2 years ago
Hello @migace001, Could you provide more details about the issue?
I sure can, I have an existing openldap server, i have gotten my ldifs that i need to import. When i use the osixia openldap it creates an organizational unit rather than a domain. I have attached a sreenshot of my original domain definition and the definition that gets created with the osixia, I need it to be defined as top domain so that my backup ldif can import definitions into it. Capture 1 is what i get with osixia openldap, Capture 2 was a manual build. What do i have to do to get it defined as like Capture 2. On Monday, October 24, 2022, 12:58:42 PM CDT, João E. Pereira Jr @.***> wrote:
Hello @migace001, Could you provide more details about the issue?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
@migace001,
Sorry, I could'nt find the screenshots. Check if the LDAP_ORGANISATION and LDAP_DOMAIN enrironment variables are properly set when starting the container via docker-composer. Inspect the containers and compare the outputs.
Here is what i a reffering to
@migace001,
I see. As far as I know using organization as the sctructural attribute in this scenario is the right behaviour. openldap also defines domain objectClasses to be used in other scenarios like DNS or email. In your case the domain is test.test1, but presented in 2 domain components dc=test,dc=test1. I think you shold proceed this way and things will work as expected.
Trying to figure out why my dc=test,dc=test1 when i click on it says its a organization not a domain. Driving me nuts the openldap docker seems easy but it seem to get around it.