From b32d8dcef5e965028e3f8e9d44cd5e40edb2b147 Mon Sep 17 00:00:00 2001 From: Arvid Requate Date: Tue, 12 Dec 2023 11:31:25 +0100 Subject: [PATCH] Workaround for link checker not finding .md files --- docs/05-iam/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/05-iam/index.md b/docs/05-iam/index.md index c175a7ccbe..5d5e61f87b 100644 --- a/docs/05-iam/index.md +++ b/docs/05-iam/index.md @@ -38,7 +38,7 @@ The idea is that customer can create groups with specific names in their own IAM These shall be mapped to a claim `groups` to be included in the OIDC token. Via the Keystone [mapping](https://docs.openstack.org/keystone/latest/admin/federation/mapping_combinations.html) they shall be mapped to roles on OpenStack projects. -[The corresponding section for Developers](../../dev-docs/operations/iam/identity-federation-in-scs) may be interesting for more technical details. +[The corresponding section for Developers](https://docs.scs.community/dev-docs/operations/iam/identity-federation-in-scs) may be interesting for more technical details. Please be aware that currently there are still some technical challenges to be solved within the OpenStack Keystone mapping engine and the mapping rules to make this work seamlessly. @@ -47,7 +47,7 @@ seamlessly. Federation between separate deployments of SCS is possible via the IdP by means of OpenID Connect. -The section on [inter SCS federation setup](intra-SCS-federation-setup-description-for-osism-doc-operations) explains the required steps in some detail. +The section on [inter SCS federation setup](https://docs.scs.community/docs/iam/intra-SCS-federation-setup-description-for-osism-doc-operations) explains the required steps in some detail. ### Prerequisites and Requirements