mirror of https://github.com/zulip/zulip.git
c54b48452d
Fixes #17277. The main limitation of this implementation is that the sync happens if the user authing already exists. This means that a new user going through the sign up flow will not have their custom fields synced upon finishing it. The fields will get synced on their consecutive log in via SAML in the future. This can be addressed in the future by moving the syncing code further down the codepaths to login_or_register_remote_user and plumbing the data through to the user creation process. We detail that limitation in the documentation. |
||
|---|---|---|
| .. | ||
| jinja2 | ||
| __init__.py | ||
| backends.py | ||
| computed_settings.py | ||
| config.py | ||
| configured_settings.py | ||
| default_settings.py | ||
| dev_settings.py | ||
| dev_urls.py | ||
| email_backends.py | ||
| legacy_urls.py | ||
| prod_settings_template.py | ||
| sentry.py | ||
| settings.py | ||
| terms.md.template | ||
| test_extra_settings.py | ||
| test_settings.py | ||
| urls.py | ||
| wsgi.py | ||