Migrate Helix SSO to new provider implementation

meilinger commented 5 years ago

Currently, we are using an older implementation (circa 2016/2017) of Helix to support IAFC's SSO capabilities w/ FireCARES. In order to maintain operational status w/ Helix for IAFC user login, we'll need to update FireCARES to handle the new/alternate attributes identifying users. We should be able to continue to use OAuth2.

~430 currently-registered users use Helix for authentication as indicated in their usernames (about 25% of registered users)
Requires update to URL settings for new endpoints (we'll still use OAuth2)
Requires mapping new incoming user attributes correctly
- Previously, we had used membershipid as an indicator of if the user could login as well as the suffix of username
- Additionally, we had to grab the functional title of the user to determine if they were a legitimate administrator of their department (whether/not they should be promoted to an admin)

see firecares/firecares_core/views.py for implementation

meilinger commented 5 years ago

see 8c0ab8718eb28841f507d9cfed911d45b7be5836

meilinger commented 5 years ago

Working w/ IAFC on straggling 27 users that didn't get migrated (membershipid were missing from mapping CSV used for user migration)...

meilinger commented 4 years ago

27 straggling users were no longer IAFC members.

FireCARES / firecares

Migrate Helix SSO to new provider implementation #520