Skip to content
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

fix(jans-linux-setup): default value of jans link prompt #8768

Merged
merged 1 commit into from
Jun 25, 2024

Conversation

devrimyatar
Copy link
Contributor

closes #8767

Signed-off-by: Mustafa Baser <mbaser@mail.com>
Copy link

dryrunsecurity bot commented Jun 24, 2024

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

DryRun Security Status Findings
Server-Side Request Forgery Analyzer 0 findings
Configured Codepaths Analyzer 0 findings
Secrets Analyzer 0 findings
Authn/Authz Analyzer 3 findings
SQL Injection Analyzer 0 findings
Sensitive Files Analyzer 0 findings
IDOR 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 are primarily focused on updating the configuration and setup options for the Jans application. The key changes include:

  1. Disabling the installation of the jans-link component by default.
  2. Updating the logic for setting the 'install_jans_link' option, where it is now set to True if the --install-jans-link argument is provided.
  3. Renaming the --no-link argument to --install-jans-link and adding a new --install-jans-keycloak-link argument.

From an application security perspective, these changes do not appear to introduce any obvious security concerns. The changes are primarily related to configuration options and the installation of optional components, rather than changes to core security-critical functionality.

However, it's important to thoroughly review any configuration changes to ensure that they do not have unintended consequences or introduce security vulnerabilities. Additionally, it's crucial to understand the purpose and dependencies of the jans-link and jans-keycloak-link components, and how their installation or removal might affect the overall system.

Files Changed:

  1. jans-linux-setup/jans_setup/setup_app/config.py: The changes in this file disable the installation of the jans-link component by setting self.install_jans_link = False.
  2. jans-linux-setup/jans_setup/setup_app/setup_options.py: The changes in this file update the logic for setting the 'install_jans_link' option, where it is now set to True if the --install-jans-link argument is provided.
  3. jans-linux-setup/jans_setup/setup_app/utils/arg_parser.py: The changes in this file rename the --no-link argument to --install-jans-link and add a new --install-jans-keycloak-link argument.

Powered by DryRun Security

@mo-auto mo-auto added comp-jans-linux-setup Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality labels Jun 24, 2024
Copy link

sonarcloud bot commented Jun 24, 2024

@yuriyz yuriyz enabled auto-merge (squash) June 24, 2024 10:53
@yuriyz yuriyz merged commit 47d69ba into main Jun 25, 2024
10 checks passed
@yuriyz yuriyz deleted the jans-linux-setup-jans-link-prompt-8767 branch June 25, 2024 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-jans-linux-setup Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fix(jans-linux-setup): Default value for jans link prompt is NO
4 participants