You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Depends on #2263, where we will learn more about what needs to be set up
We will probably need help from CDT DevSecOps on this.
The idea is to set up a tenant in the CDT Azure environment and create a registered application to represent the Benefits app. This registered application will have a client secret. The application ID and client secret are then used to configure Microsoft SSO for the Benefits app.
External users are then invited to have access to the tenant which gives them access to the registered application. Because of that relationship, they should be able to successfully authenticate into the Benefits admin with Microsoft SSO.
Acceptance criteria
There is a tenant set up in the production CDT Azure environment which allows us to invite external users to access the registered application for Benefits
Depends on #2263, where we will learn more about what needs to be set up
We will probably need help from CDT DevSecOps on this.
The idea is to set up a tenant in the CDT Azure environment and create a registered application to represent the Benefits app. This registered application will have a client secret. The application ID and client secret are then used to configure Microsoft SSO for the Benefits app.
External users are then invited to have access to the tenant which gives them access to the registered application. Because of that relationship, they should be able to successfully authenticate into the Benefits admin with Microsoft SSO.
Acceptance criteria
Additional context
Adding Microsoft credentials
The text was updated successfully, but these errors were encountered: