-
Notifications
You must be signed in to change notification settings - Fork 76
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
docs(fido2): updates to fido2 config doc #8809
Conversation
Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and 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 provided code change introduces documentation on how to configure the Janssen FIDO2 (Fast IDentity Online) functionality in the Janssen Server. The documentation covers three main aspects: command-line configuration, text-based UI configuration, and REST API configuration. From an application security perspective, the changes are notable for their emphasis on secure configuration management, proper handling of sensitive configuration properties, configurable security settings, and the inclusion of logging and monitoring capabilities. The documentation highlights the use of secure command-line, text-based UI, and REST API interfaces to manage the FIDO2 configuration, ensuring that configuration changes are performed through controlled and auditable channels. The FIDO2 configuration includes sensitive information, such as the issuer, base endpoint, and various folder paths for storing certificates and metadata, which require proper access control and secure storage. Additionally, the configuration allows administrators to control various security-related settings, and the inclusion of logging and monitoring features can be leveraged to monitor and audit the FIDO2 functionality for any security-related events or anomalies. Files Changed:
Powered by DryRun Security |
Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
* docs: update fido2 configuration document Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com> * fido2 : add schema format and example Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com> * docs: update file names Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com> * docs: remove old files Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com> * docs(fido2): update the instructions for update conf section Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com> * docs(fido2): proofreading Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com> --------- Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com> Co-authored-by: Devrim <devrimyatar@gluu.org> Former-commit-id: 90a98de
Prepare
Description
Target issue
closes #issue-number-here
Implementation Details
Test and Document the changes