Skip to content
This repository has been archived by the owner on Sep 18, 2021. It is now read-only.

Refresh Tokens #3903

Open
paulwroe opened this issue Nov 21, 2017 · 0 comments
Open

Refresh Tokens #3903

paulwroe opened this issue Nov 21, 2017 · 0 comments

Comments

@paulwroe
Copy link

A customer of ours is experiencing issues with refresh tokens.

We're trying to currently ascertain where the issue lies.

Are the below statements true?

This looks like the refresh token was successfully used

2017-11-08 19:18:06.760 +00:00 [Information] 2021: "Refresh token refresh success" / "TokenService" (Success), Context: EventContext { ActivityId: "00000000-0000-0000-d807-0080000000d2", TimeStamp: 11/08/2017 19:18:06 +00:00, ProcessId: 19372, MachineName: "RD0003FF72A511", RemoteIpAddress: "52.30.00.100", SubjectId: null }, Details: RefreshTokenRefreshDetails { ClientId: "acme_authcode", OldHandle: "75688e4170ee3ce23db1867fd127dd74", NewHandle: "75688e4170ee3ce23db1867fd127dd74", Lifetime: 2592000 }

This looks like the refresh token was re-used

2017-11-09 04:53:53.480 +00:00 [Information] 2022: "Refresh token refresh failure" / "TokenService" (Failure), Context: EventContext { ActivityId: "00000000-0000-0000-780e-0080000000ef", TimeStamp: 11/09/2017 04:53:53 +00:00, ProcessId: 19372, MachineName: "RD0003FF72A511", RemoteIpAddress: "52.30.00.100", SubjectId: null }, Details: RefreshTokenDetails { HandleId: "75688e4170ee3ce23db1867fd127dd74", Version: 0, SubjectId: null, ClientId: "acme_authcode", Scopes: null, Lifetime: 0, Claims: null }

Thanks for your help

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant