Skip to content
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

Modifying permissions will list incorrect scopes for the permission after consent #2241

Closed
musale opened this issue Nov 17, 2022 · 1 comment · Fixed by #2246
Closed

Modifying permissions will list incorrect scopes for the permission after consent #2241

musale opened this issue Nov 17, 2022 · 1 comment · Fixed by #2246
Assignees
Milestone

Comments

@musale
Copy link
Contributor

musale commented Nov 17, 2022

Describe the bug
Modifying permissions on the permissions list renders incorrect scopes below the permission after a reload.

To Reproduce
Steps to reproduce the behavior:

  1. Open the permissions list from the account menu and search for "presence". This will list 3 scopes you can consent to:
    image
  2. Consent on presence.Read. A pop up appears and vanishes. At this point I assume that the permission is consented to because I get this success alert:
    image
  3. The bug is the list of scopes under "Presence" are not presence scopes but "APIConnectors" and "AccessReview" scopes:
    image

Expected behavior
The permissions list for presence are correct after consenting to a scope.

Desktop (please complete the following information):

  • OS: Windows 11
  • Browser: Edge v107.0.1418.42

Additional context
The same thing happens when you search and consent to other permissions like "booking".

@ghost ghost added the ToTriage label Nov 17, 2022
@Onokaev Onokaev self-assigned this Nov 18, 2022
@ghost ghost removed the ToTriage label Nov 18, 2022
@Onokaev Onokaev added this to the November-2022 milestone Nov 18, 2022
@Onokaev
Copy link
Contributor

Onokaev commented Nov 18, 2022

Thanks for this @musale. We are working on it
We'll have a patch out soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants