Could not load RemoteAuthenticationOptions

[ravikumarsureshbabu]

Hello,
I am using wsfed nugget version 1.1.0 for ASP net core 2 application. It compiles succusfully but on run, it fails with following exception.

System.TypeLoadException occurred
HResult=0x80131522
Message=Could not load type 'Microsoft.AspNetCore.Builder.RemoteAuthenticationOptions' from assembly 'Microsoft.AspNetCore.Authentication, Version=2.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.

Does wsfed work for asp core 2 ? or Am I missing anything ?

[chrisdrobison]

This library is only built for ASP.NET Core 1.1.

…

On Fri, Sep 8, 2017 at 1:25 PM ravikumarsureshbabu ***@***.***> wrote: Hello, I am using wsfed nugget version 1.1.0 for ASP net core 2 application. It compiles succusfully but on run, it fails with following exception. System.TypeLoadException occurred HResult=0x80131522 Message=Could not load type 'Microsoft.AspNetCore.Builder.RemoteAuthenticationOptions' from assembly 'Microsoft.AspNetCore.Authentication, Version=2.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. Does wsfed work for asp core 2 ? or Am I missing anything ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#20>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABu24T3PsNuwoYNlMZbl6ynqGQ0u293Mks5sgZS7gaJpZM4PRl_W> .

[ravikumarsureshbabu]

Thanks for responding Chris. I am trying to use the code thats in the pull request by @michaeljfarr. Do you think using those code changes should be fine for asp net core 2 ? I have problems with getting the prompt for authentication with those changes.

[chrisdrobison]

That branch is a total experiment. You'd probably be better off waiting for the official implementation or just sticking with 1.1.

…

On Fri, Sep 8, 2017 at 8:28 PM ravikumarsureshbabu ***@***.***> wrote: Thanks for responding Chris. I am trying to use the code thats in the pull request by @michaeljfarr <https://github.com/michaeljfarr>. Do you think using those code changes should be fine for asp net core 2 ? I have problems with getting the prompt for authentication with those changes. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#20 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABu24XvTyOqAJ-21Spaecsqs5twocIpsks5sgffogaJpZM4PRl_W> .

[michaeljfarr]

Ravi, we are waiting on the next release from https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet to get things to the next stage. We have been waiting for a while, check out this thread: AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#595

Essentially, both our implementations are a bit of an experiment because the WsFederationMessage library introduces a versioning conflict that makes it unworkable in many situations. Hopefully, that library (mentioned above) will be released soon and target netstandard2.0. I haven't checked see if they are actually implementing the RemoteAuthenticationHandler though ...

The other big implementation issue on my branch is that I'm not maintaining those extension points (the "events"). If you don't mind the fact that the extension points are totally untested, I wont mind helping you to get up and running with aspnet core 2. As Chris already pointed out though, my branch is a super short term stop gap solution which you dont want to release anything critical on. The only point of difference I would make is that there are many fundamental changes to auth[n/z] in between net core 1 and 2 - so there is a chance that you'd benefit from an aspnet core 2 solution.

[michaeljfarr]

There is now a pre-release for Microsoft.AspNetCore.Authentication.WsFederation which is seems good. I had to pick the nightly builds of Microsoft.IdentityModel.Protocols.WsFederation Microsoft.IdentityModel.Tokens as described here AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#739 (comment)

The announcement is here: aspnet/Security#1473