X509Cert: connect to user via ForeignKey rather than m2m relation
An X509 certificate should only map to a single user account - we can't do authentication properly if it maps to multiple, so this was an obviously necessary change. There are several migrations for making this conversion in steps.
Showing
- gracedb/api/backends.py 1 addition, 10 deletionsgracedb/api/backends.py
- gracedb/api/tests/test_authentication.py 2 additions, 2 deletionsgracedb/api/tests/test_authentication.py
- gracedb/api/tests/test_backends.py 2 additions, 2 deletionsgracedb/api/tests/test_backends.py
- gracedb/ligoauth/migrations/0041_x509cert_add_user_foreignkey.py 28 additions, 0 deletions.../ligoauth/migrations/0041_x509cert_add_user_foreignkey.py
- gracedb/ligoauth/migrations/0042_populate_x509cert_user_field.py 44 additions, 0 deletions.../ligoauth/migrations/0042_populate_x509cert_user_field.py
- gracedb/ligoauth/migrations/0043_x509cert_delete_users_m2m_field.py 26 additions, 0 deletions...goauth/migrations/0043_x509cert_delete_users_m2m_field.py
- gracedb/ligoauth/models.py 1 addition, 1 deletiongracedb/ligoauth/models.py
Loading
Please register or sign in to comment