Difference between revisions of "LDAP"
Jump to navigation
Jump to search
Infrastation (talk | contribs) m (placeholder) |
Infrastation (talk | contribs) (preface) |
||
| Line 1: | Line 1: | ||
== LDAP configuration and troubleshooting == | == LDAP configuration and troubleshooting == | ||
| + | There are different ways to make RackTables recognize LDAP accounts instead of local accounts. One way is to configure RackTables to communicate with an LDAP server '''directly'''. In this case both password validity and group membership information are available inside RackTables. Group membership can be used in permission rules to implement site's access control policy. Another way is to configure RackTables to '''trust''' the authentication performed by httpd, which in turn is configured to authenticate HTTP(S) clients. This is sometimes the case, when the system administrator wants to reuse a working httpd+mod_auth_ldap setup. The drawback of this method is that group membership information wouldn't be available in RackTables. | ||
| + | |||
| + | === direct access to LDAP === | ||
| + | |||
| + | === trusting httpd === | ||
Revision as of 12:47, 9 June 2011
LDAP configuration and troubleshooting
There are different ways to make RackTables recognize LDAP accounts instead of local accounts. One way is to configure RackTables to communicate with an LDAP server directly. In this case both password validity and group membership information are available inside RackTables. Group membership can be used in permission rules to implement site's access control policy. Another way is to configure RackTables to trust the authentication performed by httpd, which in turn is configured to authenticate HTTP(S) clients. This is sometimes the case, when the system administrator wants to reuse a working httpd+mod_auth_ldap setup. The drawback of this method is that group membership information wouldn't be available in RackTables.
