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
The ws-federation.md article contains a step-by-step Microsoft Entra ID setup subsection that duplicates identity-provider setup already owned by the authoritative Entra documentation. Per the epic goal, ASP.NET Core docs should point to the Microsoft Entra docs for provider setup rather than duplicating it.
Keep only the two ASP.NET Core–specific values the WS-Federation middleware needs:
MetadataAddress = the Federation Metadata Document URL
Wtrealm = the Application ID URI
Delete the four now-unused Aad*.png setup screenshots listed above from aspnetcore/security/authentication/ws-federation/_static/. Confirm they aren't referenced elsewhere in the repo before deleting.
Update the stale ms.date (currently 01/16/2019, L8) to the PR merge date.
Leave the Active Directory Federation Services (ADFS) section (L24–59) and all ASP.NET Core middleware/code content (L80+) intact.
Guardrail
Remove only the duplicated Entra setup content. Do not remove framework-specific configuration, the ADFS steps, or the middleware code examples.
Important
Do not delete, rename, or alter the sign-in illustration file, which exists on disk as AadSignIn.PNG (uppercase .PNG extension) and is referenced in markdown as ws-federation/_static/AadSignIn.png at L128. It's used in the "Log in with WS-Federation" section to show the sign-in redirect result and must be kept. Only the four setup screenshots from the L61–78 block are removed.
Note
The article's front matter includes ms.custom: sfi-image-nochange (L7). Removing images may make this flag obsolete—verify whether it should be adjusted as part of this change.
Definition of done (acceptance criteria)
The "### Microsoft Entra ID" subsection (L61–78) is replaced with a short intro + crosslink to the identity-platform quickstart.
Only MetadataAddress and Wtrealm values remain as ASP.NET Core–specific guidance.
The four Aad* setup PNGs are deleted and no longer referenced anywhere in the repo.
AadSignIn.PNG and all ADFS/Adfs* images remain untouched.
ms.date (L8) is updated.
The ADFS section and all middleware/code sample content are unchanged.
Article builds without broken links or missing-image warnings.
A PR is opened against main linking back to this issue.
Pattern to follow
Model this on the successful bridge-page approach used for azure-ad-b2c.md (#36921 → PR #36922).
Description
Published article: https://learn.microsoft.com/aspnet/core/security/authentication/ws-federation
Contributes to epic #36277
Summary
The
ws-federation.mdarticle contains a step-by-step Microsoft Entra ID setup subsection that duplicates identity-provider setup already owned by the authoritative Entra documentation. Per the epic goal, ASP.NET Core docs should point to the Microsoft Entra docs for provider setup rather than duplicating it.File
aspnetcore/security/authentication/ws-federation.mdProblem
Lines 61–78 are a step-by-step Entra ID portal walkthrough (app registration, endpoints blade, Expose an API) accompanied by four screenshots:
AadNewAppRegistration.png(referenced L65)AadCreateAppRegistration.png(referenced L70)AadFederationMetadataDocument.png(referenced L74)AadAppIdUri.png(referenced L78)This is genuine duplication of content maintained in the Entra identity platform docs.
Requested changes
MetadataAddress= the Federation Metadata Document URLWtrealm= the Application ID URIAad*.pngsetup screenshots listed above fromaspnetcore/security/authentication/ws-federation/_static/. Confirm they aren't referenced elsewhere in the repo before deleting.ms.date(currently01/16/2019, L8) to the PR merge date.Guardrail
Remove only the duplicated Entra setup content. Do not remove framework-specific configuration, the ADFS steps, or the middleware code examples.
Important
Do not delete, rename, or alter the sign-in illustration file, which exists on disk as
AadSignIn.PNG(uppercase.PNGextension) and is referenced in markdown asws-federation/_static/AadSignIn.pngat L128. It's used in the "Log in with WS-Federation" section to show the sign-in redirect result and must be kept. Only the four setup screenshots from the L61–78 block are removed.Note
The article's front matter includes
ms.custom: sfi-image-nochange(L7). Removing images may make this flag obsolete—verify whether it should be adjusted as part of this change.Definition of done (acceptance criteria)
MetadataAddressandWtrealmvalues remain as ASP.NET Core–specific guidance.Aad*setup PNGs are deleted and no longer referenced anywhere in the repo.AadSignIn.PNGand all ADFS/Adfs*images remain untouched.ms.date(L8) is updated.mainlinking back to this issue.Pattern to follow
Model this on the successful bridge-page approach used for
azure-ad-b2c.md(#36921 → PR #36922).Page URL
https://learn.microsoft.com/en-us/aspnet/core/security/authentication/ws-federation?view=aspnetcore-10.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/security/authentication/ws-federation.md
Document ID
d07c4058-452f-cdac-c59d-8f09e70a43f3
Platform Id
a517a7ba-0da6-5816-32fb-1e56c761eb4c
Article author
@chlowell
Metadata
Related Issues
Associated WorkItem - 626914