Repository navigation
docs(auth0): explain connection selection and request overrides - #628
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Documentation build overview
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6839e55dc3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Auth0 users can select a social or enterprise connection through the existing extra authorization arguments mechanism, but the backend documentation does not show how. Add a configured-connection example and a CSRF-protected Django login form, explain the explicit opt-in for request overrides, and distinguish login routing from authentication policy.
Document the shared
AUTH_EXTRA_ARGUMENTS_OVERRIDE_ALLOWLISTbehavior and cross-reference the Auth0 example.Related to python-social-auth/social-core#1075.
Validation: configured pre-commit hooks passed; Sphinx HTML build passed with warnings treated as errors. The configuration and request-override examples were also verified against Auth0 authorization URL construction without provider requests.