@brockallen The oidcclient.js .. it is limited by the cookie on the OP, right? So, if we use the default (30 days?) the user would have to login eventually after 30 days, even with silent renewal ?
(i mean, in the sense that we need access_tokens to use our app at all as a user)
Hi folks. Does anybody else getting "invalid signature" error on jwt.io when pasting tokens? Or it's just me :worried:
All is working as expected, using a custom self-signed certificate to sign tokens by the way. But jwt.io says token signature is not ok :(
You releived me, my friend. Thanks :)
just checked
I think I might need a little hint on how one would get started with the Admin UI, the relation between Admin, Admin.EntityFramework and Admin.Client for instance. I get that Admin.Client is using Admin, but where does Admin.EntityFramework fit in? And where to start?
Ignore my previous shout for now. Apparently there was some trouble updating packages. All is now well.
I belive we've come across the Heisenbug re Cookies for the 2nd time now. When refreshing the access token and signing in a new ClaimsIdentity using the OWIN Authentication, it stops adding new refresh tokens to the Identity after the 2nd or 3rd call to SignIn. Hence, the following request to refresh fails, as we have an old refresh token stored in our local cookie. Niiiiice
it's Kentor time
The localization is covered in the documentation. But I cannot figure out how to add and register my own resource files (other then changing resx files on the source and recompile it)
Does anyone have knowledge on how to work with embedded resource filles?
Also, do you know when the Thinktecture.IdentityServer3.Admin project is going to be published?
It will take a couple of weeks for the admin to finish.