MicrosoftDocs
Update article for ADFS SAML IdP configurations in Azure B2C
The sample ClaimsProvider snippet should include <Item Key="XmlSignatureAlgorithm">Sha256</Item> in the TechnicalProfile's Metadata element. This is because when the ADFS relying party trust configurations are listed, in step 12 it's suggested to use sha256 for signing but B2C defaults to sha1.
Also the <Item Key="WantsEncryptedAssertions">false</Item> metadata should be omitted as it default to false - unless, there's a specific reason to explicitly set it to false, which is not mentioned in the article.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 592d4c02-12f0-c2ac-c2ea-f454fe4bb148
- Version Independent ID: 52333b29-3f21-6a72-a59c-6f59a72b9ecd
- Content: Add AD FS as a SAML identity provider by using custom policies - Azure AD B2C
- Content Source: articles/active-directory-b2c/identity-provider-adfs-saml.md
- Service: active-directory
- Sub-service: b2c
- GitHub Login: @garrodonnell
- Microsoft Alias: godonnell
@angelfourth Thanks for your feedback! We will investigate and update as appropriate.
@garrodonnell Can you please check and add your comments on this doc update request as applicable.
@garrodonnell I'm going to assign this to the document author so they can take a look at it accordingly
We've added this issue to our documentation backlog work item for internal tracking and prioritization. We'll update this issue as documentation updates are published. Thanks again for your feedback. #please-close
