docusign-esign-csharp-client: ApiClient.RequestJWTUserToken doesn't fulfill ErrorContent of ApiException from server

It might be useful to have the ErrorContent to be fulfilled here. Especially, it’d be a handful for catching the consent_required in initial consent request or responding on revocation case. It looks like a simple change of the following code onto smth like below may do the work:

throw new ApiException(
                    (int)response.StatusCode,
                    string.Concat(
                        "Error while requesting server, received a non successful HTTP code ",
                        response.ResponseStatus,
                        " with response Body: '", 
                        response.Content, "'"),
                    response.Content);

Thanks

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 15 (5 by maintainers)

Most upvoted comments

Hi @yevgen-ponomarenko, we have resolved this with v3.1.3 release. Please have a look, feel free to close this issue. Thanks.

RajRele on Nov 29, 2018

For anyone else facing this issue (e.g. no error returned by the response):

DocuSign.eSign.Client.ApiException: 'Error while requesting server, received a non successful HTTP code Error with response Body: '

The issue/solution for me was malformed oauthBasePath. At first I was using https://account-d.docusign.com/oauth/auth then tried https://account-d.docusign.com then finally got it to work with just account-d.docusign.com

Hope this helps someone else!

ltickett on Dec 24, 2020

@SrinathJandhyala

Docusign doesn’t send clear errors when there is an issue with the request. In my case I was using https://account-d.docusign.com instead of account-d.docusign.com for the AuthServer value and it didn’t tell the issue.

while calling apiClient.RequestJWTUserToke

ZeeshanAdilButt on Jul 11, 2019

Excellent. Thank you for the update.

LarryKlugerDS on Dec 17, 2018