JWT base64-secret should not be mandatory in oauth2 profile
Motivation for or Use Case
Reproduce the error
Generate the JHipster application with OIDC authentication and select integration with JHipster Registry
Start the Keycloak container
Start jhipster-registry container -- docker-compose -f src/main/docker/jhipster-registry up
You shall see startup errors due to the null base64-secret configuration required by TokenProvider.
Specify some dummy long base64-secret under src/main/docker/central-server-config/localhost-config/application.yml and start JHipster Registry again. This time you should see the registry starts up correctly.
Related issues
Suggest a Fix
JHipster Registry Version(s)
Browsers and Operating System
[ ] Checking this box is mandatory (this is just to show you read everything)
Overview of the issue
JWT base64-secret should not be mandatory in oauth2 profile
Motivation for or Use Case
Reproduce the error
jhipster-registry
container --docker-compose -f src/main/docker/jhipster-registry up
base64-secret
configuration required by TokenProvider.src/main/docker/central-server-config/localhost-config/application.yml
and start JHipster Registry again. This time you should see the registry starts up correctly.Related issues
Suggest a Fix
JHipster Registry Version(s)
Browsers and Operating System