Authentication

I used the Application integration key as the userId and called the ApiClient#requestJWTUserToken method. The returned tokenType was Application. What is the function of this token? Is there any documentation to explain? 

I am having no issues with the development environment; however, in production when I call the apiClient.requestJWTUserToken I’m getting back an error message.  “java.net.UnknownHostException: https”CODE    OAuthToken getToken(String apiClientUrl, String oAuthPath,             String clientId, String userId,             ArrayList<String> scopes, String keyValue) throws IllegalArgumentException, ApiException, IOException {        ApiClient apiClient =this.getApiClient(apiClientUrl, oAuthPath);        return apiClient.requestJWTUserToken(clientId, userId, scopes, keyValue.getBytes(), 3600);    }In dev the apiClient is using apiClientUrl = https://demo.docusign.net/restapithe oAuthPath value is https://account-d.do

Hi there,I’m getting the following error when requesting an access token from the authorization code previously generated by Docusign:{ "error": "invalid_grant"}I’ve followed all steps in https://developers.docusign.com/platform/auth/public-authcode-get-token/. I can easily get an authorization code, but when using it to request an access token I get above error. This is the request I do:POST in https://account-d.docusign.com/oauth/token with:code=<code returned as query param in the redirect_uri>grant_type=authorization_codeclient_id=<my integration key in development environment>code_verifier=<my original

I want to create a PKS/P12 certificate file from the RSA key pair for JWT.  Have tried open SSL command openssl.exe pkcs12 -export -out docusign.pfx -inkey docusign.key -in docusign.crtWith the inputs as the Private and Public key contents, but getting ‘unable to load certificates’  

I am currently integrating DocuSign with Oracle Integration (OIC). At present, I am using the following REST API to generate a bearer token:<BASE_URL>/oauth/token?grant_type=refresh_token&client_id=[client_id]&client_secret=[client_secret]&refresh_token=[refresh_token] This works fine as long as my refresh token is valid. However, when the refresh token itself expires, I currently use Postman to manually log in to my DocuSign account, provide consent, and generate a new refresh token.This approach is not ideal since it introduces manual intervention and breaks the automation.My Questions: What is the best way to avoid this manual Postman step? Is there a way to fully automate the token generation process in Oracle Integration so that I don’t have to worry about refresh token expiry? Should I switch to the JWT Grant flow for this type of server-to-server integratio

Hello,         I am developing an integration from Workday to DocuSign to pull the completed documents into Workday. I am getting following error when trying to authenticate to the endpoint - https://account-d.docusign.com/oauth/token to get the access tokenError code : badrequestResponse :{"error":"invalid_grant","error_description":"unsupported_grant_type"}I have the following Grant type which works fine in Postman. In addition to grant type, assertion key is generated which is passed along with grant type in Workdayassertion=@{props['jwt.assertion']}&grant_type=urn:ietf:params:oauth:grant-type:jwt-bearerPostman: 

I was using  https://account-d.docusign.com/oauth/token earlier and it was working fine. But now it stopped working. Getting the error  {   "error": "invalid_grant",   "error_description": "unauthorized_client" } . Can you please check and letm e know what could be the issue ?   

Hello,can someone help me to solve my Authentication problem. This is my code:// 1) Copia qui la tua Integration Key da Apps & Keysconst string IntegrationKey = "TUO-CLIENT-ID-GUID";// 2) Copia qui il tuo User ID (GUID) da My Account Informationconst string UserId = "TUO-USER-ID-GUID";// 3) Il PEM privato che hai scaricato da Service Integrationconst string PrivateKeyPath = "docusign_private_key.pem";// 4) L’host OAuth per democonst string OAuthHost = "account-d.docusign.com";// 5) L’URL base delle REST APIconst string BasePath = "https://demo.docusign.net/restapi";            var apiClient = new ApiClient(BasePath);            apiClient.SetOAuthBasePath(OAuthHost);            //byte[] privateKeyBytes = await File.ReadAllBytesAsync(PrivateKeyPath);            byte[] privateKeyBytes = Encoding.UTF8.GetBytes(privateKeyPem);//            var scopes = new[] { OAuth.Scope

