You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Visit the metadata endpoint, see that the new scope is now present.
Expected behavior
The new scope should be immediately visible.
Screenshots
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:
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:
Expected behavior
The new scope should be immediately visible.
Screenshots
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:
OpenAM/openam-oauth2/src/main/java/org/forgerock/oauth2/core/RealmOAuth2ProviderSettings.java
Lines 1036 to 1038 in 4835723
The text was updated successfully, but these errors were encountered: