Rebuild SSO Sequence

[kjporter]

Description The site presently uses VATUSA's ULS. VATUSA will sunset ULS on 12/31/22. This authentication sequence must be replaced with a direct interface to the VATSIM Connect SSO.

Acceptance Criteria

• [X] Authentication sequence is seamless and the change is not noticeable to users

Accepted By: @iccowan

Dev Notes

• This should be developed as a patch so it can be shared with the 10 (approx) other sites that use the same website baseline
• One thing to consider here is that we're going to have to rework how we pull data for users. Right now, we update that information when the user logs in because we get that back with the user data. Do we want to request that data from VATUSA when the users login is successful through VATSIM SSO or just wait and let an hourly(? I think?) update sync the user data.
• Probably not a necessity to pull the data every time that a user logs in (we've authenticated the user, so we know who it is). I'll look at the login sequence, but I think we can just pull from the database and allow the sync to automate the pull from VATUSA.
• There is an existing VATSIM Connect SSO integration for Laravel located at: https://github.com/vatsimnetwork/connect-laravel

Working Branch sso-migration

PR

206

QA Notes

Deployment Notes

[iccowan]

Tagged as a points value of 3. This shouldn't be overly complex to setup (really just rework our current flow), but will take some refactoring of the VATUSA data-pulling and updating process.

VATUSA will sunset ULS in the winter of 2022.

Do we have a date for this? Or just sometime this winter?

[kjporter]

Do we have a date for this? Or just sometime this winter?

No hard date, but I'm targeting migration complete by November. VATUSA12 is encouraging us (WMs) to get this done as soon as possible.