Upgrade Okta Classic to Okta Identity on Staging - Githubissues

CDCgov / prime-reportstream

ReportStream is a public intermediary tool for delivery of data between different parts of the healthcare ecosystem.

https://reportstream.cdc.gov

Creative Commons Zero v1.0 Universal

64 stars 38 forks source link

Upgrade Okta Classic to Okta Identity on Staging #14297

Open chris-kuryak opened 2 weeks ago

chris-kuryak commented 2 weeks ago

Problem statement

In order to obtain new features and avoid being stuck on a deprecated engine, we want to upgrade our Okta Classic engine to Okta Identity engine.

What you need to know

Plan document: https://docs.google.com/document/d/1DKrBuRR_VwEvBoIBgkZt5V52X0gHeLiZPEFIamSuwgs/edit#heading=h.t7m2dyannnnn

Acceptance criteria

Before May 20:

[x] (Joseph) Schedule the upgrade on Staging (OktaPreview) for May 20 at 12pm EST

On May 20:

[ ] (Chris) to inform stakeholders of the upgrade via Slack
[ ] (Joseph) Update email templates’ usage of fromURI
[ ] (Audrey, Joseph) Verify login/self-service scenarios
- [ ] Login
- [ ] Lock-out
- [ ] Reset Password
- [ ] MFA Factors
- [ ] New account first login setup
[ ] (Joseph) Verify frontend -> API communication works
[ ] (Victor) Verify backend CLI -> API communication works