"User couldn't be authenticated" error in sunstone interface

Community Support
1

Good morning,

I have a problem related with the authentication when using sunstone interface. I enter with oneadmin user, and sometimes I get a [ImagePoolInfo] (or other info pools) “User couldn’t be authenticated” error.

I normally have to wait a bit until I can refresh the contents of the page but it’s unconfortable for a user to have to wait until he can continue using the interface. May it be a synchronization problem with databases in the zones?

Thanks a lot for your help

Best regards

2

Hi,

That’s strange. You mentioned you use different zones, is it happening in any opennebula, or only in slave zones?
What user authentication driver are you using?
When that message is returned, do you see any other info in the sunstone or oned log files?

3

Hi, thank you very much and sorry for the late response.

It is independent of the user. I normally use oneadmin, but it happens with normal users from “user” group.

This is the content of oned.log:

Thu Oct 15 20:46:06 2015 [AuM][E]: Auth Error: login token expired
Thu Oct 15 20:46:06 2015 [ReM][D]: Req:1728 UID:- TemplatePoolInfo invoked, -2, -1, -1
Thu Oct 15 20:46:06 2015 [ReM][E]: Req:1728 UID:- TemplatePoolInfo result FAILURE [TemplatePoolInfo] User couldn’t be authenticated, aborting call.
Thu Oct 15 20:46:06 2015 [AuM][D]: Message received: LOG I 3106 Command execution fail: /var/lib/one/remotes/auth/server_cipher/authenticate serveradmin 0699316f18e9bd4ec74fe56fb6e23144b6ddd3f7 ****

Thu Oct 15 20:46:06 2015 [AuM][I]: Command execution fail: /var/lib/one/remotes/auth/server_cipher/authenticate serveradmin 0699316f18e9bd4ec74fe56fb6e23144b6ddd3f7 ****
Thu Oct 15 20:46:06 2015 [AuM][D]: Message received: LOG E 3106 login token expired

Thu Oct 15 20:46:06 2015 [AuM][I]: login token expired
Thu Oct 15 20:46:06 2015 [AuM][D]: Message received: LOG I 3106 ExitCode: 255

Thu Oct 15 20:46:06 2015 [AuM][I]: ExitCode: 255
Thu Oct 15 20:46:06 2015 [AuM][D]: Message received: AUTHENTICATE FAILURE 3106 login token expired

Thank you very much for your help.

Best regards

4

Hi,

Tokens are generated using the following constants in CloudAuth.rb:

If the expiration time of the token is lower than 300 a new one will be generated, so there should not be an expired token with this configuration. You can try to modify this value to generate tokens earlier.

Hope this helps

5

Sorry, but I don’t find the file where I have to change that configuration. I’m using OpenNebula 4,6.

Thank you very much.

Best regards