Resolve "Backend/Frontend - Platform - Authentication Setup"
HEY, HEY LISTEN!
🧚
Okay dokie big one here, for the reviewer there's a few things to should cover before you start reviewing, since this also covers a few different areas:
- Changes to the pipeline:
- Changed test image to a lighter weight one which has
chromeandnodeby default rather than using achromeservice on anodeimage, this should reduce the amount of storage we're using preventing runner out of storage error. - Setup so that the pipeline will only run on merge requests with changes to the frontend folder.
- Changed the node image.
- Changed test image to a lighter weight one which has
- Added in authentication
- Followed a similar setup to
passport.jswhich means we can easily add and remove different authentication strategies - I created a set of routes that we reuse throughout the different strategies.
- This should
404when using an invalid strategy. - If no
redirect_urlis supplied throws a200
- This should
- Followed a similar setup to
To Test
- You're gonna need a new
.envcovering the provider keys, it's shared in the teams chat.
Closes #33 (closed)
Edited by Liam Mcmanus