Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 1.0.0.Alpha6
Affects Version/s: 1.0.0.Alpha4
Component/s: _am_uncertain
Labels:
None

Steps to Reproduce:
1. Login to hawkular
2. Go to App Server Deployments tab
3. (Re)Deploy a WAR
4. Wait 5 minutes (until token refreshes)
5. (Re)Deploy a WAR .. this one fails
Workaround Description:

Hide

Extend the Access Token Lifespan (at http://localhost:8080/auth/admin/master/console/#/realms/hawkular/token-settings) to a greater value so the impact isn't so big

Show
Extend the Access Token Lifespan (at http://localhost:8080/auth/admin/master/console/#/realms/hawkular/token-settings ) to a greater value so the impact isn't so big
Git Pull Request:
https://github.com/hawkular/hawkular/pull/495, https://github.com/hawtio/hawtio-oauth/pull/13

Description

Keycloak by default has a 5 minute Access Token Lifespan, meaning every 5 minutes the token must be refreshed, invalidating the previous access token.

When this is happening the Hawkular Accounts is not updating $rootScope.userDetails.token value with the new token, so WS operations making use of it fail with "Invalid Token".

Attachments

Activity

People

Assignee:: Juraci Paixão Kröhling (Inactive)

Reporter:: Alexandre Mendonça (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2015/09/23 11:02 AM

Updated:: 2017/01/19 5:01 AM

Resolved:: 2016/01/19 11:44 AM