From 3279ff6024c71e58f8bbebdb0d5b433d57b18d7d Mon Sep 17 00:00:00 2001 From: Arvid Requate Date: Fri, 24 Nov 2023 18:36:27 +0100 Subject: [PATCH] Explain that identity federation is currently a testbed feature (#117) Signed-off-by: Arvid Requate --- dev-docs/operations/iam/identity-federation-in-scs.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/dev-docs/operations/iam/identity-federation-in-scs.md b/dev-docs/operations/iam/identity-federation-in-scs.md index 65e8755258..5fd7b1cc11 100644 --- a/dev-docs/operations/iam/identity-federation-in-scs.md +++ b/dev-docs/operations/iam/identity-federation-in-scs.md @@ -13,6 +13,9 @@ to achieve that goal. To simplify connecting the different parts of SCS to customer owned IAM solutions, SCS deploys Keycloak as central Identity Provider (IdP) service. +Currently this is deployed automatically only in the [osism/testbed](https://docs.scs.community/docs/iaas/guides/deploy-guide/examples/testbed/), +which provides [its own documentation for authentication with OIDC](https://docs.scs.community/docs/iaas/guides/deploy-guide/examples/testbed#authentication-with-oidc). + The following sections describe how this is done. ## 1. IaaS / OpenStack