docs: update default authn method document

[ossdhaval]

Documents in the configuration guide section should follow the same logical grouping as in the TUI

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)

[dryrunsecurity]

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
Configured Codepaths Analyzer	✅	0 findings
Secrets Analyzer	✅	0 findings
IDOR Analyzer	✅	0 findings
Sensitive Files Analyzer	✅	0 findings
Authn/Authz Analyzer	✅	0 findings
AppSec Analyzer	✅	0 findings

Note

🟢 Risk threshold not exceeded.

Change Summary (click to expand)

The following is a summary of changes in this pull request made by me, your security buddy 🤖. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective.

Summary:

The code changes in this pull request focus on the default authentication method configuration in the Janssen Server. The changes provide detailed documentation on how administrators can manage the default authentication method using the command-line interface, text-based UI, and REST API. From an application security perspective, this is an important feature as it allows administrators to choose the appropriate authentication method based on the security requirements of the application.

To ensure the security of the Janssen Server, it is crucial that the default authentication method is set to a secure and robust option, such as multi-factor authentication, to prevent unauthorized access. Additionally, it is essential to implement proper access controls, authentication, and authorization mechanisms for the CLI, TUI, and REST API tools used to manage the authentication configuration. Logging and monitoring of any changes to the default authentication method should also be in place to ensure accountability and detect any suspicious activities.

Files Changed:

• docs/admin/config-guide/default-authentication-method-config.md: This file provides detailed documentation on how to configure the default authentication method in the Janssen Server. It covers the use of the command-line interface, text-based UI, and REST API to perform these tasks. The document also highlights the importance of securing the default authentication method and controlling access to the configuration tools.

Powered by DryRun Security