docs(config): update instructions in LDAP configuration document

[ossdhaval]

Prepare

• Read PR guidelines
• Read license information

---

Description

Target issue

closes #issue-number-here

Implementation Details

---

Test and Document the changes

• Static code analysis has been run locally and issues have been fixed
• Relevant unit and integration tests have been added/updated
• Relevant documentation has been updated if any (i.e. user guides, installation and configuration guides, technical design docs etc)

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.

• 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 introduces changes to the Janssen Server's LDAP configuration management, focusing on secure LDAP configurations, proper credential management, input validation, access control, and logging and auditing to ensure the overall security and maintainability of the LDAP configuration management solution.

Expand for full summary

Summary:

The code changes in this pull request are related to the configuration of the Lightweight Directory Access Protocol (LDAP) in the Janssen Server. The changes provide details on how to manage LDAP configurations using the Janssen command-line interface (CLI) and the Configuration REST API. The code emphasizes the importance of using secure LDAP configurations, proper credential management, input validation, access control, and logging and auditing to ensure the overall security and maintainability of the LDAP configuration management solution.

From an application security perspective, the key points to highlight are:

1. The use of secure LDAP configurations, such as enabling SSL/TLS communication and using non-anonymous binds, to protect the LDAP communication and ensure proper authentication and authorization.
2. The proper management of LDAP bind credentials, including secure storage and encryption, to protect these sensitive credentials.
3. The need for thorough input validation to prevent potential injection attacks, such as LDAP injection, when creating or updating LDAP configurations.
4. The importance of implementing appropriate access control mechanisms to ensure that LDAP configuration management operations are properly authorized.
5. The requirement for comprehensive logging and auditing of LDAP configuration management operations to enable security monitoring and incident investigation.

Overall, the changes appear to be focused on providing a secure and maintainable LDAP configuration management solution for the Janssen Server.

Files Changed:

• docs/admin/config-guide/auth-server-config/ldap-configuration.md: This file provides documentation on how to manage LDAP configurations using the Janssen CLI and Configuration REST API. It covers various operations, such as getting, adding, updating, deleting, and patching LDAP configurations, and emphasizes the importance of using secure LDAP configurations and proper credential management practices.

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.