Is there any dotnet core version of DocuSign.eSign Nuget package? or even source code I can fork?
DocuSign.eSign Nuget pacakge
Source code for C# client
There isn't any officially provided by DocuSign or alternatives that I'm aware of.
You could generate your own library with Swagger CodeGen and the DocuSign OpenAPI Specifications Swagger JSON
There is an unofficial fork of the C# SDK for .NET Core. Check the issues for the DocuSign C# SDK for a link.
Also, I'm looking to conduct 30 minute interviews with developers who are using DocuSign or considering to do so to get their opinions on how I can improve the developer products. Contact me via larry.kluger.docusign#gmail.com if you'd like more info.
After trying out both suggested solutions, it turns out that .net core SDK does not support the JWT Oauth workflow and it only support what's called legacy authentication method.
So, If you are trying to use JWT authentication using dotnet core SDK, you cannot
Related
I'm beginning the R&D (and scoping requirements) to implement an OAUTH2 Authorization Server, and our existing framework is ASP.NET (version 4.6.1 +). Is there an existing well-exercised SDK for this? I see that the oauth.net folks are still pointing .NET developers to the NuGet package(s) DotNetOpenAuth, but it looks like the relevant packages there have not been touched since 2013. Is that just because they are really stable and hence really solid? Or has the world moved on and I should be looking elsewhere for building blocks for an OAUTH2 server implementation?
Advice very welcome!
I did not manage to find in the documentation Microsoft Teams extension samples that use .NET Core. Every sample I found in GitHub included those of Build 2019 are in .NET Framework. I was expected to see everything in .NET Core, especially for something like Microsoft Teams which is recent and moving fast.
So that makes me wonder if .NET Core is supported for building Microsoft Teams extension.
.NET Core was not supported for bots until Bot Framework SDK v4. It wasn't supported for Bot Framework 3.x. All of our samples that use bots, with one exception, still support Bot Framework 3.x, and we expect to support both 3.x and 4.x indefinitely: in part because there's no good way to migrate from 3.x to 4.x.
The exception is our sample app for our Bot Framework 4.x SDK, which is currently in beta.
Over time we expect to focus more on .NET Core as we add Bot Framework SDK 4.x support to more of our samples.
Is there any plan to support .NET Core in the near future? I mean, without refactoring my bot code. There are still components not compatible with it.
Yes, it is planned and in the works. You can follow the topic on this related GitHub issue: [Feature Request] Porting to .NET core #572
Update 2017-10-26:
Bot Framework team is working on a complete rewrite of BotBuilder SDK (v4) which will be fully compatible with .NET Core.
Update 2017-12-14
Bot Builder v3 - New Bot Connector support for ASP.NET Core 2.0 and 1.1 has been released on NuGet!
We’ve released two new nuget packages for the Microsoft Bot Connector to support .NET Core 2.0:
Microsoft.Bot.Connector.AspNetCore.1.1.3.2.nupkg
Microsoft.Bot.Connector.AspNetCore.2.0.0.3.nupkg
The above packages each target ASPNetCore 1.x and ASPNetCore 2.x respectively, and provision authentication for your bot. They must also use Microsoft.Bot.Connector.3.12.2.4 or higher.
I am migrating an ASP.NET application to be on ASP.NET Core, but have met a problem of Ws-Federation authentication: there is no [Ws-Federation] (https://www.nuget.org/packages?q=Microsoft.Owin.Security.WsFederation) OWIN middleware available in ASP.NET Core platform.
But I noticed all authentication middleware for ASP.NET Core are now under Microsoft.AspNetCore.Authentication namespace, so I searched all packages from nuget.org and found most of the authentication packages are there, but unfortunately only the Microsoft.AspNetCore.Authentication.WsFederation is missing.
So, I would like to know, if the package is missing because it is not implemented yet or any other reason? Alternatively, is there existing ASP.NET Core based authentication middleware for Ws-Federation?
It's not implemented yet, mainly because .NET Core doesn't have the encrypted XML and XML dsig classes needed.
See https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/500
I've ported the Katana middleware over to ASP.NET Core. It has a hard dependency on the full .NET Framework since that is the only place the required libraries exist right now.
https://github.com/chrisdrobison/aspnetcore-wsfed
It appears .NET Core 2.1 WS Federation package is now available. Microsoft.AspNetCore.Authentication.WsFederation.
More information found at the following link:
https://learn.microsoft.com/en-us/aspnet/core/security/authentication/ws-federation?view=aspnetcore-2.1
I had a ServiceAccount hookup in my .NET Core RC1 app that worked fine. However now, "ServiceAccountCredential" doesn't exist in "Google.APIs.Auth.OAuth2" anymore. The whole library seems to be missing a ton of classes in the RTM version of Core.
Here are the related packages in my project.json
"Google.Apis.Core": "1.14.0",
"Google.Apis.Auth": "1.14.0",
"Google.Apis.Oauth2.v2": "1.14.0.540"
I even tried using the RC1 packages, but I keep getting the same thing. Is it simply because Google Auth isn't fully supported in Core yet?
The Google API's indeed do not fully support .NET Core yet: https://github.com/google/google-api-dotnet-client/issues/695.
In fact the ServiceAccountCredential is problematic (as I mentioned here) since it calls Windows-specific API's to parse the certificate. It has to be implemented cross-platform first to fully support .NET Core (.NET Standard actually).