This repository was archived by the owner on Jun 23, 2023. It is now read-only.
Find scope #76
Merged
Find scope #76
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…he grant under which the new token is minted. This can happen during token exchange.
peppelinux
approved these changes
May 30, 2021
|
Does this PR close this issue I havent analyzed yet the dump |
|
Yes, exactly! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is about finding the scope for a token. The scope may be in the token, in a token in a hierarki of tokens used to mint the token in question or in the grant that is minting/have minted the token.
The idea is that you follow the path from the token through the set of based_on tokens to end up at the grant.
The first item that has a scope defined decides the outcome.