Jhipster Monolith with MongoDB with Keycloak Using MySql

[sthraki]

Hi ,

I was wondering if it's possible to have a Jhipster Spring Monolith with Keycloak , where Spring app uses MongoDB and Keycloak uses Mysql . Is it possible to configure JDL like that and generate app ?

[Tcharl]

Hi @sthraki and welcome!

The spring app using mongo and keycloak are of course possible: just use the relative options in jdl (authenticationType: oauth2, databaseType: mongodb). For the keycloak database, JHipster uses the default provided by the KC community: I don't know which one it is TBH, I think it's H2.
Still, note that the third party services (Keycloak, Redis, Elasticsearch, Consul, even databases) are not meant to be deployed as is in production: Jhipster provides a default configuration to ease the bootstrap locally or in development environment, but you'll have to install these soft by yourself in your IT environment to get production-grade services.
For example:

• Databases are not scaled by default, do not have automated backups
• ES is not secured with Oauth2
• Keycloak is not replicated neither uses a production-ready database.

Contribution to JH making these production-grade third party services for 'prod' profile could be a nice addition.

[TatyOko28]

Yes, this setup is possible.

You can run a JHipster Spring Monolith using MongoDB for the application data, while Keycloak uses MySQL as its own internal database.

Important clarification

JHipster only manages the database for your generated application.

So in your case:

• JHipster app → MongoDB
• Keycloak server → MySQL

These are two separate systems.

JDL Configuration

Your JDL only needs to define MongoDB for the JHipster application.

application {
  config {
    baseName myApp
    applicationType monolith
    authenticationType oauth2
    prodDatabaseType mongodb
    devDatabaseType mongodb
  }
}