fix(jans-linux-setup): remove saml_scim_client

[devrimyatar]

closes #9047

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

[dryrunsecurity]

DryRun Security Summary

The pull request removes a client configuration for the "Jans SCIM Client for SAML" from the clients.json file, which was used for SCIM integration with SAML, and it's important to review the remaining client configurations to ensure that the authorization methods, grant types, and scopes are appropriate and aligned with the application's security requirements.

Expand for full summary

Summary:

The code changes in this pull request involve the removal of a client configuration from the clients.json file. The removed client was the "Jans SCIM Client for SAML," which was used for SCIM (System for Cross-domain Identity Management) integration with SAML (Security Assertion Markup Language). From an application security perspective, the removal of this client configuration does not seem to introduce any immediate security concerns. However, it's important to consider the overall context and the potential impact of this change on the application's security posture. The removal of the SCIM client may be part of a larger architectural or functional change, and it's essential to ensure that the application's SCIM integration is properly handled and that any potential security implications are thoroughly assessed. Additionally, it's worth reviewing the remaining client configurations to ensure that the authorization methods, grant types, and scopes are appropriate and aligned with the application's security requirements.

Files Changed:

• jans-linux-setup/jans_setup/templates/jans-saml/clients.json: This file has been updated to remove the "Jans SCIM Client for SAML" client configuration, which had the client prefix "2100." and was used for SCIM integration with SAML. The remaining client configurations appear to be for Keycloak-related clients, which are used for SAML authentication, API access, and master realm authentication. It's recommended to review these remaining client configurations to ensure that the authorization methods, grant types, and scopes are appropriate and aligned with the application's security requirements, especially for the "kc_scheduler_api" client, which has a broad set of scopes.

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.

[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