Docusign account URL is account-specificAccording to https://developers.docusign.com/platform/api-endpoint-base-paths/, the {server} value (which determines the base URL for several Docusign APIs) is specific to a Docusign account:The Account Base URI section of the Apps and Keys page. This is confirmed by the structure of the /oauth/userinfo response, where the base URL can vary per account. For example:{ "sub": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "name": "First Last", "given_name": "First", "family_name": "Last", "created": "2015-08-

Hi!I’m trying to make API calls according to this how-to articlehttps://developers.docusign.com/platform/auth/authcode/confidential-authcode-get-token/But I’m stuck on “Step 3. Get your user's base URI” - the https://account-d.docusign.com/oauth/userinfo url always response with:{ "error": "internal_server_error", "reference_id": "d63dceae-72c6-4d27-9218-3b0fd58b2c30"}Authorization header is added as described in the docs -Bearer somelongCode......ProvidedIDK why it’s happening because I’m able to get Docusign access token from step 2 - that’s means that credentials set

Hello,I am trying to create a module in Make.com that checks if an envelope has been completed. This works for a while, but eventually, I receive an error message. I have a business plan with DocuSign. I have tried several solutions in both DocuSign and Make.com to resolve the issue, but so far without success.I believe the access token might only be valid for a limited time, and I’m looking for a way to either extend the access token’s validity or use a refresh token so that the system doesn’t keep failing as it does now.Has anyone encountered this issue and can offer guidance on how to solve it?Thank you in advance for your help!

Hello, While doing user testing for a client I came across a bug on the docusign platform, specifically in the Firefox browser when the 1Password extension is enabled. The password manager seems to be blocking users from fully completing their account set up with Docusign.session transaction ID b055adb1-64a6-4592-95f6-868a8f9b8d8f and the steps to reproduce this error.Steps in Firefox browser (regular or private browsing, with browser cache fully cleared): Docusign account activation by following the generated link in email inbox Set password for Docusign Account → when the login button is clicked, 1pass redirects the user to the Application error message rather than the successful Docusign login page. This process works in Chrome with 1password extension installedAny advice on how to get around this bug (without disabling the extension) would be greatly appreciated.

JWT GrantI am new to Docusing and was going through the documentation. I stumbled upon the Authorization Grant of the Platform 101 docs, and read the above excerpt. Can anyone clarify what does this mean If you use a single login for all users in your integration, you should use JWT Grant.  Using single login for all of the integration users mean what? Does that all follow the same login/signup method or the same credentials?

An Ruby on Rails application that I support is failing to send an envelope after the login/consent-grant step in the flow diagram.  I receive a response to my callback URL with a ‘code’ parameter set:

Hello I am trying to make a soap call through postman but I get an error that my username or password is incorrect. For username I use the email I have on Docusign and for the password the app password I created from the settings. Is this combination correct?XML body <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ds="http://www.docusign.net/API/3.0">   <soapenv:Header>      <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">         <wsse:UsernameToken>            <wsse:Username>myEmail</wsse:Username>            <wsse:Password>myPassword</wsse:Password>         </wsse:UsernameToken>      </wsse:Security>   </soapenv:Header>   <soapenv:Body>      <ds:RequestEnvelope>         <ds:EnvelopeI

Getting Socket Exception while connecting the Production base path. It is running successfully with demo base path.We have followed the same set of procedure for creating RSA key and consent requirement completion.We are not sure, why it is getting Socket Connection reset exception and in detail exception shows “javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake”Could any one please advise?

Is it only the Authentication that will be end of life? can we still use the SDK from before and just change the authentication to 2.0 OAuth?I wanna know cuz were still using the v2.1, will this still work?

Hello, In power platform I get the error create and authorize OAuth connection failed when I try tor deploy my app. What can be possibly wrong. It happens after I input my credentials correctly.  

