Skip to content

Commit 52dc907

Browse files
authored
Add an entry for ADFS issue
We got an incident for this issue.
1 parent 92d66c5 commit 52dc907

File tree

1 file changed

+8
-2
lines changed
  • articles/active-directory-b2c

1 file changed

+8
-2
lines changed

articles/active-directory-b2c/faq.yml

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ metadata:
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: faq
12-
ms.date: 02/09/2023
12+
ms.date: 03/15/2023
1313
ms.author: godonnell
1414
ms.subservice: B2C
1515
ms.custom: "b2c-support"
@@ -64,7 +64,13 @@ sections:
6464
* Microsoft account: openid email profile
6565
* Amazon: profile
6666
* LinkedIn: r_emailaddress, r_basicprofile
67-
67+
68+
- question: |
69+
I'm using ADFS as an identity provider in B2C. When I tried to initiate a log out request from B2C, ADFS throws the error "MSIS7084: SAML logout request and logout response messages must be signed when using SAML HTTP Redirect or HTTP POST binding." Why is B2C not signing the SAML logout request?
70+
answer: |
71+
On the ADFS server, run the following: `Set-AdfsProperties -SignedSamlRequestsRequired $true`
72+
This will force B2C to sign all requests to ADFS.
73+
6874
- question: |
6975
Does my application have to be run on Azure for it work with Azure AD B2C?
7076
answer: |

0 commit comments

Comments
 (0)