| Info | ||
|---|---|---|
| ||
This Delegating Authority to Trusted Third-Party Sources design document is in draft status and evolving as informed by the Ed-Fi community. Please use the Comments section below for any feedback into the design of single-sign on support for Ed-Fi Tools. |
...
Today, Admin App supports only forms-based authentication for using the application. This design proposes adding another method of delegating user-authentication to trusted 3rd party-sources via OpenID Connect, to provide single-sign on like experiences to users of Ed-Fi tools. If this design, implemented code and pattern is successful in Admin App, it will be considered for reuse in applications such as Data Import.
Below is a table of contents for topics into the Delegating Authority to Trusted Third-Party Sources design:
Table of Contents minLevel 2
...
On development environment all these details can be stored on Authentication section on appsettings.json file or can be set as user-secrets.
ex: dotnetuser-secrets set "Authentication:Google:Client_Id""sampleapp"
For production environment, it is recommended to store Client_Id and Client_Secret on environment variables.
...