SQL Server

Auth0 Server-to-Server Access Token (Client Credentials flow)

See more HTTP Examples

Demonstrates how to obtain an Auth0 access token using client credentials (client_id and client_secret).

This is just a matter of duplicating this CURL command:

curl --request POST
  --url 'https://chilkat.auth0.com/oauth/token' \
  --header 'content-type: application/json' \
  --data '{"grant_type":"client_credentials","client_id": "xxxx","client_secret": "xxxx","audience": "https://api.example.com/geocoding/v1/"}'

SQL Server

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

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

    -- We want to duplicate this curl command:
    -- 
    -- curl --request POST
    --   --url 'https://chilkat.auth0.com/oauth/token' \
    --   --header 'content-type: application/json' \
    --   --data '{"grant_type":"client_credentials","client_id": "my_client_id","client_secret": "my_client_secret","audience": "https://api.example.com/geocoding/v1/"}'

    -- Build the JSON body of the request.
    DECLARE @json int
    EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @json OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'grant_type', 'client_credentials'
    EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'client_id', 'AUTH0-CLIENT-ID'
    EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'client_secret', 'AUTH0-CLIENT-SECRET'
    EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'audience', 'https://api.example.com/geocoding/v1/'

    -- IMPORTANT: You would use your own url.  You would not use "chilkat.auth0.com".  
    -- Instead you would use "your_name.auth0.com"
    DECLARE @http int
    EXEC @hr = sp_OACreate 'Chilkat.Http', @http OUT

    DECLARE @resp int
    EXEC @hr = sp_OACreate 'Chilkat.HttpResponse', @resp OUT

    EXEC sp_OAMethod @http, 'HttpJson', @success OUT, 'POST', 'https://chilkat.auth0.com/oauth/token', @json, 'application/json', @resp
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @json
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @resp
        RETURN
      END

    -- A 200 response status code indicates success.  In the success case, the response body
    -- contains the JSON access token, such as: 
    -- {
    --   "access_token": "eyJz93a...k4laUWw",
    --   "token_type":"Bearer",
    --   "expires_in":86400
    -- }
    -- 


    EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
    PRINT 'response status code = ' + @iTmp0

    -- The repsonse is JSON if successful and also JSON for errors.
    DECLARE @jsonResp int
    EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @jsonResp OUT

    EXEC sp_OASetProperty @jsonResp, 'EmitCompact', 0
    EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
    EXEC sp_OAMethod @jsonResp, 'Load', @success OUT, @sTmp0

    EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
    IF @iTmp0 <> 200
      BEGIN
        -- The response body contains error information in JSON format.
        EXEC sp_OAMethod @jsonResp, 'Emit', @sTmp0 OUT
        PRINT @sTmp0

        -- An example of an error response:
        -- 		{
        -- 		  "error": "access_denied",
        -- 		  "error_description": "Client is not authorized to access \"https://api.example.com/geocoding/v1/\". You might probably want to create a \"client-grant\" associated to this API. See: https://auth0.com/docs/api/v2#!/Client_Grants/post_client_grants"
        -- 		}
        EXEC @hr = sp_OADestroy @json
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @resp
        EXEC @hr = sp_OADestroy @jsonResp
        RETURN
      END


    PRINT 'Success!'
    EXEC sp_OAMethod @jsonResp, 'Emit', @sTmp0 OUT
    PRINT @sTmp0

    -- A successful JSON response body looks like this:

    -- {
    --   "access_token": "eyJz93a...k4laUWw",
    --   "token_type":"Bearer",
    --   "expires_in":86400
    -- }

    EXEC @hr = sp_OADestroy @json
    EXEC @hr = sp_OADestroy @http
    EXEC @hr = sp_OADestroy @resp
    EXEC @hr = sp_OADestroy @jsonResp


END
GO