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:
https://github.com/OpenIdentityPlatform/OpenAM/blob/48357235bd38c0019b4432215d9fdfd83fcc6da3/openam-oauth2/src/main/java/org/forgerock/oauth2/core/RealmOAuth2ProviderSettings.java#L1036-L1038