Bug #2608
Missing step to use LDAP as default driver
Status: | Closed | Start date: | 01/09/2014 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | Javi Fontan | % Done: | 0% | |
Category: | Documentation | |||
Target version: | Release 4.4.1 | |||
Resolution: | fixed | Pull request: | ||
Affected Versions: | OpenNebula 4.4 |
Description
From 4.4 documentation :
To be able to use this driver for users that are still not in the user database you must set it to the default driver. To do this go to the auth drivers directory and copy the directory ldap to default. In system-wide installations you can do this using this command:
$ cp -R /var/lib/one/remotes/auth/ldap /var/lib/one/remotes/auth/default
To make it working, we must add default
in AUTH_MAD
like in the following:
--- oned.conf.orig 2014-01-09 16:09:36.887288127 +0100
+++ oned.conf 2014-01-09 16:10:47.793759142 +0100
@@ -532,7 +532,7 @@
AUTH_MAD = [
executable = "one_auth_mad",
- authn = "ssh,x509,ldap,server_cipher,server_x509"
+ authn = "default,ssh,x509,ldap,server_cipher,server_x509"
]
SESSION_EXPIRATION_TIME = 900
The same applies to 4.2.
Regards.
History
#1 Updated by EOLE Team over 7 years ago
Note that I think it could be better to make a symbolic link as it stands that default
is LDAP
:
$ ln -s /var/lib/one/remotes/auth/ldap /var/lib/one/remotes/auth/default
#2 Updated by Ruben S. Montero over 7 years ago
- Status changed from Pending to New
- Target version set to Release 4.4.1
THANKS for your feedback!!!
#3 Updated by Ruben S. Montero over 7 years ago
- Assignee set to Javi Fontan
#4 Updated by Javi Fontan over 7 years ago
- Status changed from New to Closed
- Resolution set to fixed
The documentation in the repository is changed for both master and 4.4 versions:
- https://github.com/OpenNebula/docs/commit/2f9cc60e3df7746f0654aef0e065cf346f4f39b9
- https://github.com/OpenNebula/docs/commit/27b794f799bfa691787d191afa0d75e82afa11fd
In the next documentation build this change will go to the web page.
We used ln -s in previous versions of the documentation but this created some problems with the remote copy of scripts to nodes. To stay safe we suggest to copy the directory.