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

Change client default scope loading #103

Closed
jjg-123 opened this issue Jun 9, 2023 · 0 comments
Closed

Change client default scope loading #103

jjg-123 opened this issue Jun 9, 2023 · 0 comments

Comments

@jjg-123
Copy link
Contributor

jjg-123 commented Jun 9, 2023

Currently the default is to load every scope for a client, then remove what is explicitly denied. This was done originally to make deploying the client (intended as a very simple sample) a snap. Evolution has made the client central to any number of operations such as proxying and this is now counter-intuitive and annoying.

The expected behavior is that only listing a scope explicitly adds it to the client's request list. Optionally it may be disabled (mostly so you don't have to go to the trouble of removing it from the configuration for, say, debugging purposes).

@jjg-123 jjg-123 closed this as completed Jul 10, 2023
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