You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 16, 2018. It is now read-only.
I am using a very similar flow to the one that is described in this issue over at the IS3 repo, IdentityServer/IdentityServer3#1363. In fact I am already using a lot of oidc-token-manager to obtain my tokens and stash them on the client. I have a token manager that lives in an angular directive that initiates the login over to IS3, from there the user logs in and sent back to a callback page where the tokens are checked and put into local storage.
However, much like the original poster in that issue describes. I would like to be able to extend the token when the user actually uses the token. So the flow would go something like this:
Users logs in, token is stored in local
Users hits an API with the token passed over to it. At this point the token expiration should be extended as they are clearly active. How should this be implemented via IS3 and my token manager?
The text was updated successfully, but these errors were encountered:
I am using a very similar flow to the one that is described in this issue over at the IS3 repo, IdentityServer/IdentityServer3#1363. In fact I am already using a lot of oidc-token-manager to obtain my tokens and stash them on the client. I have a token manager that lives in an angular directive that initiates the login over to IS3, from there the user logs in and sent back to a callback page where the tokens are checked and put into local storage.
However, much like the original poster in that issue describes. I would like to be able to extend the token when the user actually uses the token. So the flow would go something like this:
The text was updated successfully, but these errors were encountered: