John Korsnes
John Korsnes
Yep, this is still an issue with RTM, not only previews / RCs. Updated to title of this ticket to reflect it. The only 2 possible resolutions I've found: 1)...
I think adding a time aspect into that message, like "and do it NOW" would suffice. No need to involve MC Hammer ;)
Also using refresh tokens and 2.6.0, but not the mongodb package. Not having issues so far. This issue probably relates to: #3458
I see the mongodb implementation does not serialize the claimsprincipal. Could that be it? Maybe @jageall can chime in :)
@cypressious : can you test the new mongodb package, and see if that solves your issues?
How are you implementing `IRefreshTokenStore`? EF? Rolled your own? The MongoDB implementation was lacking the `Subject` for Refreshtokens - not sure if what you're seeing is related or not.
The default is in-memory, not backed by SQL.
Do you have something in that SerializerSettings for converting the `ClaimsPrincipal` as well ..? (the `.Subject` prop of `RefreshToken.cs`) Similar to: https://github.com/IdentityServer/IdentityServer3.EntityFramework/blob/master/Source/Core.EntityFramework/Stores/BaseTokenStore.cs#L67
No, the `Subject` property has been there for 2 years. Not sure why you haven't seen an issue with it before, but this commit from @brockallen I believe is the...
Is this the (currently) blank page that is shown after doing a redirect back to the RP after successful login? If so - hooray! :)