diff options
| author | mo khan <mo@mokhan.ca> | 2022-03-30 11:25:52 -0600 |
|---|---|---|
| committer | mo khan <mo@mokhan.ca> | 2022-03-30 11:25:52 -0600 |
| commit | 50a38c5f934cb161bdc1c315d077691f3a8f20fb (patch) | |
| tree | 0c6d8505f9197bc4b49c08b9db45d1143192d8cb | |
| parent | efeb39e24074423c77c5d75c02c9b1d0661775af (diff) | |
fix link to cloud-idp
| -rw-r--r-- | doc/authz/OAUTH.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/authz/OAUTH.md b/doc/authz/OAUTH.md index fc9d1c7..3c0de9e 100644 --- a/doc/authz/OAUTH.md +++ b/doc/authz/OAUTH.md @@ -18,7 +18,7 @@ the Terraform Cloud permissions. <!-- In this idea, how coupled is TFC to HCP at runtime? --> -In Terraform Cloud, (cloud-idp)[https://github.com/hashicorp/cloud-idp] will act +In Terraform Cloud, [cloud-idp][4] will act as the intermediary between Terraform and HCP. All Authz permissions (claims) for a given Principal (Resource Owner) will be included in a stateless OpenID Connect ID Token that can be used by the Terraform Cloud API (Resource Server) @@ -60,3 +60,4 @@ What do we need to do to understand this better? Is it feedback from others, is [1]: https://datatracker.ietf.org/doc/html/rfc7662#section-2 [2]: https://github.com/hashicorp/atlas/blob/c060b88f91aeca9cf30b7d890445a8701f7eba82/app/models/authentication_token.rb#L96-L112 [3]: https://github.com/hashicorp/atlas/tree/c060b88f91aeca9cf30b7d890445a8701f7eba82/app/policies +[4]: https://github.com/hashicorp/cloud-idp |