Repository navigation
Document SAML 2.0 authentication - #320
Open
stephan-wolf-ais wants to merge 4 commits into
Open
stephan-wolf-ais wants to merge 4 commits into
stephan-wolf-ais wants to merge 4 commits into
Conversation
Add a guide for configuring login via SAML 2.0: API server and frontend configuration, registering Dependency-Track at the identity provider, username and email attributes, user provisioning, team synchronization, group provisioning, examples for Keycloak and Entra ID, troubleshooting, and limitations. Regenerate the configuration reference to include dt.frontend-url and the dt.saml.* properties, list SAML users in the access control concept, and link the new guide from the feature list and the OIDC and LDAP guides. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Stephan Wolf <stephan.wolf@kontron-ais.com>
Explain the difference between the subject identifier, which decides which account a login belongs to, and the username. Describe how Dependency-Track matches, renames, and binds accounts at login, when it refuses a login, and use the object ID as subject identifier in the Entra ID example. State that the IdP metadata URL must use HTTPS, and regenerate the configuration reference for dt.saml.subject-attribute. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Stephan Wolf <stephan.wolf@kontron-ais.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Stephan Wolf <stephan.wolf@kontron-ais.com>
The API server reports SAML availability in the public system capabilities instead of a dedicated /saml/availability endpoint. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Stephan Wolf <stephan.wolf@kontron-ais.com>
This branch has not been deployed
This file contains hidden or 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
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.
Add a guide for configuring login via SAML 2.0: API server and frontend configuration, registering Dependency-Track at the identity provider, username and email attributes, user provisioning, team synchronization, group provisioning, examples for Keycloak and Entra ID, troubleshooting, and limitations.
Regenerate the configuration reference to include dt.frontend-url and the dt.saml.* properties, list SAML users in the access control concept, and link the new guide from the feature list and the OIDC and LDAP guides.