70-332 · Question #3
You are implementing a claims-based authentication solution for a SharePoint farm in an Active Directory Domain Services domain. You install and configure Active Directory Federation Services (AD…
The correct answer is A. Configure AD FS with the web application as a relying party. C. Configure web applications to use claims-based authentication and AD FS as the trusted identity provider. E. Configure SharePoint to trust AD FS as an identity provider. Implementing SAML-based claims authentication with AD FS in SharePoint requires configuring AD FS to recognize SharePoint as a relying party, configuring web applications for claims-based authentication with AD FS as the trusted identity provider, and establishing trust between…
Question
Options
- AConfigure AD FS with the web application as a relying party.
- BConfigure web applications to use forms-based authentication and AD FS as the trusted identity provider.
- CConfigure web applications to use claims-based authentication and AD FS as the trusted identity provider.
- DConfigure web applications to use classic mode authentication and AD FS as the trusted identity provider.
- EConfigure SharePoint to trust AD FS as an identity provider.
How the community answered
(24 responses)- A79% (19)
- B13% (3)
- D8% (2)
Why each option
Implementing SAML-based claims authentication with AD FS in SharePoint requires configuring AD FS to recognize SharePoint as a relying party, configuring web applications for claims-based authentication with AD FS as the trusted identity provider, and establishing trust between SharePoint and AD FS.
AD FS must have the SharePoint web application registered as a relying party trust so it knows to issue security tokens for that application.
Forms-based authentication uses username and password forms and does not support SAML token exchange; SAML requires claims-based authentication mode, not FBA.
Each web application must be configured to use claims-based authentication mode and reference AD FS as the trusted identity provider, enabling it to accept SAML tokens.
Classic mode authentication uses Kerberos or NTLM and is incompatible with SAML-based claims; it does not support trusted identity providers like AD FS.
SharePoint must explicitly trust AD FS as an identity provider by adding its token-signing certificate as a trusted root authority and creating a SPTrustedIdentityTokenIssuer, completing the trust chain.
Concept tested: SharePoint SAML claims authentication with AD FS configuration
Source: https://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/implement-saml-based-authentication-in-sharepoint-server
Topics
Community Discussion
No community discussion yet for this question.