forked from DefectDojo/django-DefectDojo
-
Notifications
You must be signed in to change notification settings - Fork 0
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
changed Oauth to oicd plugin and configured it.... #6
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…D_LDAP_* Original author: Lars Meijers <[email protected]>
…lugin ID on import
Django database engine supports OPTIONS entry in DATABASES setting. This entry is the only way to configure specific non-standard database connection settings, for instance: mutual TLS authentication. This commit adds DD_DATABASE_OPTIONS environment variable support as dictionary, empty by default.
…nt key permissions) Due to kubernetes/kubernetes#57923 we have to copy the provided client secrets to a temporary writable location and adjust private key file permissions (to 0600). This has to be done for all Pods which may connect to the database.
…GROUPS via environment
…es one When using non-DefectDojo native authentication backend, there could be a case when groups are created by this backend. For instance, when LDAP module is configured to mirror groups. This commit handles this case and creates/deletes Dojo_Group instance when "auth_group" is created/deleted.
When using non-DefectDojo native authentication backend, there could be a case when group membership is updated by this backend. For instance, when LDAP module is configured to mirror groups it will automatically add users to groups. This commit handles this case and update Dojo native group membership according to internal groups configured by auth backend.
This commit removes mysql requirements from Python and Docker. It also changes the default database engine in settings to avoid failure during dummy startup. This commit does not have chances to be merged into upstream.
…xing client key permissions
See also discussion in DefectDojo#9050
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are narrowing the scope of acceptable enhancements to DefectDojo in preparation for v3. Learn more here:
https://github.com/DefectDojo/django-DefectDojo/blob/master/readme-docs/CONTRIBUTING.md
Description
Describe the feature / bug fix implemented by this PR.
If this is a new parser, the parser guide may be worth (re)reading.
Test results
Ideally you extend the test suite in
tests/
anddojo/unittests
to cover the changed in this PR.Alternatively, describe what you have and haven't tested.
Documentation
Please update any documentation when needed in the documentation folder)
Checklist
This checklist is for your information.
dev
.dev
.bugfix
branch.Extra information
Please clear everything below when submitting your pull request, it's here purely for your information.
Moderators: Labels currently accepted for PRs:
Contributors: Git Tips
Rebase on dev branch
If the dev branch has changed since you started working on it, please rebase your work after the current dev.
On your working branch
mybranch
:In case of conflict:
When everything's fine on your local branch, force push to your
myOrigin
remote:To cancel everything:
Squashing commits
pick
byfixup
on the commits you want squashed outpick
byreword
on the first commit if you want to change the commit messageForce push to your
myOrigin
remote: