From e749e75be94c8c03030e115e4f6bc6149369960f Mon Sep 17 00:00:00 2001
From: Joe DeCock <josephdecock@gmail.com>
Date: Tue, 3 Oct 2023 09:42:55 -0500
Subject: [PATCH] Escape all usage of <iframe> tags

Without this, hugo doesn't render them!
---
 .../docs/content/reference/services/interaction_service.md  | 2 +-
 .../v6/docs/content/ui/logout/external_notification.md      | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/IdentityServer/v6/docs/content/reference/services/interaction_service.md b/IdentityServer/v6/docs/content/reference/services/interaction_service.md
index ee85b3fa..b6a9316b 100644
--- a/IdentityServer/v6/docs/content/reference/services/interaction_service.md
+++ b/IdentityServer/v6/docs/content/reference/services/interaction_service.md
@@ -170,7 +170,7 @@ The above methods return various models.
 
 * ***SignOutIFrameUrl***
 
-    The URL to render in an *<iframe>* on the logged out page to enable single sign-out.
+    The URL to render in an *\<iframe>* on the logged out page to enable single sign-out.
 
 * ***Parameters***
     
diff --git a/IdentityServer/v6/docs/content/ui/logout/external_notification.md b/IdentityServer/v6/docs/content/ui/logout/external_notification.md
index 1945b699..cfe9dbd4 100644
--- a/IdentityServer/v6/docs/content/ui/logout/external_notification.md
+++ b/IdentityServer/v6/docs/content/ui/logout/external_notification.md
@@ -7,8 +7,8 @@ Federated sign-out is the situation where a user has used an external identity p
 When the user signs out, it will be useful for IdentityServer to be notified so that it can sign the user out of IdentityServer and all of the applications that use IdentityServer.
 
 Not all external identity providers support federated sign-out, but those that do will provide a mechanism to notify clients that the user has signed out.
-This notification usually comes in the form of a request in an *<iframe>* from the external identity provider's "logged out" page.
-IdentityServer must then notify all of its clients (as discussed [here]({{< ref "../logout" >}})), also typically in the form of a request in an *<iframe>* from within the external identity provider's *<iframe>*.
+This notification usually comes in the form of a request in an *\<iframe>* from the external identity provider's "logged out" page.
+IdentityServer must then notify all of its clients (as discussed [here]({{< ref "../logout" >}})), also typically in the form of a request in an *\<iframe>* from within the external identity provider's *\<iframe>*.
 
 What makes federated sign-out a special case (when compared to a normal [logout]({{< ref "../logout" >}})) is that the federated sign-out request is not to the normal sign-out endpoint in IdentityServer.
 In fact, each external IdentityProvider will have a different endpoint into your IdentityServer host. 
@@ -19,7 +19,7 @@ which means we are missing the sign-out notifications to IdentityServer's client
 We must add code for each of these federated sign-out endpoints to render the necessary notifications to achieve federated sign-out.
 
 Fortunately IdentityServer already contains this code. 
-When requests come into IdentityServer and invoke the handlers for external authentication providers, IdentityServer detects if these are federated signout requests and if they are it will automatically render the same *<iframe>* as [described here for logout]({{< ref "../logout" >}}).
+When requests come into IdentityServer and invoke the handlers for external authentication providers, IdentityServer detects if these are federated signout requests and if they are it will automatically render the same *\<iframe>* as [described here for logout]({{< ref "../logout" >}}).
 
 
 In short, federated signout is automatically supported.