-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't use Yast2 Users Module to Add Users to 389-ds... #104
Comments
the 389ldap.txt was copied to /etc/openldap and ldap.conf ldap.txt is the default 389-ds configuration found in /etc folder as per 389-ds server config the 389ldap.txt was adjusted and then placed in /etc/openldap folder so yast2 users module would sort of work. what i mean here is that a dialogue actually brought up those settings i made in the openldap/ldap.conf file. i entered the password and then it stopped working. i have to exit out of ssh as it wouldn't come back with an error for ages. |
I don't think this module is what manages users in yast? Also that user and group admin is for local users no? Not ldap users? Regardless, we'd probably remove that feature from yast as the dsidm command is better suported within the 389-ds ecosystem. |
In the past, yast2-users was better integrated with LDAP and the related YaST modules. Since the rewrite of those authentication client/server modules that integration is lost. See a summary of the situation here: https://github.com/yast/yast-users/blob/master/doc/auth-modules.md |
Currently there isn't really much interest to expand yast to be a full ldap/iam/idm access management tool, as it's not really in the best place to provide this functionality. |
if i'm correct, yast-auth-client module allows yast users module to connect to 389-ds server and enable administrator to add ldap users.
right now it seems that the configuration is still set up the old way with openldap settings. please change this so that yast users module can make use of the 389-ds server
The text was updated successfully, but these errors were encountered: