feat(jans-core): use DB document store by default

[yurem]

closes #9179

• I confirm that there is no impact on the docs due to the code changes in this PR.

Closes #9268,

[dryrunsecurity]

DryRun Security Summary

The pull request includes changes to the Jans application's configuration, such as transitioning to a database-based document store, updating the SMTP configuration with sensitive information, and configuring an LDAP-based authentication mechanism, all of which require careful security review to ensure proper access controls, encryption, and data protection measures are in place.

Expand for full summary

Summary:

The code changes in this pull request are related to the configuration settings for the Jans application. The key changes include the transition from a local document store to a database-based document store, updates to the SMTP configuration that contain sensitive information, and the configuration of an LDAP-based authentication mechanism.

From a security perspective, these changes require careful review to ensure that proper access controls, encryption, and data protection measures are in place for the database storage, the SMTP configuration is properly secured, and the LDAP authentication process is implemented securely, including the use of SSL/TLS. Additionally, the miscellaneous configuration changes should be reviewed to understand their purpose and potential security implications within the overall application architecture.

Files Changed:

• jans-linux-setup/jans_setup/templates/configuration.ldif: This file contains the configuration settings for the Jans application, including the following changes:
  1. Document Store Configuration: The jansDocStoreConf configuration has been changed from using a "LOCAL" document store to a "DB" (database) document store, which may impact the way sensitive data is stored and accessed.
  2. SMTP Configuration: The jansSmtpConf configuration contains sensitive information, such as the key store file name, password, and signing algorithm, which need to be properly secured.
  3. LDAP Authentication Configuration: The jansDbAuth configuration sets up an LDAP-based authentication mechanism, which requires review to ensure the security of the authentication process, including the use of SSL/TLS.
  4. Miscellaneous Configuration: The jansOrgProfileMgt and jansScimEnabled settings are included in the configuration, and their security implications should be reviewed in the context of the overall application architecture.

Code Analysis

We ran 9 analyzers against 1 file and 0 analyzers had findings. 9 analyzers had no findings.

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[mo-auto]

Error: Hi @yurem, You did not reference an open issue in your PR. I attempted to create an issue for you.
Please update that issues' title and body and make sure I correctly referenced it in the above PRs body.

[sonarqubecloud]

Quality Gate passed for 'jans-linux-setup'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud