No description provided.
This probably needs devise to provide a central model, in which clients can be added.
There are 2 common conventions, each with drawbacks:
Through this process, people have to sign in, then they can add providers to control auth to their accounts.
This is the simpler process, in which someone coming from a provider we've never seen before is compared to existing users based on emails, and if there is a match, the new oAuth account is associated with existing users
TAs can now login from multiple locations. Closes #82
The TA Queue is kind of doing its own thing in terms of logins. Logging in just means you are being created in the DB, and logging out removes you from the DB, so it's all very transient. This decision was made based on a number of factors not worth enumerating here. Thank you for your input, though, as that advice has lots of application outside of this case.