Add a TPA pipeline step to allow force sync of user details.
The feature is controlled by a switch on the provider. Emails are sent if the email changes during the sync. We skip syncing the username/email if there would be a conflict.
Showing
- common/djangoapps/third_party_auth/migrations/0013_sync_learner_profile_data.py 29 additions, 0 deletions...d_party_auth/migrations/0013_sync_learner_profile_data.py
- common/djangoapps/third_party_auth/models.py 8 additions, 0 deletionscommon/djangoapps/third_party_auth/models.py
- common/djangoapps/third_party_auth/pipeline.py 81 additions, 1 deletioncommon/djangoapps/third_party_auth/pipeline.py
- common/djangoapps/third_party_auth/settings.py 1 addition, 0 deletionscommon/djangoapps/third_party_auth/settings.py
- common/djangoapps/third_party_auth/tests/test_pipeline_integration.py 104 additions, 3 deletions...oapps/third_party_auth/tests/test_pipeline_integration.py
- common/templates/emails/sync_learner_profile_data_email_change_body.txt 25 additions, 0 deletions...es/emails/sync_learner_profile_data_email_change_body.txt
- common/templates/emails/sync_learner_profile_data_email_change_subject.txt 6 additions, 0 deletions...emails/sync_learner_profile_data_email_change_subject.txt
Loading
Please register or sign in to comment