Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Authenticate users with WS-Federation #9706

Closed
fabich opened this issue Nov 27, 2018 · 3 comments · Fixed by #18147
Closed

Update Authenticate users with WS-Federation #9706

fabich opened this issue Nov 27, 2018 · 3 comments · Fixed by #18147
Assignees
Labels
doc-bug Source - Docs.ms Docs Customer feedback via GitHub Issue
Projects
Milestone

Comments

@fabich
Copy link

fabich commented Nov 27, 2018

This article is no longer up to date.

@Rick-Anderson EDIT: 3.1K to 5K PV, 75% CSAT


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@dotnet-bot dotnet-bot added the Source - Docs.ms Docs Customer feedback via GitHub Issue label Nov 27, 2018
@Rick-Anderson Rick-Anderson added the Pri1 High priority, do before Pri2 and Pri3 label Nov 27, 2018
@Rick-Anderson Rick-Anderson added this to the Backlog milestone Nov 27, 2018
@Rick-Anderson
Copy link
Contributor

We'll try to get this updated.
@scottaddie - this is an advanced topic. I think we should remove all the screen shots so it's easier to keep up to date.

@Rick-Anderson Rick-Anderson changed the title Page no longer up to date Update Authenticate users with WS-Federation Jan 19, 2019
@Rick-Anderson Rick-Anderson added Pri2 Priority 2 and removed Pri1 High priority, do before Pri2 and Pri3 labels Jan 19, 2019
@Rick-Anderson
Copy link
Contributor

Moved to master issue: WS-Federation #16508

@Rick-Anderson Rick-Anderson self-assigned this May 5, 2020
@Rick-Anderson Rick-Anderson removed the Pri2 Priority 2 label May 5, 2020
@Rick-Anderson Rick-Anderson added this to To do in Next sprint via automation May 5, 2020
@Rick-Anderson
Copy link
Contributor

@Rick-Anderson ,

Hi, thanks for following up.

I was referring mostly to this introduction:

This tutorial demonstrates how to enable users to sign in with a WS-Federation authentication provider like Active Directory Federation Services (ADFS) or Azure Active Directory (AAD). It uses the ASP.NET Core 2.0 sample app described in Facebook, Google, and external provider authentication.

For ASP.NET Core 2.0 apps, WS-Federation support is provided by Microsoft.AspNetCore.Authentication.WsFederation. This component is ported from Microsoft.Owin.Security.WsFederation and shares many of that component's mechanics. However, the components differ in a couple of important ways.

If I'm mistaken, then my apologies.

I have a large website using ws-federation on .net 4.6.1 right now and I'm looking into upgrade paths to asp core 3.1. I can't find any actual end-to-end usage or implementation of it in any Microsoft sample. And most other usage is using owin still.

If you happen to know of something I might be missing that would be greatly appreciated! Thanks.

@Rick-Anderson Rick-Anderson reopened this May 5, 2020
@Rick-Anderson Rick-Anderson added this to To do in May 2020 via automation May 5, 2020
@Rick-Anderson Rick-Anderson removed this from To do in Next sprint May 5, 2020
May 2020 automation moved this from To do to Done May 5, 2020
@dotnet dotnet locked and limited conversation to collaborators May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
doc-bug Source - Docs.ms Docs Customer feedback via GitHub Issue
Projects
No open projects
May 2020
  
Done
Development

Successfully merging a pull request may close this issue.

4 participants