Hi Ritesh,
First of all, stop your Rundeck service to start to add some files and edit the configuration. So, the first step is to create the jaas-ldap.conf file on /etc/rundeck path with your LDAP configuration information (here you can check a good example). I have this one for testing:
ldap {
com.dtolabs.rundeck.jetty.jaas.JettyCachingLdapLoginModule required
debug="true"
contextFactory="com.sun.jndi.ldap.LdapCtxFactory"
providerUrl="ldap://your-ldap-host:389"
bindDn="cn=admin,dc=example,dc=net"
bindPassword="admin"
authenticationMethod="simple"
forceBindingLogin="false"
userBaseDn="ou=Users,dc=example,dc=net"
userRdnAttribute="uid"
userIdAttribute="uid"
userPasswordAttribute="userPassword"
userObjectClass="posixAccount"
roleBaseDn="cn=Roles,dc=example,dc=net"
roleNameAttribute="cn"
roleUsernameMemberAttribute="memberUid"
roleMemberAttribute="memberUid"
roleObjectClass="posixGroup"
cacheDurationMillis="300000"
supplementalRoles="user"
reportStatistics="true"
timeoutRead="10000"
timeoutConnect="20000"
nestedGroups="false";
};
Keep in mind that the attributes must match with your LDAP server (for example, the providerUrl, bindDn, bindPassword, userBaseDn, userPasswordAttribute, and roleBaseDn attributes ). Also, make sure that the file is readable by rundeck user.
Now, it’s important to tell to Rundeck about your new LDAP configuration, for that, you need to create or edit the rundeckd file located at /etc/sysconfig path on RedHat/CentOS based distros or /etc/defaults on Debian/Ubuntu based distros (on some web guides you can see that some users edit the /etc/rundeck/profile file, that’s a bad practice because can generate problems at the moment of upgrade your Rundeck instance in the future, so, do no edit the /etc/rundeck/profile file). I have this one:
RDECK_JVM_OPTS="-Drundeck.jaaslogin=true \
-Djava.security.auth.login.config=/etc/rundeck/jaas-ldap.conf \
-Dloginmodule.name=ldap"
Now you can start the Rundeck service and if all is well configured, you can log in with users defined at userBaseDn. So, now you need to focus to create a basic ACL rule for your new users and roles to give access to your projects and jobs, please take a look at this and this ACL example.
If you like to test in a safe environment you can use the Osixia docker image and Apache Directory Studio to access and populate it. Anyway, here you can check the same process for Active Directory, and here an amazing docker example to see how works.
Hope it helps!
--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/dc1beb11-594f-4cc5-aa1a-99681bb5c0fan%40googlegroups.com.
Hi Ritesh,
Make sure that you’re pointing bindDn and userBaseDn attributes well, probably you’re set reversed (same issue). You can use Apache Directory Studio tool to browse and check your LDAP server.
Hope it helps!
Contact your administrator. (User roles: )
I need to get the roles read from file which is configured in rundeck instead of AD provide roles as well.
can you please help me to get the same configured.
Thanks,
Ritesh Garg
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/1113424c-0c6b-4ee0-994f-01404c3739dbn%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "rundeck-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rundeck-discuss/tSOw6cBmexM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/e5fc7596-92f3-440f-ad97-6bb723372995n%40googlegroups.com.
Hi Ritesh,
About LDAP configuration, Rundeck takes the roles from roleBaseDn attribute (make sure that is well pointed to your LDAP tree, in your case, just change the groups on your ACL definition accordingly with your LDAP roleBaseDn). About ACLs, you can define your rules against individual users (username: myusername at the end of the ACL definition) and roles (group: mygroup at the end of the ACL definition). Take a look at this.
Regards!