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 Apr 9, 2024. It is now read-only.
Maybe this belongs alongside User Management somehow and could be part of it??
Ability to augment tokens coming from multiple providers with additional claims that can be used during authorization.
A good example of this could be to have claims on every user saying which national society (Tenant) they have access to. This is not the Azure AD tenant ID - but something that enables us to check for authorisation if a particular user in a bounded context has access to the national society it claims to have.
Would it be an idea to have Identity Server infront of all this and augment the tokens with more information and let UserManagement interact with this and provide the mapping between users and what national societies they have access to.
einari
changed the title
Look into having Identity Server as our proxy for auth
Use Identity Server as authority and let it have support for multiple providers - augment tokens
Mar 22, 2018
Maybe this belongs alongside User Management somehow and could be part of it??
Ability to augment tokens coming from multiple providers with additional claims that can be used during authorization.
A good example of this could be to have claims on every user saying which national society (Tenant) they have access to. This is not the Azure AD tenant ID - but something that enables us to check for authorisation if a particular user in a bounded context has access to the national society it claims to have.
Would it be an idea to have Identity Server infront of all this and augment the tokens with more information and let UserManagement interact with this and provide the mapping between users and what national societies they have access to.
See also #31, #327, #328, #510
The text was updated successfully, but these errors were encountered: