Skip to content

User auth test #10191

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

Merged
merged 5 commits into from
Nov 19, 2024
Merged

User auth test #10191

merged 5 commits into from
Nov 19, 2024

Conversation

yurem
Copy link
Contributor

@yurem yurem commented Nov 19, 2024

closes #10190

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

… tests

Signed-off-by: Yuriy Movchan <Yuriy.Movchan@gmail.com>
…ests

Signed-off-by: Yuriy Movchan <Yuriy.Movchan@gmail.com>
Signed-off-by: Yuriy Movchan <Yuriy.Movchan@gmail.com>
Copy link

dryrunsecurity bot commented Nov 19, 2024

DryRun Security Summary

The code changes in this pull request focus on improving the handling of user data, including user attributes, authentication, and SCIM functionality, with a few security-conscious updates, but no obvious security vulnerabilities introduced.

Expand for full summary

Summary:

The code changes in this pull request cover a wide range of modifications across multiple files in the Janssen Project. The changes primarily focus on improving the handling of user data, including user attributes, authentication, and SCIM (System for Cross-domain Identity Management) functionality. Overall, the changes do not introduce any obvious security concerns, but there are a few areas that should be reviewed to ensure the ongoing security and integrity of the application.

Files Changed:

  1. Database Configuration and Schema Changes:

    • The changes in the pgsql-config.md and mysql-config.md files update the database configuration, including password hashing, connection pool management, and data mapping. These changes generally follow good security practices.
    • The jans-sql.properties file updates the MySQL-specific configuration, including the use of simple JSON handling, which should be reviewed to ensure it does not introduce any security vulnerabilities.
    • The jans-schema.json and jans-schema-mappings.json files update the Janssen schema, including the renaming of the jansAddress attribute. These changes are mostly routine maintenance tasks.
  2. SCIM Functionality Changes:

    • The changes in the custom_scim_handler.java and custom_scim_handler.py files focus on the handling of SCIM search results, including the removal of sensitive user data (e.g., addresses) from the response. These changes are security-conscious.
    • The Scim2UserService.java file includes updates to the handling of user attributes, such as email addresses and extended attributes. These changes improve the overall functionality and security of the SCIM implementation.
  3. User Authentication and Attribute Management:

    • The changes in the UserAuthenticator.java and UserAuthenticatorService.java files focus on improving the handling of user authenticators, including the implementation of hashCode() and equals() methods. These changes help ensure the proper management of user authentication data.
    • The SimpleUser.java file includes updates to the user attribute management functionality, such as the addition of a removeAttributeValue() method. These changes can be beneficial for maintaining data integrity and user privacy.
  4. Test and Sample Code Changes:

    • The changes in the various test and sample code files, such as DatabaseTest.php, SqlEntryManagerSample.java, and SpannerSample.java, are mostly routine maintenance tasks and do not introduce any significant security concerns.

Overall, the code changes in this pull request appear to be focused on improving the functionality and maintainability of the Janssen Project, with a few security-conscious updates. While there are no obvious security vulnerabilities introduced, it's important to review the changes in the context of the entire application and ensure that the application's security practices are robust and up-to-date.

Code Analysis

We ran 9 analyzers against 22 files and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer Findings
Sensitive Files Analyzer 1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

@mo-auto mo-auto added area-documentation Documentation needs to change as part of issue or PR comp-docs Touching folder /docs comp-jans-auth-server Component affected by issue or PR comp-jans-core Component affected by issue or PR comp-jans-linux-setup Component affected by issue or PR comp-jans-orm Component affected by issue or PR comp-jans-scim Component affected by issue or PR labels Nov 19, 2024
Copy link

Copy link

Copy link

Copy link

@yuriyz yuriyz enabled auto-merge (squash) November 19, 2024 13:44
Copy link

Copy link

@yuriyz yuriyz merged commit 28a9d9c into main Nov 19, 2024
11 checks passed
@yuriyz yuriyz deleted the user_auth_test branch November 19, 2024 15:14
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-documentation Documentation needs to change as part of issue or PR comp-docs Touching folder /docs comp-jans-auth-server Component affected by issue or PR comp-jans-core Component affected by issue or PR comp-jans-linux-setup Component affected by issue or PR comp-jans-orm Component affected by issue or PR comp-jans-scim Component affected by issue or PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feat(jans-auth): cover custom attributes and authenticator functionality by DB tests
7 participants