(SQL Server) Twitter PIN-Based Authorization (Step 1)

Demonstrates the 1st step in Twitter PIN-based authorization using OAuth. The purpose of this step is to obtain a temporary request token that will be traded for an access token + secret in the final step. Once the access token + secret is obtained, the application can access the Twitter account in whatever ways it was authorized.

Note: This example requires Chilkat v11.0.0 or greater.

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

-- 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 requires the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

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

    EXEC sp_OASetProperty @http, 'OAuth1', 1
    EXEC sp_OASetProperty @http, 'OAuthConsumerKey', 'my-consumer-key'
    EXEC sp_OASetProperty @http, 'OAuthConsumerSecret', 'my-consumer-secret'

    DECLARE @req int
    EXEC @hr = sp_OACreate 'Chilkat.HttpRequest', @req OUT

    EXEC sp_OASetProperty @req, 'HttpVerb', 'POST'
    EXEC sp_OASetProperty @req, 'ContentType', 'application/x-www-form-urlencoded'

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

    EXEC sp_OAMethod @http, 'HttpReq', @success OUT, 'https://api.twitter.com/oauth/request_token', @req, @resp
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @req
        EXEC @hr = sp_OADestroy @resp
        RETURN
      END

    EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
    IF @iTmp0 = 200
      BEGIN

        DECLARE @oauthToken nvarchar(4000)
        EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
        EXEC sp_OAMethod @resp, 'UrlEncParamValue', @oauthToken OUT, @sTmp0, 'oauth_token'

        PRINT 'OAuth temporary request token = ' + @oauthToken

        DECLARE @oauthTokenSecret nvarchar(4000)
        EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
        EXEC sp_OAMethod @resp, 'UrlEncParamValue', @oauthTokenSecret OUT, @sTmp0, 'oauth_token_secret'

        PRINT 'OAuth temporary token secret = ' + @oauthTokenSecret

        DECLARE @oauthCbConfirmed nvarchar(4000)
        EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
        EXEC sp_OAMethod @resp, 'UrlEncParamValue', @oauthCbConfirmed OUT, @sTmp0, 'oauth_callback_confirmed'

        PRINT 'OAuth callback confirmed  = ' + @oauthCbConfirmed

        -- At this point, the end-user needs to browse to the following
        -- Twitter URL to log in to his/her Twitter account and get a PIN.
        -- 
        -- https://api.twitter.com/oauth/authenticate?oauth_token=OAUTH_TOKEN
        -- 
        -- (where OAUTH_TOKEN is replaced with the contents
        -- of the OAuth temporary request token.)

        -- Your application may have an embedded browser such
        -- that it automatically navigates to the above URL, or it may
        -- be necessary for the user to browse to this URL independently.

        -- Once the PIN is obtained, your application should provide a means
        -- for the end-user to enter it (by typing it into an input text box, for example), 
        -- and then Step 2 (the final step) can begin.

      END
    ELSE
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
      END

    EXEC @hr = sp_OADestroy @http
    EXEC @hr = sp_OADestroy @req
    EXEC @hr = sp_OADestroy @resp


END
GO