Re: UAA restart invalidates a valid token

Filip Hanik

After the fix, having override: true should not revoke the tokens. If it
still does, then it's a bug and we would like to know. thanks

On Wed, Sep 9, 2015 at 8:37 AM, Kayode Odeyemi <dreyemi(a)> wrote:


option 2 is definitely the cause of the problem.

Thank you very much.

On Wed, Sep 9, 2015 at 4:32 PM, Filip Hanik <fhanik(a)> wrote:

We introduced a feature called 'revokable tokens'. A token would
automatically be revoked if a client changed it's secret. All tokens issued
previously would be automatically revoked.

In earlier versions of the UAA, if you have clients in your manifest, and
override flag set to true, even though the secret didn't change in the
manifest, the hashed secret was regenerated and thus this would expire all
the tokens.

you have a couple of different options
1. Update your UAA - this was fixed in
2. Set override to false for your boot strapped clients and users

On Wed, Sep 9, 2015 at 8:22 AM, Kayode Odeyemi <dreyemi(a)> wrote:


What could cause a valid token to become invalid on UAA restart?

I've noticed this overtime, that a token (of client_credentials grant
type) which has a validity of 315360000 and has been used for
authentication and authorization of users and resource servers, suddenly
returns invalid_token when validated after a UAA restart.

"error": "invalid_token",

Any ideas please?

Join { to automatically receive all group messages.