Skip to content

Configuring authorized client applications doesn't work #52

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

Open
scale-tone opened this issue Feb 25, 2022 · 0 comments
Open

Configuring authorized client applications doesn't work #52

scale-tone opened this issue Feb 25, 2022 · 0 comments

Comments

@scale-tone
Copy link

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

#Configure Authorized client applications for service (TodoListService-OBO-sample-v2)
....
In the manifest editor, change the "knownClientApplications": [] line so that the array contains the Client ID of the client application (TodoListClient-OBO-sample-v2) as an element of the array.

This does not work. At least, not in my tenant. No matter whether client appId is added or is not added to knownClientApplications, the user is still presented with 'Need admin approval' page:

What does work is pre-authorizing that client application:

and pre-assigning the scope. Then the user doesn't get the consent dialog at all.

So (at least, in my tenant) it is either a mandatory admin consent or no consent.
Probably, this needs to be clarified in the readme.

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

No branches or pull requests

1 participant