jans-docs: Lock Updates to README, Cedarling and Lock Master docs.

[nynymike]

Prepare

• Read PR guidelines
• Read license information

---

Description

Mike's latest updates to the Lock docs and diagrams.

Target issue

#8831

Implementation Details

Just words and pictures

---

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 focuses on updating the documentation for the Janssen Project's authorization and access control platform, the "Janssen Lock" system, including changes to the project's navigation, expansion of the "Lock Master" component documentation, renaming the project, and explaining the distributed authorization model used by the system.

Expand for full summary

Summary:

The code changes in this pull request focus on updating the documentation for the Janssen Project's authorization and access control platform, known as the "Janssen Lock" system. The key changes include:

1. Removal of several sections related to the "Lock Guide" from the project's navigation, indicating a potential shift in the focus or deprecation of the Lock functionality.
2. Expansion of the documentation for the "Lock Master" component, providing more details about its architecture, configuration, logging, and OAuth security aspects.
3. Renaming the project from "Jans Lock" to "Janssen Lock" and providing a more detailed overview of the system's architecture, which consists of Cedarling, Lock Master, and Jans Auth Server components.
4. Explanation of the distributed authorization model used by Janssen Lock, including the Policy Store, Cedarling, and their roles in the overall system.

From an application security perspective, the changes highlight the importance of the Janssen Lock system in the overall security architecture of the Janssen Project. The use of a declarative policy engine (Cedar), centralized policy management, and JWT token validation are all positive security features that should be thoroughly reviewed and tested to ensure their proper implementation and effectiveness.

Files Changed:

1. mkdocs.yml: The changes remove several sections related to the "Lock Guide" from the navigation, potentially indicating a shift in the focus or deprecation of the Lock functionality.
2. docs/admin/lock/lock-master.md: The changes expand the documentation for the "Lock Master" component, providing more details about its architecture, configuration, logging, and OAuth security aspects.
3. docs/admin/lock/README.md: The changes rename the project from "Jans Lock" to "Janssen Lock" and provide a more detailed overview of the system's architecture and the distributed authorization model used.
4. docs/admin/lock/cedarling.md: The changes document the Cedarling, which is a WebAssembly-based policy decision point (PDP) that enables developers to define and enforce security policies using the Cedar policy syntax.

Code Analysis

We ran 9 analyzers against 11 files and 0 analyzers had findings. 9 analyzers had no findings.

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.