http://bugzilla.opensuse.org/show_bug.cgi?id=1096303 http://bugzilla.opensuse.org/show_bug.cgi?id=1096303#c1 Hans de Raad changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #1 from Hans de Raad --- (In reply to Wolfgang Rosenauer from comment #0) Actually from this logfile I guess the dirsrv instance is actually created yet there is an issue when accessing it due to a missing/wrong password: 2018-06-06 18:23:48 +0200 pk12util: PKCS12 decode not verified: SEC_ERROR_BAD_PASSWORD: The security password entered is incorrect. \npk12util: PKCS12 decode validate bags failed: SEC_ERROR_INVALID_ARGS: security library: invalid arguments. I have also encountered the issue of (apparently) not having a valid pcks12 cert entered in the Yast config wizard on creation of the dirsrv. It would be very helpful if some cert sanity check was performed on accepting the form values to prevent such a situation. Currently the code only seems to check for the prevention of empty values. Perhaps it would be advisable to add more in-depth validation logic to the ldap server module wizard? Like the validation of a PKCS12 cert (and password/etc)? A command like "openssl pkcs12 -info -in certname.p12" which output (password requests/confirmations) would need to be handled by the wizard more transparently than only referring to a logfile would imho improve the UX considerably. I have changed the status to Confirmed for the reason that the report outlines a valid issue with the current Leap 15 LDAP setup validation process that leaves the user/admin with a disfunctional setup. If that is not supposed to be done this way, please change the status appropriately. As an avid user of the Yast LDAP server/client functionality (which usually works just great, thanks to you geekos!) I am very interested in seeing this component mature as soon as resource-wise possible. -- You are receiving this mail because: You are on the CC list for the bug.