docusign-csharp-client | Official DocuSign C # Client Library | REST library

by docusign C# Version: v5.3.1-rc License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | docusign-csharp-client Summary

docusign-csharp-client is a C# library typically used in Web Services, REST applications. docusign-csharp-client has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

The Official DocuSign C# Client Library used to interact with the eSignature REST API. Send, sign, and approve documents using this client.

Support

Quality

Security

License

Reuse

Support

docusign-csharp-client has a low active ecosystem.

It has 93 star(s) with 139 fork(s). There are 35 watchers for this library.

It had no major release in the last 12 months.

There are 16 open issues and 183 have been closed. On average issues are closed in 89 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of docusign-csharp-client is v5.3.1-rc

Quality

docusign-csharp-client has 0 bugs and 0 code smells.

Security

docusign-csharp-client has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

docusign-csharp-client code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

docusign-csharp-client is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

docusign-csharp-client releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of docusign-csharp-client

Get all kandi verified functions for this library.

docusign-csharp-client Key Features

No Key Features are available at this moment for docusign-csharp-client.

docusign-csharp-client Examples and Code Snippets

No Code Snippets are available at this moment for docusign-csharp-client.

Community Discussions

Trending Discussions on docusign-csharp-client

While getting consent, I'm prompted to login to my developer account (but can I skip this?)

QUESTION

While getting consent, I'm prompted to login to my developer account (but can I skip this?)

Asked 2020-May-03 at 16:28

I have been working on connecting to the DocuSign API via a Blazor web app. For the most part, I have things working, except for the consent piece.

For context, my current build is mostly referencing https://github.com/docusign/docusign-csharp-client as the source, and I've modified what I needed from there. I've included code examples below. Additionally, I would like to say that I have tried just about every c# authorization flow DocuSign has documented, and in every case, it's also the consent piece where I run into issues.

Now, onto the specific issue: when I try to authorize consent (see code immediately below) with the returned Uri, I am prompted to login to DocuSign with my developer account. This is baffling to me, as I can't find any mention in their documentation that this is supposed to happen. From what I can tell, the user should be prompted to "Accept" or "Decline" the consent, but that is all. I can only assume I'm mistaken in my understanding of what's supposed to happen.

...

ANSWER

Answered 2020-May-02 at 02:16

Consent for only required once per app/integration.

Let's answer your questions:

Am I understanding the flow correctly? Yup, you do.
Why do I have to sign in when attempting to get consent? Well, how would DocuSign know who is consenting if they didn't sign-in? the consent is tied to your individual user account and every user has to consent individually.
Is that expected behavior? yup, it is.
If it is expected behavior, can I skip that (without pissing off DocuSign lawyers)? not sure about the lawyers part, but you cannot skip it. It is only required once. Once a user gives consent to an app, and unless they explicitly revoke it later, they do not need to do this again, ever.

To summarize:

Consent for only required once per app/integration.

Source https://stackoverflow.com/questions/61552980

Community Discussions, Code Snippets contain sources that include Stack Exchange Network