Develop BE documentation for Okta

[chris-kuryak]

Problem statement

Now that we have identified what documentation we need, we now need to create that documentation per the plan.

What you need to know

• Okta Documentation Plan - #13621

Acceptance criteria

Create the following documentation In Github:

• [ ] How is Okta integrated into our back-end (TBD by Platform)
  • [ ] Environment variables that need to be set to point correctly to our BE
  • [ ] If giving us an Okta token is a valid way to authenticate, then we need to ensure there is documentation in the Prime-router area explaining how Okta is an OAuth2 and how they can communicate using that with examples
• [ ] How Okta integrates with Azure and DevOps and the necessary elements needed from Okta to make it work properly (TBD by DevOps)
  • [ ] Mapping names from Okta variables to DevOps variables (may be covered by environment variables documentation above)
• [ ] Needs succession plan for admin ownership

[devopsmatt]

@sarah-g-parker - where do we keep the private documentation of Okta? Is it somewhere in SharePoint?

[megreed1]

Removed "DevSecOps" from title as DevSecOps does not have Okta access.

[megreed1]

9/23- Carrying over to Sprint 130 due to other priorities

[megreed1]

12/1- DevSecOps does not have anything to do with this ticket, we can update the AC