Linux – OpenNebula: [HostPoolInfo] User couldn’t be authenticated, aborting call

authenticationlinuxopennebula

I installed OpenNebula 3.2.1 following the guide found under http://opennebula.org/documentation:rel3.2:ignc on a Debian 6.0.4 machine. Everything seemed fine until trying to execute the command

onevm list

Then I always get this:

oneadmin@opennebula-master:~$ onevm list
[VirtualMachinePoolInfo] User couldn't be authenticated, aborting call.

The file one_auth exists. I even gave the oneadmin user a password although it doesn't seem to be required according to the guide. I copied the password hash from /etc/shadow to the one_auth file. Still no success.

Any ideas are appreciated.

Best Answer

Note that the answer from Peteris is a verbatim quote from the OpenNebula documentation which presumably is not clear enough...

Based on the question, 2 points seem to need clarification:

OpenNebula uses its own distinct authentication, NOT system auth, so the username and password in the file named in the $ONE_AUTH environment variable are ones set using OpenNebula itself.
The password field is not a hash, it is plaintext. For that reason it is important that you make sure the file has restrictive permissions, e.g. 600

Related Solutions

Linux – Opennebula Sunston user oneadmin password

In case of lost password you can use another user in oneadmin group to change the lost password:

    $ oneuser passwd --sha1 oneadmin 'newpassword'

Or change the password directly in the database:

Stop OpenNebula daemons (this is needed as some data is cached).
Connect to the database and get the body of oneadmin user:
```
select body from user_pool where name='oneadmin';
```
You will get an xml document with user data. The value you have to change is password. Make sure the password is hashed with sha1. You can do it with this command:
```
$ echo -n 'newpassword' | openssl sha1
```

Update the table with the edited xml:

update user_pool set body='<edited xml>' where name='oneadmin';

Now you can change your credentials and start OpenNebula again:

    $ echo "oneadmin:new_password" > ~/.one/one_auth
    $ one start

Ssh – Solaris pam_ldap Authentication Using sshd-kbdint and Failing

As it turns out, the issue is with the 'binding' control_type keyword used in the /etc/pam.conf and **/etc/pam.d/ *files.

By replacing all instances of 'binding' with 'sufficient' for the pam_unix_auth.so.1 lines in the files, authentication now works. As an example:

login   auth binding            pam_unix_auth.so.1 server_policy
login   auth required           pam_ldap.so.1 debug

should become

login   auth sufficient         pam_unix_auth.so.1 server_policy
login   auth required           pam_ldap.so.1 debug

Be sure to do this wherever you want to use LDAP authentication.

Best Answer

Related Solutions

Linux – Opennebula Sunston user oneadmin password

Ssh – Solaris pam_ldap Authentication Using sshd-kbdint and Failing

Related Topic