Y25-660 - As a developer (Ben) I would like to integrate the Okta login system.

[BenTopping]

User story

As a developer (Ben) I would like to integrate the Okta login system. This should be possible via https://github.com/okta/okta-vue or okta js. Developer will need to submit a service desk to create an okta app in org to test with.

Note: if while developing it makes more sense to split this into two stories (setting up okta/discovery and implementing okta) please feel free.

Who are the primary contacts for this story

Ben T

Who is the nominated tester for UAT

Developer and test with users to confirm.

Acceptance criteria

Consider if these features can be featured flagged to decouple testing and deployment.
To be considered successful the solution must allow:

• Traction app is created in okta

• Unknown We will need a new Okta app for each environment (how to use okta across multiple environments (uat, training, prod))?

• Unknown Correct dev setup locally, stub auth for tests etc

• All traction ui pages move behind okta authentication. This should be feature flagged / disable-able in case they run into issues in the labs.

• okta integration works with SSO and existing accounts

• Requests to traction service include the relevant access token

Additional context

This is an outcome of #2430
See okta proposed integration
See research doc

[StephenHulme]

Ticket to create Traction Okta app created: https://sanger.freshservice.com/a/tickets/56517

[StephenHulme]

I have setup an initial page in traction UI at http://localhost:5173/#/protected on branch y25-660-add-okta.

However, it runs into an issue with the use of the hash-anchor when redirecting. This issue-comment outlines the problem and solution.

[StephenHulme]

We have a login screen:

[StephenHulme]

Sanger Okta config: https://sanger.okta.com/.well-known/openid-configuration?client_id=0oaurrnc5aBDHc8AI417