Revision d44cbf26
Added by François ARMAND almost 7 years ago
| 30_basic_administration/80_user_management.txt | ||
|---|---|---|
|
==== Configuring an LDAP authentication provider for Rudder
|
||
|
|
||
|
If you are operating on a corporate network or want to have your users in a
|
||
|
centralized database, you can enable LDAP authentication for Rudder users.
|
||
|
centralized database, you can enable LDAP authentication for Rudder users.
|
||
|
|
||
|
===== LDAP is only for authentication
|
||
|
|
||
| ... | ... | |
|
credential provided by the user.
|
||
|
|
||
|
|
||
|
So next, you have to set-up the connection parameters to the LDAP directory to use.
|
||
|
So next, you have to set-up the connection parameters to the LDAP directory to use.
|
||
|
There are five properties to change:
|
||
|
|
||
|
- rudder.auth.ldap.connection.url
|
||
| ... | ... | |
|
You can also build custom roles with whatever permission you want, using a type
|
||
|
and a level as specified below.
|
||
|
|
||
|
image::./..//images/workflow_roles.png[Roles can match different types of users]
|
||
|
image::./images/workflow_roles.png[Roles can match different types of users]
|
||
|
|
||
|
In the xml file, the role attribute is a list of permissions/roles, separated by
|
||
|
a comma. Each one adds permissions to the user. If one is wrong, or not correctly
|
||
Also available in: Unified diff
Fixes #10700: Documentation build broken