2020-11-05

[[id:ac376401-a8b9-45c5-ab1a-4a77837bd03c][Partnership Squad Engineering Stand-up]]

<2020-11-05 Thu 8:30-9:00>

[[id:5f3e03a3-cfba-426d-97c1-9cb8e5860fc7][R&D Monthly Meeting]]

Thu Nov 5, 202010:00–11:00

DONE Look for a new wood stove

CLOSED: Fri Nov 6, 202008:57

DONE Draft roadmap for [[id:ef481268-f37b-43d0-b10b-1a52eb2d3236][ENG-12761 - Investigation of SAML login for Mobile]]

CLOSED: Fri Nov 6, 202008:57

Potential flow

+ Add `/account/login/sso/auth/` endpoint that has a "sign-in using Single Sign-on" button to POST to `/account/login/?next=/account/login/sso/redirect/`

+ Modify `/saml2/acs/` AssertionConsumerServiceView and when `app_login` relaystate is set:

- Stores the SAMLResponse data in the DB

- Do not log the user in

- Generates a one-time auth token

+ Add `/account/login/sso/verify/` endpoint which takes a POSTed one-time auth token and returns the SAMLResponse expected from `login_with_saml2_response` function

Questions

+ Can the mobile app POST directly to the account/login endpoint or do we need a "new" login template that has only one button that can POST with the appropriate `next` GET parameter for a relay state?

API experiments

#+begin_src restclient

GET https://saml-azure.15five.localhost/mobile/login_with_saml_access_key/?debug_api=1&check_signature=false

#+end_src

#+begin_src restclient

GET https://saml-azure.15five.localhost/mobile/login_with_saml_access_key/?debug_api=1&check_signature=false&access_key=3

#+end_src

#+begin_src restclient

GET https://saml-azure.15five.localhost/mobile/login_with_saml_access_key/?debug_api=1&check_signature=false&access_key=123ff092-2f7c-4cb2-90b1-5412391e4219

#+end_src

DONE Create user stories on https://15five-dev.atlassian.net/browse/ENG-12761

CLOSED: Fri Nov 6, 202008:57

DONE Review [[id:4ab0f084-d9c6-4b40-a455-e7e34ca1971c][Carleigh Smith]] comment on [[roam:TRIAGE-1585]]

CLOSED: Fri Nov 6, 202008:57