-
Notifications
You must be signed in to change notification settings - Fork 9
Description
Issue: Documentation Corrections and Enhancements
1. Incorrect Description for SOCIALACCOUNT_AUTO_SIGNUP
Under Authentication Documentation:
-
Current Description:
SOCIALACCOUNT_AUTO_SIGNUP = Trueforces new users to fill out a signup form even if the provider does provide the email address. -
Correct Description:
SOCIALACCOUNT_AUTO_SIGNUP = Falseforces new users to fill out a signup form even if the provider does provide the email address.
2. Database Initialization Required After Setting OIDC
When choosing OIDC (e.g. Keycloak) as an IDP, the database initialization must be repeated after the allauth Library Installation as described in the Database Initialization Documentation.
3. Mentioning the LOGIN_FORM Parameter
Including a reference to the LOGIN_FORM parameter in the authentication documentation All Auth documentation would be helpful for clarity and completeness.
4. Additional Profile Parameters
The following parameters should also be mentioned in All Auth documentation to clarify their role:
PROFILE_UPDATE = False
PROFILE_DELETE = False5. TLS Certificate for On-Premise IDP Deployments
For on-premise IDP deployments (e.g. Keycloak), adding the TLS IDP Certificate to Python Packages is necessary unless an alternative implementation is provided by the project maintainers.
- Example Command:
echo 'COMPANY CA
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----' | sudo tee -a /srv/rdmo/rdmo-app/env/lib/python*/site-packages/certifi/cacert.pemSuggested Actions
- Update the documentation for
SOCIALACCOUNT_AUTO_SIGNUPto reflect the correct behavior. - Add a note under OIDC configuration to repeat the database initialization step.
- Include references to the
LOGIN_FORM,PROFILE_UPDATE, andPROFILE_DELETEparameters for better user guidance. - Provide instructions or a note about adding TLS certificates for on-premise IDP deployments.
Thank you for considering these updates!