Repository navigation
Adding 3-legged support to existing endpoints - #193
Draft
hubertp-ericsson wants to merge 4 commits into
Draft
hubertp-ericsson wants to merge 4 commits into
hubertp-ericsson wants to merge 4 commits into
Conversation
…ng-3-legged-support-to-existing-enpoints
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
What this PR does / why we need it:
There is an ongoing discussion in issue #180 on how to support B2B2C where it is proposed to enable support for 3-legged access token for the access operations which target devices and currently support only 2-legged access tokens. This PR shows how that proposal can be realized in the Access API. It includes also the discussed call flows as a supporting document.
Which issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
This is a draft proposal for discussion in the team.
Changelog input
Additional documentation
This section can be blank.