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

OAuth2 realm config - updating 'scopes supported' requires a restart #790

Closed
lscorcia opened this issue Sep 17, 2024 · 1 comment
Closed
Assignees

Comments

@lscorcia
Copy link
Contributor

Describe the bug
Hi, very small issue here. When editing the "scopes supported" field in the OAuth2 realm config, a server restart is required to make sure the scopes are updated in the metadata endpoint. It should be possible to update those at runtime.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Services > OAuth2 Provider
  2. Click on Supported Scopes, add a new scope
  3. Visit the metadata endpoint https://yourhost/openam/oauth2/realms/root/.well-known/openid-configuration
  4. See the new scope is missing.
  5. Restart the webapp
  6. Visit the metadata endpoint, see that the new scope is now present.

Expected behavior
The new scope should be immediately visible.

Screenshots
immagine

Additional context
It seems that the issue was already fixed in the other fork openam-jp: https://github.com/openam-jp/openam/pull/155/files .
The fix should be applicable to this project too by applying the same change here:

@vharseko vharseko self-assigned this Sep 18, 2024
vharseko pushed a commit to vharseko/OpenAM that referenced this issue Sep 19, 2024
vharseko added a commit that referenced this issue Sep 19, 2024
@vharseko
Copy link
Member

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

2 participants