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.

[dryrunsecurity]

DryRun Security Summary

The provided code changes focus on improving the security and manageability of the Jans Config API by enhancing the schema definitions for various components, while also addressing a minor bug fix in the DBDocumentService class.

Expand for full summary

Summary:

The provided code changes primarily focus on improving the security and manageability of the Jans Config API by enhancing the schema definitions for various components, such as attributes, clients, scopes, and UMA resources. These changes introduce new security-related features and configurations, which can help ensure data integrity, improve access control, and enable better logging and auditing capabilities.

The changes to the DBDocumentService class appear to be a minor bug fix that ensures the correct format of the Distinguished Name (DN) string for documents. While this change does not directly introduce any security vulnerabilities, it is important to maintain a comprehensive security posture for the entire application by regularly reviewing the codebase, implementing input validation and sanitization, and conducting security audits and penetration testing.

Files Changed:

1. jans-core/document-store/src/main/java/io/jans/service/document/store/service/DBDocumentService.java:

   • The changes modify the format of the returned DN string for a document to ensure that the inum (unique identifier) is correctly included.
   • The getDnForDocument method is a utility function used throughout the DBDocumentService class to build the DN string for various document-related operations.
   • While the code change does not introduce any immediate security concerns, it is essential to maintain a comprehensive security posture for the entire application.

2. jans-config-api/docs/jans-config-api-swagger.yaml:

   • The changes update the schema definitions for various components, such as JansAttribute, Client, Scope, and UmaResource.
   • The updates include features like attribute validation, scope management, UMA resource management, client configuration, logging and auditing, and asset management.
   • These changes aim to enhance the security and manageability of the Jans Config API by providing more granular control over security-related aspects of the system.
   • Reviewing these changes and ensuring the appropriate security controls are in place is crucial for maintaining the overall security posture of the application.

Code Analysis

We ran 9 analyzers against 2 files and 0 analyzers had findings. 9 analyzers had no findings.

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[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

[sonarqubecloud]

Quality Gate passed for 'jans-config-api-parent'

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