Cannot login as regular user

[bergtwvd]

I set up ElasticKube with a mail server.

When I add a new user the mail is sent out and received by the user.
The user clicks the provided link in the email and a validation page is provided.
So far so good.

After entering the requested data, and pressing the Validate button, an error appears in the browser:

e is undefined dismiss

The user cannot log in. -- Not good.

After clearing the browser cache and re-entering the direct link to the elastickube site, the user is prompted for username/password.
Again, after entering the data, the following errors appear in the browser window (FF 45.4.0):

e is undefined dismiss

The user cannot log in. -- Not good.

Same result in other browsers by the way (IE, GC).

When I login as the admin I see that the user is correctly registered (no pending status anymore).

When I look in the container api server log, I do not see anything odd (I changed the user's email address to EMAILADDRESS):

2017-01-29 23:38:18,142 Stopping watch for collection Users
2017-01-29 23:38:18,142 Removing callback from elastickube.Users namespace.
2017-01-29 23:38:18,143 Stopping watch for message {u'action': u'instances', u'body': {u'namespace': u'default'}, u'operation': u'watch', u'correlation': u'4'}
2017-01-29 23:38:18,143 AsyncHTTPClient closed
2017-01-29 23:38:18,144 AsyncHTTPClient closed
2017-01-29 23:38:18,144 AsyncHTTPClient closed
2017-01-29 23:38:18,145 AsyncHTTPClient closed
2017-01-29 23:38:18,145 AsyncHTTPClient closed
2017-01-29 23:38:18,146 AsyncHTTPClient closed
2017-01-29 23:38:18,240 Stopping watch for collection Settings
2017-01-29 23:38:18,240 Removing callback from elastickube.Settings namespace.
2017-01-29 23:38:18,262 Closing MainWebSocketHandler
2017-01-29 23:38:18,285 304 GET /api/v1/auth/providers (0.0.0.0) 2.17ms
2017-01-29 23:38:27,741 Initiating PasswordHandler post
2017-01-29 23:38:28,147 Authenticating user 'EMAILADDRESS'
2017-01-29 23:38:28,244 User 'EMAILADDRESS' authenticated.
2017-01-29 23:38:28,245 200 POST /api/v1/auth/login (0.0.0.0) 504.12ms
2017-01-29 23:38:28,281 Initializing MainWebSocketHandler
2017-01-29 23:38:28,298 Initializing LogsActions
2017-01-29 23:38:28,298 Initializing InstancesActions
2017-01-29 23:38:28,298 Initializing NamespacesActions
2017-01-29 23:38:28,298 Initializing SettingsActions
2017-01-29 23:38:28,298 Initializing UsersActions
2017-01-29 23:38:28,298 Initializing InviteActions
2017-01-29 23:38:28,299 Initializing CursorWatcher
2017-01-29 23:38:28,299 check_permissions for user EMAILADDRESS and operation watch on db watch
2017-01-29 23:38:28,299 Starting watch for collection Charts
2017-01-29 23:38:28,447 Adding elastikube.Charts callback
2017-01-29 23:38:28,541 Initializing CursorWatcher
2017-01-29 23:38:28,541 check_permissions for user EMAILADDRESS and operation watch on db watch
2017-01-29 23:38:28,541 Starting watch for collection Namespaces
2017-01-29 23:38:28,542 Adding elastikube.Namespaces callback
2017-01-29 23:38:28,558 Initializing CursorWatcher
2017-01-29 23:38:28,558 check_permissions for user EMAILADDRESS and operation watch on db watch
2017-01-29 23:38:28,558 Starting watch for collection Users
2017-01-29 23:38:28,559 Adding elastikube.Users callback

[napat1412]

I have same problem too. when i login with user-role: user, i got logs

2017-04-28 03:24:24,218 200 POST /api/v1/auth/login (0.0.0.0) 380.58ms
2017-04-28 03:24:24,314 Initializing MainWebSocketHandler
2017-04-28 03:24:24,323 Initializing LogsActions
2017-04-28 03:24:24,323 Initializing InstancesActions
2017-04-28 03:24:24,323 Initializing NamespacesActions
2017-04-28 03:24:24,323 Initializing SettingsActions
2017-04-28 03:24:24,323 Initializing UsersActions
2017-04-28 03:24:24,323 Initializing InviteActions
2017-04-28 03:24:24,324 Initializing CursorWatcher
2017-04-28 03:24:24,324 check_permissions for user [email protected] and operation watch on db watch
2017-04-28 03:24:24,324 Starting watch for collection Charts
2017-04-28 03:24:24,422 Adding elastikube.Charts callback
2017-04-28 03:24:24,515 Initializing CursorWatcher
2017-04-28 03:24:24,515 check_permissions for user [email protected] and operation watch on db watch
2017-04-28 03:24:24,515 Starting watch for collection Namespaces
2017-04-28 03:24:24,516 Adding elastikube.Namespaces callback
2017-04-28 03:24:24,524 Initializing CursorWatcher
2017-04-28 03:24:24,524 check_permissions for user [email protected] and operation watch on db watch
2017-04-28 03:24:24,524 Starting watch for collection Users
2017-04-28 03:24:24,525 Adding elastikube.Users callback

but when i login with user-role:administrator. ElasticKube can initial KubeWatcher and login to the system successfully.

2017-04-28 03:13:06,343 check_permissions for user [email protected] and operation watch on db watch
2017-04-28 03:13:06,343 Starting watch for collection Charts
2017-04-28 03:13:06,518 Adding elastikube.Charts callback
2017-04-28 03:13:06,532 Initializing CursorWatcher
2017-04-28 03:13:06,532 check_permissions for user [email protected] and operation watch on db watch
2017-04-28 03:13:06,532 Starting watch for collection Namespaces
2017-04-28 03:13:06,613 Adding elastikube.Namespaces callback
2017-04-28 03:13:06,616 Initializing CursorWatcher
2017-04-28 03:13:06,617 check_permissions for user [email protected] and operation watch on db watch
2017-04-28 03:13:06,617 Starting watch for collection Users
2017-04-28 03:13:06,619 Adding elastikube.Users callback
2017-04-28 03:13:06,623 Initializing KubeWatcher
2017-04-28 03:13:06,623 check_permissions for user [email protected] and operation watch on kube watch
2017-04-28 03:13:06,624 Starting watch KubeWatcher for message {u'action': u'instances', u'body':
{u'namespace': u'default'}, u'operation': u'watch', u'correlation': u'5'}
2017-04-28 03:13:07,119 Starting watch

How to fix it?

My system

• ElasticKube v0.1.0.199
• Kubernetes v1.5.4
• Coreos 1353.7.0

[ridnarong]

please check this PR #137