In my C# code, when I try to create a Envelop got this errror,DocuSign.eSign.Client.ApiException: 'Error calling CreateEnvelope: {  "errorCode": "USER_AUTHENTICATION_FAILED",  "message": "One or both of Username and Password are invalid."}' Code...ApiClient apiClient = new ApiClient("https://demo.docusign.net/restapi");Configuration.Default.ApiClient = apiClient;//Verify Account Detailsstring accountId = loginApi(credential.UserName, credential.Password); -- account verification working fine here// |EnvelopesApi| contains methods related to creating and sending Envelopes (aka signature requests)EnvelopesApi envelopesApi = new EnvelopesApi();EnvelopeSummary envelopeSummary = envelopesApi.CreateEnvelope(accountId, envDef); --here i got the error    

Hi,I have 1 app which is created by a user whom left the organisation and now the problem I’m facing is the app doesn’t work with my GUID (User Id) it’s asking for old GUID (user id) who created the app.Is there any way we can manage this situation. shift the app to mine guid? 

Hello Everyone,I am getting this errorjava.lang.RuntimeException: java.lang.ClassNotFoundException: com.sun.ws.rs.ext.RuntimeDelegateImplwhen i try to executeOAuth.OAuthToken token =apiClient.requestJWTUserToken(clientId,userId,scopes,rsaPrivateKey,expiresIn);please give solution so that i can proceed withe the integration.Thanks in Advance.

Hello members,I'm encountering an issue while generating an access token using the JWT flow in PowerShell. Initially, I thought it might be a simple fix, but I've been troubleshooting for several hours without identifying the root cause. Here's the situation:I'm using a PowerShell script to generate a JWT assertion and then use that assertion to retrieve a temporary access token. Unfortunately, my request is failing. For comparison, I generated a JWT using JWT.io with the same private and public keys, and it successfully retrieved an access token. I've verified that the structure and payload of both tokens appear similar(Check below, same iss and sub) Working Failing

Hi, I am new to Docusign and facing an issue with access token being generated. The previous developer had integrated Appian with Docusign to send envelopes and the integration was working successfully till some time ago. Strangely, the integration is working well in both TEST and PROD. environments but failing in DEV. I am getting the error as “invalid grant”. The code and the keys are the same across all three environments except for the userId which is environment specific. I am using an Appian function to return the JWT token. Can anyone advice how to resolve this issue? TIA createdocusignrsajwttoken(  /*externalSystemKey:*/ cons!DSC_SCS_KEY_DOCUSING_RSA_PRIVATE_KEY,  /*iss:*/ cons!DSC_INTEGRATION_KEY,  /*alg:*/ cons!DSC_ENCRYPTION_TYPE_RS256,  /*typ:*/ cons!DSC_HEADER_TYPE_JWT,  /*aud:*/ cons!DSC_AUTH_AUD_URI,  /*scope:*/ joinarray({cons!DSC_SCOPE_SIGNATURE,cons!DSC_SCOPE_IMPERSONATION},cons!DSC_REQUEST_SCOPE_SEPARATOR),

Not getting consent page for Authorization Code Grant sample, trying with console sample java application. getting com.docusign.click.client.ApiException: Error while requesting server, received a non successful HTTP code 400 with response Body: '{"error":"consent_required"}'

I represent an ERP from which my customers (Business) will emit signable documents.Currently, if my customer requires a Docusign integration, we ask them to create an appdemo account so that we (, logging in with their credentials, ) can create and configure the App & Key credentials, security settings, etc. Then, when the tests are finished, they have to provide another (this time, paid) account so we can link it with their previous development account.My intention is to create the App & Keys from my Docusign enterprise account for each of these customers whenever they require a Docusign integration. Then, when I finish the mandated 20 integrated tests, I would send them the OAuth link so they can login and authorize using their subscribed account.By doing that, I intend to keep all integration keys my ERP uses in a single, managed, account.Is there an issue here? Should I not be doing that? Is this behavior expected? And if not, what are the alt