Oauth Client ID not conifugred correctly in Geoserver memory until manually saved

[giohappy]

It already happened a few times to me with three different GeoNode 4.1.x projects (Geoserver 2.23.0) run with Docker compose.

1. The Oauth2 client id and secret that are configured inside the .env file are correctly set automatically in Geoserver, I can see it from the usual geonode-oauth2 authentication filter page.
2. Try to login in Geoserver with the GeoNode button (oauth2 login). it fails because of an invalid client id. Indeed, the wrong id is visible in the URL(maybe a default value from Geoserver?).
3. Save the authentication configuration in Geoserver (clicking s both ave inside the geonode-oauth2 filter page, and the parent page).
4. The oauth2 login uses the expected Client id and succeeds

Notice that doing a Reload of Geoserver catalog doesn't solve the problem.

Apparently, the configuration of Geoserver happening when the Docker services are run for the first time brings to an inconsistent state of the Geoserver catalog, which can only be resolved with the Save action.