Clarify SSO setup via Database Admin interface - #12474
Open
br413 wants to merge 3 commits into
Open
Conversation
Fixes inventree#10415 by documenting that Social applications are configured in Django admin at /admin/, not via config.yaml or API.
✅ Deploy Preview for inventree-web-pui-preview canceled.
|
SchrodingersGat
approved these changes
Jul 27, 2026
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.
Summary
Updates SSO documentation to match current setup: provider backends in
config.yaml, client credentials as Social applications in the Database Admin at/admin/.Fixes #10415
Changes
/admin/access, trailing slash, andINVENTREE_ADMIN_ENABLEDTest plan
Refs #10415