Skip to content

docs(saml): document User Identifier Source and Match Users By - #16322

Open
paulOsinski wants to merge 2 commits into
devfrom
feat/saml-user-identifier-docs
Open

paulOsinski wants to merge 2 commits into
devfrom
feat/saml-user-identifier-docs

Conversation

@paulOsinski

Copy link
Copy Markdown
Contributor

Description

Documentation for the new SAML user-matching settings in DefectDojo Pro (User Identifier Source and Match Users By). Until now a SAML login was always matched by comparing the assertion's NameID against the DefectDojo username, and the page told readers to change what the IdP sends as the NameID. Pro can now take the identifier from a mapped attribute instead and compare it against username or email, which is what an opaque or transient NameID needs.

Changes to docs/content/admin/sso/PRO__saml.md:

  • New Matching logins to users section: the two settings, when to use a mapped attribute, keeping the NameID but matching on email, and how created users get their username.
  • Setup steps renumbered to include the two settings; the attribute-mapping bullet no longer says username is the only match field.
  • Cloud-vs-on-prem table: the "Username matching" row now describes the options and the two environment variables.
  • Troubleshooting "User not found" entry rewritten around identifier mismatch with the three remedies.

Docs only; no code changes.

Test results

Rendered locally; links are in-page anchors.

Documentation

This PR is the documentation.

🤖 Generated with Claude Code

DefectDojo Pro can now match a SAML login by the NameID or by a mapped
attribute, compared against username or email. Add a "Matching logins to
users" section, fold the two settings into the setup steps, update the
cloud-vs-on-prem table, and rewrite the "User not found" troubleshooting
entry around identifier mismatch.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@paulOsinski paulOsinski added this to the 3.5.0 milestone Oct 13, 2026
@github-actions github-actions Bot added the docs label Oct 13, 2026
@dryrunsecurity

Copy link
Copy Markdown

DryRun Security

This pull request modifies sensitive codepaths in dojo/db_migrations and dojo/finding by an author not on the allowed list. These changes are flagged as low severity and are non-blocking.

Configured Sensitive Codepath Modified by Non-Allowed Author in dojo/db_migrations/0299_finding_test_numsev_index.py (drs_76a67a60)
Vulnerability Configured Sensitive Codepath Modified by Non-Allowed Author
Description File 'dojo/db_migrations/0299_finding_test_numsev_index.py' matches configured sensitive codepath pattern 'dojo/db_migrations/*.py' and was modified by 'paulOsinski' (commit 66898c9) who is not in the allowed authors list.
Configured Sensitive Codepath Modified by Non-Allowed Author in dojo/finding/models.py (drs_b0f9227b)
Vulnerability Configured Sensitive Codepath Modified by Non-Allowed Author
Description File 'dojo/finding/models.py' matches configured sensitive codepath pattern 'dojo/finding/*.py' and was modified by 'paulOsinski' (commit 66898c9) who is not in the allowed authors list.

Comment to provide feedback on these findings.

Report false positive: @dryrunsecurity fp [FINDING ID] [FEEDBACK]
Report low-impact: @dryrunsecurity nit [FINDING ID] [FEEDBACK]

Example: @dryrunsecurity fp drs_90eda195 This code is not user-facing

All finding details can be found in the DryRun Security Dashboard.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant