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
When using the client-scope properties on realm resource there is a "chicken-egg-problem" (see #470 (comment)). Version 5.1 added dedicated resources to control client-scope for realms (realm_default_client_scopes & realm_optional_client_scopes). It might make sense to have only one place to configure the realm scopes in future. Therefore I propose to flag those client-scope properties from realm resource as deprecated (deprecation docs) and give a hint to use the newly introduced separate resource for configuring the realm client scopes, hat do you think?
Description
When using the client-scope properties on realm resource there is a "chicken-egg-problem" (see #470 (comment)). Version 5.1 added dedicated resources to control client-scope for realms (realm_default_client_scopes & realm_optional_client_scopes). It might make sense to have only one place to configure the realm scopes in future. Therefore I propose to flag those client-scope properties from realm resource as deprecated (deprecation docs) and give a hint to use the newly introduced separate resource for configuring the realm client scopes, hat do you think?
References:
The text was updated successfully, but these errors were encountered: