From 56351bf7a0092e86326dd0b6699822368e2559d1 Mon Sep 17 00:00:00 2001 From: tanalam2411 Date: Fri, 8 Dec 2023 20:14:04 +0530 Subject: [PATCH] updated vault --- content/tutorials/vault/enabling-multi-tenancy-vault.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/tutorials/vault/enabling-multi-tenancy-vault.md b/content/tutorials/vault/enabling-multi-tenancy-vault.md index 0379ed047..143d132f8 100644 --- a/content/tutorials/vault/enabling-multi-tenancy-vault.md +++ b/content/tutorials/vault/enabling-multi-tenancy-vault.md @@ -22,7 +22,7 @@ This requires a running `RHSSO(RedHat Single Sign On)` instance integrated with MTO integration with Vault and RHSSO provides a way for users to log in to Vault where they only have access to relevant tenant paths. -Once both integrations are set up with [IntegrationConfig CR](../../how-to-guides/integration-config.md), MTO links tenant users to specific client roles named after their tenant under Vault client in RHSSO. +Once both integrations are set up with [IntegrationConfig CR](../../how-to-guides/integration-config.md#rhsso-red-hat-single-sign-on), MTO links tenant users to specific client roles named after their tenant under Vault client in RHSSO. After that, MTO creates specific policies in Vault for its tenant users.