From 11af2e1b6544f64bdcd5b55d4b632dd58f906e67 Mon Sep 17 00:00:00 2001 From: James Hochadel Date: Tue, 23 Jul 2024 14:23:49 -0400 Subject: [PATCH] Update entity IDs to drop spurious protocol Our entity ID does not actually include a protocol (https://). In a recent IDP integration, we discovered that including the protocol can cause an error due to the audience restriction not matching the actual audience (the entity ID). It appears some IDPs remove the protocol automatically and some do not. In any case, the correct value is the login hostname with no protocol. --- _docs/orgs-spaces/sso.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_docs/orgs-spaces/sso.md b/_docs/orgs-spaces/sso.md index f023a083f..b6f6803c2 100644 --- a/_docs/orgs-spaces/sso.md +++ b/_docs/orgs-spaces/sso.md @@ -72,7 +72,7 @@ This is the environment where we test the configuration first. It matches our pr #### Entity ID -- +- `login.fr-stage.cloud.gov` #### OIDC Configuration @@ -90,7 +90,7 @@ The same configuration as our staging environment, just with production hostname #### Entity ID -- +- `login.fr.cloud.gov` #### OIDC Configuration