(SQL Server) Google Drive Insert Permission

This example demonstrates how to insert a permission for a file (see https://developers.google.com/drive/v2/reference/permissions/insert)

The impetus for creating this example was a need to be able to view files uploaded using a service account key in the Google Drive web interface. When using a service account access token, the files your application will see are those for the service account, and not the files for your main account. For example, the Google Account I use for testing has a username of "support@chilkatcloud.com". (Don't send email to support@chilkatcloud.com, it's just use for testing and not interactively read.) I use "support@chilkatcloud.com" when I log into Google interactively to view files in Google Drive at https://drive.google.com/drive/my-drive.

The files I upload to Google Drive using a service account key won't be visible in the browser UI. To make them visible, you need to insert a permission for the file so that the main user account, which in this case is "support@chilkatcloud.com", is a reader. After the permission is inserted, the file will be visible under "Shared with me" -- as if another Google Drive account shared the file with you.

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 = 1

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

    -- This example uses a previously obtained access token having permission for the 
    -- Google Drive scope.

    DECLARE @gAuth int
    -- Use "Chilkat_9_5_0.AuthGoogle" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.AuthGoogle', @gAuth OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    EXEC sp_OASetProperty @gAuth, 'AccessToken', 'GOOGLE-DRIVE-ACCESS-TOKEN'

    DECLARE @rest int
    -- Use "Chilkat_9_5_0.Rest" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Rest', @rest OUT

    -- Connect using TLS.
    DECLARE @bAutoReconnect int
    SELECT @bAutoReconnect = 1
    EXEC sp_OAMethod @rest, 'Connect', @success OUT, 'www.googleapis.com', 443, 1, @bAutoReconnect

    -- Provide the authentication credentials (i.e. the access token)
    EXEC sp_OAMethod @rest, 'SetAuthGoogle', @success OUT, @gAuth

    EXEC sp_OAMethod @rest, 'AddHeader', @success OUT, 'Content-Type', 'application/json; charset=UTF-8'

    DECLARE @json int
    -- Use "Chilkat_9_5_0.JsonObject" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @json OUT

    EXEC sp_OAMethod @json, 'AppendString', @success OUT, 'role', 'reader'
    EXEC sp_OAMethod @json, 'AppendString', @success OUT, 'type', 'user'
    EXEC sp_OAMethod @json, 'AppendString', @success OUT, 'value', 'support@chilkatcloud.com'

    -- A note from a Chilkat customer:
    -- 
    --   My coding attempt was frustrated because I tried a role of "owner".
    --   Even when providing the extra parameter of ...?transferOwnership=true
    --   that approach fails (400, Bad Request).
    -- 

    -- This example is inserting a permission for the file whose fileId is "0By-hrxCCDzSQUGxJY0hzNUFpNmc".
    DECLARE @jsonResponse nvarchar(4000)
    EXEC sp_OAMethod @json, 'Emit', @sTmp0 OUT
    EXEC sp_OAMethod @rest, 'FullRequestString', @jsonResponse OUT, 'POST', '/drive/v2/files/0By-hrxCCDzSQUGxJY0hzNUFpNmc/permissions', @sTmp0
    EXEC sp_OAGetProperty @rest, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 <> 1
      BEGIN
        EXEC sp_OAGetProperty @rest, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @gAuth
        EXEC @hr = sp_OADestroy @rest
        EXEC @hr = sp_OADestroy @json
        RETURN
      END

    -- A successful response will have a status code equal to 200.
    EXEC sp_OAGetProperty @rest, 'ResponseStatusCode', @iTmp0 OUT
    IF @iTmp0 <> 200
      BEGIN

        EXEC sp_OAGetProperty @rest, 'ResponseStatusCode', @iTmp0 OUT
        PRINT 'response status code = ' + @iTmp0

        EXEC sp_OAGetProperty @rest, 'ResponseStatusText', @sTmp0 OUT
        PRINT 'response status text = ' + @sTmp0

        EXEC sp_OAGetProperty @rest, 'ResponseHeader', @sTmp0 OUT
        PRINT 'response header: ' + @sTmp0

        PRINT 'response JSON: ' + @jsonResponse
        EXEC @hr = sp_OADestroy @gAuth
        EXEC @hr = sp_OADestroy @rest
        EXEC @hr = sp_OADestroy @json
        RETURN
      END

    -- Show the JSON response.
    EXEC sp_OAMethod @json, 'Load', @success OUT, @jsonResponse

    -- Show the full JSON response.
    EXEC sp_OASetProperty @json, 'EmitCompact', 0
    EXEC sp_OAMethod @json, 'Emit', @sTmp0 OUT
    PRINT @sTmp0


    PRINT 'Success.'

    EXEC @hr = sp_OADestroy @gAuth
    EXEC @hr = sp_OADestroy @rest
    EXEC @hr = sp_OADestroy @json


END
GO