Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Not sure, but should the bind as field not be a valid user dn instead of just the account name? If in doubt, look at the ldap logs, that's what they're there for.
Right, well does it exist??? you must have created it if it does, so only you will know. I do know that "cn=Manager,dc=domain,dc=local" is not EXACTLY the same as "cn=Manager,dc=voipcenter,dc=local" however... have you not actually configured openldap properly yet? It's not exactly fair to expect to use a tool to configure a server before that server has at least been configured a tiny bit, enough to be supported by said tool.
It's not exactly fair to expect to use a tool to configure a server before that server has at least been configured a tiny bit, enough to be supported by said tool.
Well, I thought I could create new OU's and users like in Active Directory with this Luma-GUI...
Well you can clearly appreciate that luma is connecting to ldap using ldap, therefore basics (which you've already shown us, so I don't understand why you'd not have configured them to your needs already..??) still need to be there. You only need a working manager account, nothing more, and that's nothing you wouldn't have done for an equivalent in AD, e.g. a domain admin account.
That is the account that Luma is expecting to be given to access the ldap server. They need to be the same, and correct for your deployment.
I'm sorry, I don't understand.
You tell me that I need a "domain admin". According to me that is : cn=Manager,dc=domain,dc=local
When using this information as login (and with the correct password) I get the message : Could not expand entry: No such object
(so login was successful, but I cannot do anything)
You tell me "You only need a working manager account, nothing more".
But apparently, I am still missing something, right ?
I'm totally lost as to what you do and don't have. Can you show the configs you actually have? Forget Luma for now. You need to be able to bind to ldap with the manager account, whatever it is called (and it's not REALLY still called "cn=Manager,dc=domain,dc=local" letter for letter is it?? please say no...)
this should work... "ldapsearch -x -h ip.of.ser.ver -D cn=manager,dc=whatevertherestis" where "work" means at least seeing a valid bind message in the ldap logs. get that working first.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.