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 Dec 14, 2017. It is now read-only.
Sorry if this has been asked before - is it possible to validate tokens from IdentityServer 3 and unpack to a new ClaimsIdentity rather than a middleware that sets the current identity?
I want to use IdentityServer for a 'signing' process, so still use OpenID Connect to secure the tokens but use them for a different use case, i.e. the user has 'signed' a process. The reason we don't want to update the claims, or elevate the user for this signing is because it's only a one off process - they must re-authenticate the next time they wish to perform this process.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sorry if this has been asked before - is it possible to validate tokens from IdentityServer 3 and unpack to a new ClaimsIdentity rather than a middleware that sets the current identity?
I want to use IdentityServer for a 'signing' process, so still use OpenID Connect to secure the tokens but use them for a different use case, i.e. the user has 'signed' a process. The reason we don't want to update the claims, or elevate the user for this signing is because it's only a one off process - they must re-authenticate the next time they wish to perform this process.
The text was updated successfully, but these errors were encountered: