|
Bugzilla – Full Text Bug Listing |
| Summary: | No YaST2 Module create the LDAP (SUSE) default ou=ldapconfig | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Forgotten User QtBI7gWTIh <forgotten_QtBI7gWTIh> |
| Component: | YaST2 | Assignee: | Jiří Suchomel <jsuchome> |
| Status: | RESOLVED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | varkoly |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | My YaST2 Logs | ||
|
Description
Forgotten User QtBI7gWTIh
2008-08-29 07:26:29 UTC
Created attachment 236141 [details]
My YaST2 Logs
Hm, strange, for me it works. Does it behave correctly when you 1. create LDAP server, 2. use "Create the default objects" in ldap-client and 3. check mail-server module? E.i. do not run mail-server before creating the default objects. Please attach also the output of ldapsearch -x, and /etc/ldap.conf file I have found a way to create this ou=ldapconfig ? I have edit /etc/sysconfig/ldap old BASE_CONFIG_DN="dc=xxx,dc=xxxx" the ou=ldapconfig is missing ???? new BASE_CONFI_DN="ou=ldapconfig,dc=xxx,dc=xxx" then I start yast2 ldap-client and say, create default config afterward the "ou=ldapconfig" is correct created ? Now I have a working ldap ;) I send later the Logs, OK ? (In reply to comment #3 from Günther J. Niederwimmer) > I have found a way to create this ou=ldapconfig ? > > I have edit /etc/sysconfig/ldap > > old > > BASE_CONFIG_DN="dc=xxx,dc=xxxx" > > the ou=ldapconfig is missing ???? Well, than it is easy, isn't it? YaST Ldap Client creates the entry marked as BASE_CONFIG_DN. It doesn't check its value. > I send later the Logs, OK ? I don't think it is needed. I think the behavior is correct. ?? ;) Yes, YaST Ldap Client create this "normal" as default, but in SUSE 11.0 this feature is missing ? It doesn't check and doesn't create the correct BASE_CONFIG_DN. What do you mean is missing? BASE_CONFIG_DN is the value user has to enter in the specific text entry. YaST LDAP Client offers ou=ldapconfig<,base DN> only if BASE_CONFIG_DN is empty. In your case, it wasn't empty, so it wasn't replaced. I don't know why you had BASE_CONFIG_DN="dc=xxx,dc=xxxx" as BASE_CONFIG_DN. Try to reproduce whole situation again and watch when it occurs there. "Normal" (all YaST before 11.0) the YaST Ldap Client create the default, in advanced settings (Ldap Client), when the button create the default settings is switched ON ? With 11.0 the defaults are never created ? My Situation was a clean new installation, after install I start YaST2 Mailserver to config ldap usw. This is all in the YaST.log Normal the mailserver (ldap_client) config create the correct BASE_CONFIG_DN ? (In reply to comment #7 from Günther J. Niederwimmer) > "Normal" (all YaST before 11.0) the YaST Ldap Client create the default, in > advanced settings (Ldap Client), when the button create the default settings is > switched ON ? > > With 11.0 the defaults are never created ? > > My Situation was a clean new installation, after install I start YaST2 > Mailserver to config ldap usw. Than please try what I suggested in comment 2: Try to "Create Defaults" before running mail server configuration. And during the test, do what I suggested in comment 6: Try to reproduce whole situation again and watch when it (the value of BASE_CONFIG_DN) occurs there. |