feat(jans-config-api): update swagger api

[yurem]

closes #9270

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

Closes #9273,

[dryrunsecurity]

DryRun Security Summary

The pull request modifies the format of the distinguished name (DN) string for a document in the DBDocumentService class, separating the inum value from the baseDn with a comma, and it is important to review the overall context and usage of this method to ensure that there are no potential security vulnerabilities.

Expand for full summary

Summary:

The code change in this pull request modifies the format of the distinguished name (DN) string for a document in the DBDocumentService class. The previous implementation concatenated the inum value directly with the baseDn, while the updated code separates the inum value from the baseDn with a comma. From an application security perspective, this change does not introduce any obvious security concerns, as it is a minor implementation detail related to the construction of the DN string.

However, it is important to review the overall context and usage of this method to ensure that there are no potential security vulnerabilities. Specifically, you should check if the inum value is properly sanitized and validated before being used in the DN string construction, as improper handling of user-supplied input can lead to security issues like injection vulnerabilities. Additionally, you may want to review the other methods in the DBDocumentService class to ensure that they are also implemented securely and follow best practices for application security.

Files Changed:

• jans-core/document-store/src/main/java/io/jans/service/document/store/service/DBDocumentService.java: The changes in this file modify the format of the distinguished name (DN) string for a document in the getDnForDocument method. The previous implementation concatenated the inum value directly with the baseDn, while the updated code separates the inum value from the baseDn with a comma. This change does not introduce any obvious security concerns, but it is important to review the overall context and usage of this method to ensure that there are no potential security vulnerabilities.

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-core'

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