[opensuse-autoinstall] ldap-configuration using ldap
Hi,
I'm currently testing ldap-client configuration using autoyast.
Here is a list of issues I found. Please comment.
I'll probably file some bug reports next week. Testing system is
factory snapshot from April 12, 2012 (that is, M3, probably).
- (YaST) Issues during installation:
- Both the reference profile and the XML schema allow the parameter
V Fri, 11 May 2012 10:39:48 +0200
Robert Klein
Hi,
I'm currently testing ldap-client configuration using autoyast.
Here is a list of issues I found. Please comment.
I'll probably file some bug reports next week. Testing system is factory snapshot from April 12, 2012 (that is, M3, probably).
- (YaST) Issues during installation: - Both the reference profile and the XML schema allow the parameter
, but there's no binddn in /etc/ldap after installation.
It's saved to /etc/sysconfig/ldap
- missing support for additional LDAP configuration parameters, for example there ought to be a parameter
resulting in a bindpw in /etc/ldap.conf after installation. Also, I could use a way wo put the tls certfile into the autoyast xml, e.g. using a parameter <source><![CDATA[...]]>
Hm, let's solve the certificate in your (coming) bug report.
- Yast Reference Profile (created using Yast -> Autoyast -> Tools -> Create Reference Profile) issues: - A created reference profile has a parameter <mkhomedir>, but it isn't allowed according to the XML schema (/usr/share/YaST2/schema/autoyast/rng/ldap.rng) and apparently isn't used, i.e. it didn't appear in /etc/ldap.conf after installation (I only had it set to "false", though).
You are right about schema bug here (I'll fix it). But mkhomedir does not go to /etc/ldap, it causes 'pam-config -a --mkhomedir' run.
- schema only issues: - The parameters <sssd>,
and aren't in the XML schema (/usr/share/YaST2/schema/autoyast/rng/ldap.rng) They are, however reference profiles created with Yast -> AutoYast and are used during installation
OK, I'll fix it. Jiri -- Jiri Suchomel SUSE LINUX, s.r.o. Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
Hi I try to configure vsftpd on a SLES11 SP1 system via an XML file but ... neither the GUI nor the CLI give me an option to select the vsftpd as the preferred FTP server. In the GUI ( Autoinstallation - networkservices - ftp server ) the option for the vsftp is greyed out. Also the way to configure the system for vsftpd usage and then get the XML file via "yast clone_system " gives no vsftpd config. Is this a bug or a feature ? Tia Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
On 11.06.2012 18:38, Hans-Joachim Ehlers wrote:
I try to configure vsftpd on a SLES11 SP1 system via an XML file but ... neither the GUI nor the CLI give me an option to select the vsftpd as the preferred FTP server. In the GUI ( Autoinstallation - networkservices - ftp server ) the option for the vsftp is greyed out. Also the way to configure the system for vsftpd usage and then get the XML file via "yast clone_system " gives no vsftpd config.
Is this a bug or a feature ?
hm, I was able to reproduce that. On the first sight it looks like a bug in yast2-ftp-server but I'm not 100% sure because when I looked at the code it was okay and might be a problem in the yast2 package bindings. Can you open a bugreport for it? -- ciao, Uwe Gansert SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer Home: http://www.suse.de/~ug - Blog: http://suse.gansert.net listening to: "Atlas" by Covenant -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
participants (4)
-
Hans-Joachim Ehlers -
Jiří Suchomel -
Robert Klein -
Uwe Gansert