-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[management] Delete scope approval #1851
Closed
zdenda-online opened this issue
Jan 25, 2019
· 0 comments
· Fixed by gravitee-io/gravitee-access-management#549 or gravitee-io/gravitee-docs#143
Closed
[management] Delete scope approval #1851
zdenda-online opened this issue
Jan 25, 2019
· 0 comments
· Fixed by gravitee-io/gravitee-access-management#549 or gravitee-io/gravitee-docs#143
Comments
brasseld
changed the title
[am-management] Delete scope approval
[management] Delete scope approval
Feb 6, 2019
tcompiegne
added a commit
to gravitee-io/gravitee-docs
that referenced
this issue
Mar 26, 2019
tcompiegne
added a commit
to gravitee-io/gravitee-docs
that referenced
this issue
Mar 26, 2019
tcompiegne
added a commit
to gravitee-io/gravitee-access-management
that referenced
this issue
Mar 27, 2019
tcompiegne
added a commit
to gravitee-io/gravitee-docs
that referenced
this issue
Mar 28, 2019
brasseld
pushed a commit
to gravitee-io/gravitee-access-management
that referenced
this issue
Mar 28, 2019
brasseld
pushed a commit
to gravitee-io/gravitee-docs
that referenced
this issue
Mar 28, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to revert scope approval (consent), I gave to a 3rd-party application
as an end user
I need to have the possibility to delete such approval (at least on API level)
Detailed Context
We want to use Gravitee.io AM for PSD2 context (open banking) and in (national) standards require that bank must allow deletion of scope approval (consent). E.g. when bank end user approves that 3rd-party application can access his bank account, he must be able to take this decision back.
Possible Solution
Implement scope deletion. Minimum is on API level (so some custom bank application can call it from its front-end) or better with UI with auth.
The text was updated successfully, but these errors were encountered: