Enable and Fix keycloak User Registration Config along with defaulting to 'User' group for newly registered users

[RawSanj]

Enable and Fix Keycloak User Registration Config along with defaulting to the 'User' group for newly registered users:

1. This fixes the error in the Jhipster Realm config which throws an error when enabling the User Registration in Keycloak.
2. The User Registration is now by default enabled and newly registered accounts by default are assigned to the User group to get the USER Role.

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[CLAassistant]

All committers have signed the CLA.

[RawSanj]

This PR belongs to the label theme: keycloak. Not sure if I can edit the labels.

[atomfrede]

LGTM. Should we document this as a breaking change, such that existing applications can disable user registration as they might rely on the old default configuration?

[RawSanj]

LGTM. Should we document this as a breaking change, such that existing applications can disable user registration as they might rely on the old default configuration?

Would it go under - https://github.com/jhipster/jhipster.github.io/blob/main/pages/security.md#keycloak or in the release notes?

Or I can disable the user registration to false by default. But we might still require a note to inform users that User Registration is now fixed and can be enabled.

[atomfrede]

I would say lets keep it enabled as one can register without keycloak too by default.

[RawSanj]

@atomfrede Is there anything else I should work upon to get this merged?
If not, can you please merge this PR?

[idNoRD]

There are two "users" configuration keys in the json.
Can you please refactor to have only one "users" key to avoid json validation warning "Object contains duplicate keys 'users'"? Thanks

[mraible]

@idNoRD I don't see two users keys being added in this PR, so I believe your request is unrelated. Please open a new issue/PR for this.

[mraible]

@RawSanj I QA'd this PR today and I can confirm it enables registration by default and puts users in the proper group.

However, if I create a brand new app with JHipster 8.3.0 (using jhipster jdl blog-oauth2), I can enable user registration successfully and register just fine. Because of this, it seems this PR only enables user registration.

Can you please provide the steps needed to reproduce the issue where Keycloak throws an error when enabling user registration?

[RawSanj]

@mraible Looks like the registration issue is fixed in another PR-25679 merged (30 March) after this PR was raised (6 Jan).

This PR now only enables the User Registrations by default and Puts newly registered users into User Group/Role.
Let me know if we should skip this PR or sync up the changes and merge this PR?

[mraible]

@RawSanj If I create a new app with jhipster jdl blog-oauth2 with JHipster 8.4.0, enable registration in Keycloak, and create a new user, it has access to the Entities menu.

I thought this implies the new user is added to the correct group, but the new user has no groups.

Please sync this PR with main and we'll get it merged.