-
Notifications
You must be signed in to change notification settings - Fork 85
fix(jans-config-api): security bugfixes #8963 #8974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
* updated the keycloak configuration file to reflect the configuration for the storage-spi Signed-off-by: Rolain Djeumen <uprightech@gmail.com>
Signed-off-by: Rolain Djeumen <uprightech@gmail.com>
Signed-off-by: Rolain Djeumen <uprightech@gmail.com>
* begin removing references to the metadata timer (functionality moved to the scheduler) Signed-off-by: Rolain Djeumen <uprightech@gmail.com>
* removed references to MetadataValidationTimer * refactored saml inbount and saml idp rest resource providers Signed-off-by: Rolain Djeumen <uprightech@gmail.com>
DryRun Security SummaryThe pull request focuses on improving the management of SAML Identity Providers and Service Providers in the Jans Config API application, including the removal of metadata file processing functionality, simplification of metadata file handling, and improvements to logging, potentially reducing the attack surface and mitigating security risks. Expand for full summarySummary: The code changes in this pull request are primarily focused on the management of SAML (Security Assertion Markup Language) Identity Providers (IDPs) and Service Providers (SPs) in the Jans Config API application. The key changes include the removal of various methods responsible for processing unprocessed metadata files, simplification of metadata file handling, and improvements to logging. From an application security perspective, the removal of the metadata file processing functionality could potentially reduce the attack surface and mitigate security risks associated with handling untrusted metadata files. However, it's important to ensure that the application still has alternative mechanisms in place to properly validate and update SAML metadata to maintain the security and integrity of the SAML integration. The code changes also include updates to the SAML configuration endpoints, which are crucial for maintaining proper access control and security configurations. It's essential to thoroughly review these changes and test the application to ensure that the SAML-related functionality continues to meet the security requirements. Overall, the changes appear to be focused on improving the SAML-related functionality and security of the Jans Config API. While the changes do not introduce any obvious security vulnerabilities, it's important to review the broader context of the application and ensure that the SAML integration and metadata handling processes are secure and robust. Files Changed:
Code AnalysisWe ran
Riskiness🟢 Risk threshold not exceeded. |
|
|
|
|
* fix(jans-linux-setup): improper scim configuration for jans kc #8210 * updated the keycloak configuration file to reflect the configuration for the storage-spi Signed-off-by: Rolain Djeumen <uprightech@gmail.com> * chore(jans-keycloak-integration): bump kc version to 24.0.0 #8315 Signed-off-by: Rolain Djeumen <uprightech@gmail.com> * fix(jans-config-api): broken build of saml config-api plugin #8963 * begin removing references to the metadata timer (functionality moved to the scheduler) Signed-off-by: Rolain Djeumen <uprightech@gmail.com> * fix(jans-config-api): broken build of saml config-api plugin #8963 * removed references to MetadataValidationTimer * refactored saml inbount and saml idp rest resource providers Signed-off-by: Rolain Djeumen <uprightech@gmail.com> --------- Signed-off-by: Rolain Djeumen <uprightech@gmail.com> Co-authored-by: Mohammad Abudayyeh <47318409+moabu@users.noreply.github.com> Former-commit-id: 974040e
Prepare
Description
Target issue
closes #issue-number-here
Implementation Details
Test and Document the changes
Please check the below before submitting your PR. The PR will not be merged if there are no commits that start with
docs:
to indicate documentation changes or if the below checklist is not selected.