auth_token does not updated when endpoint is updated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
keystonemiddleware |
Fix Released
|
Undecided
|
Yang Youseok |
Bug Description
nova-api using auth_token middleware does not find identity server when identity endpoint is not created yet emitting EndpointNotfound Exception. It's working normally since there is no proper endpoint in auth_token.
The problem is even after user create proper identity endpoint used by nova-api, auth_token does not re-authenticate til expiration time is reached. Operator can restart nova-api and re-initialize token auth though, I think it should be working without restart.
It does not related to caching in auth_token, since every different token also failed after identity endpoint created. It results from adapter in _identity_server does not be updated using original auth (original catalog which does not have identity endpoint yet).
So I think it's better to have any ways to be notified when endpoint updated in auth_token.
Thanks.
Changed in keystonemiddleware: | |
assignee: | nobody → Yang Youseok (ileixe) |
status: | New → In Progress |
Could you include the traceback that you are seeing when this happens?