You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/faq.yml
+8-2Lines changed: 8 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ metadata:
9
9
ms.service: active-directory
10
10
ms.workload: identity
11
11
ms.topic: faq
12
-
ms.date: 02/09/2023
12
+
ms.date: 03/15/2023
13
13
ms.author: godonnell
14
14
ms.subservice: B2C
15
15
ms.custom: "b2c-support"
@@ -64,7 +64,13 @@ sections:
64
64
* Microsoft account: openid email profile
65
65
* Amazon: profile
66
66
* 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
+
68
74
- question: |
69
75
Does my application have to be run on Azure for it work with Azure AD B2C?
0 commit comments