Repository navigation
feat(backend): enable OIDC/oAuth2 provider by default - #12731
Conversation
Closes inventree#6339
…default-enable-oidc
✅ Deploy Preview for inventree-web-pui-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #12731 +/- ##
==========================================
+ Coverage 87.13% 87.16% +0.02%
==========================================
Files 1483 1483
Lines 100534 100662 +128
Branches 11524 11615 +91
==========================================
+ Hits 87604 87737 +133
+ Misses 12868 12863 -5
Partials 62 62
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
…feat(backend)--add-scim
…default-enable-oidc
…feat(backend)--add-scim
|
@SchrodingersGat ready for review |
|
API number bump addressed |
| MIGRATIONS_CHECK_DONE = False | ||
|
|
||
| OIDC_CLIENT_CHECKED = False | ||
| DEFAULT_OIDC_APP_ID = 'zDFnsiRheJIOKNx6aCQ0quBxECg1QBHtVFDPloJ6' |
There was a problem hiding this comment.
Should this be configurable at the system level? Or is it important that it is hard-coded across all InvenTree instances?
There was a problem hiding this comment.
No, it being well-known and stable is important for seamlessly working with the python-api and possibly the app
There was a problem hiding this comment.
additional client can be create via the API
|
Are there existing docs for OIDC configuration? It does not appear that this PR adds any |
there is https://docs.inventree.org/en/stable/api/#oauth2-and-oidc and there is not much more to it then creating and application and using it in whatever client you use. |
…default-enable-oidc
…default-enable-oidc
|
@SchrodingersGat I have adapted the docs a bit and added more descriptive descriptions to the forms |


This has been shipping with the codebase for a while but disabled by default. This PR changes that.
oAuth2 is the default standard for secure inter-application communication. I think it is reasonable to shift ppl towards it for most surfaces (pattform integrations, apps, desktop clients, mcp servers).
TODO:
Related:
Ref #12714
Contains #12713
Closes #12746