Closed Tratcher closed 7 years ago
I guess I could ILMerge the dependencies to get rid of the version conflict while you guys are working on that.
That's problematic as they are exposed as public API
@chrisdrobison current POR is for an April refresh of M.IM.Protocols.WsFederation. Currently this topic branch is used to piece it together. https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/tree/WsFed
@brentschmaltz I literally just ran into that right before you posted. Looking forward to that .
This is a blocking issue for us too. We need to be able to use WS-Fed as our ADFS server is running on 2012 r2 and cannot be upgraded without causing widespread issues.
@DaleMckeown we committed an early beta to https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet so progress is being made in this area.
@Eilon This needs to be assigned in our weekly triage meeting.
We managed to dump WS-Fed and implement oAuth 2 instead.
@DaleMckeown Are you using ADFS3? If so, could you provide some samples? I'm porting MVC5 apps to .net core and having issues with ADFS integration.
@abezulski Yeah, we are using Oauth2 with ADFS3.0.
Can't give you a working example unfortunately, but me and @lilpug followed this post on carbon60: http://www.carbon60.com/blog/using-adfs-3-0-with-mvc-6-asp-net-5
Took us a while to modify the source code accordingly, but we go there in the end. David documented the changes made to get it working in a comment on the above blog post.
has anyone known any information about using adfs 2.0 in core2.0 ?
@YaoNiGu It's not yet available. We've just started the work.
We need to access a legacy SOAP service that authenticates with WS-Security (WSS) from a .NET Core app. We are looking for WSFed support also. I work in Government IT. .NET Core and Azure have much promise here, but we very often need to access legacy datasources.
Do you have an ETA on when this will this will be addressed.
@ashgadala The work has started. I expect we'll have something in preview before the end of the year.
@danroth27 Wonderful. Thank you so much for the update.
The eager can start tracking the work in this branch: https://github.com/aspnet/security/tree/tratcher/wsfed.
The plan is to start by releasing a 2.0.0 compatible preview package off cycle from the normal ASP.NET Core milestones (e.g. ASAP). We'll let you know when something is available on myget.org.
Reminder - Apply this change when moving to 2.1: https://github.com/aspnet/Security/issues/1188
@chrisdrobison - any updates on https://github.com/chrisdrobison/aspnetcore-wsfed - working with asp.net cpre 2 ?
An official preview is now available. See: https://github.com/aspnet/Security/issues/1473
Closing because the bulk of the work is done and in the public preview. We'll track any additional features and bugs as separate issues.
Depends on System.IdentityModel.Tokens.Jwt and Microsoft.IdentityModel.Protocol.Extensions.