SQL Server

Docusign Refresh OAuth2 Access Token

See more DocuSign Examples

Demonstrates how to refresh a Docusign OAuth2 access token. The refresh does not require user interaction via a web browser. If an access token expires (typically with a 401 response code), a new access token can be automatically obtained by using the code in this example. SQL Server

--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

    --  This example requires the Chilkat API to have been previously unlocked.
    --  See Global Unlock Sample for sample code.

    --  It is assumed we previously obtained an OAuth2 access token.
    --  This example loads the JSON access token file 
    --  saved by this example: Get Docusign OAuth2 Access Token

    DECLARE @jsonToken int
    EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @jsonToken OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    EXEC sp_OAMethod @jsonToken, 'LoadFile', @success OUT, 'qa_data/tokens/docusign.json'
    IF @success <> 1
      BEGIN

        PRINT 'Failed to load docusign.json'
        EXEC @hr = sp_OADestroy @jsonToken
        RETURN
      END

    --  The access token JSON looks like this:

    --  {
    --    "access_token": "eyJ0eXA....YQyig",
    --    "token_type": "Bearer",
    --    "refresh_token": "eyJ0eXA....auE3eHKg",
    --    "expires_in": 28800
    --  }

    DECLARE @oauth2 int
    EXEC @hr = sp_OACreate 'Chilkat.OAuth2', @oauth2 OUT

    --  For the developer sandbox environment, the token endpoint is https://account-d.docusign.com/oauth/token
    --  For the production platform, the token endpoint is https://account.docusign.com/oauth/token
    EXEC sp_OASetProperty @oauth2, 'TokenEndpoint', 'https://account-d.docusign.com/oauth/token'

    --  Replace these with actual values.
    --  The client ID is also known as the "integration key" in Docusign.
    EXEC sp_OASetProperty @oauth2, 'ClientId', 'MY_DOCUSIGN_CLIENT_ID'
    --  This is your secret key for the authorization code grant.
    EXEC sp_OASetProperty @oauth2, 'ClientSecret', 'MY_DOCUSIGN_CLIENT_SECRET'

    --  Get the "refresh_token"
    EXEC sp_OAMethod @jsonToken, 'StringOf', @sTmp0 OUT, 'refresh_token'
    EXEC sp_OASetProperty @oauth2, 'RefreshToken', @sTmp0

    --  Send the HTTP POST to refresh the access token..
    EXEC sp_OAMethod @oauth2, 'RefreshAccessToken', @success OUT
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @oauth2, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @jsonToken
        EXEC @hr = sp_OADestroy @oauth2
        RETURN
      END


    EXEC sp_OAGetProperty @oauth2, 'AccessToken', @sTmp0 OUT
    PRINT 'New access token: ' + @sTmp0

    EXEC sp_OAGetProperty @oauth2, 'RefreshToken', @sTmp0 OUT
    PRINT 'New refresh token: ' + @sTmp0

    --  Update the JSON with the new tokens.
    EXEC sp_OAGetProperty @oauth2, 'AccessToken', @sTmp0 OUT
    EXEC sp_OAMethod @jsonToken, 'UpdateString', @success OUT, 'access_token', @sTmp0
    EXEC sp_OAGetProperty @oauth2, 'RefreshToken', @sTmp0 OUT
    EXEC sp_OAMethod @jsonToken, 'UpdateString', @success OUT, 'refresh_token', @sTmp0

    --  Save the new JSON access token response to a file.
    DECLARE @sbJson int
    EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbJson OUT

    EXEC sp_OASetProperty @jsonToken, 'EmitCompact', 0
    EXEC sp_OAMethod @jsonToken, 'EmitSb', @success OUT, @sbJson
    EXEC sp_OAMethod @sbJson, 'WriteFile', @success OUT, 'qa_data/tokens/docusign.json', 'utf-8', 0


    PRINT 'OAuth2 authorization granted!'

    EXEC sp_OAGetProperty @oauth2, 'AccessToken', @sTmp0 OUT
    PRINT 'New Access Token = ' + @sTmp0

    EXEC @hr = sp_OADestroy @jsonToken
    EXEC @hr = sp_OADestroy @oauth2
    EXEC @hr = sp_OADestroy @sbJson


END
GO