SQL Server

Duo Auth API - Check

See more Duo Auth MFA Examples

The /check endpoint can be called to verify that the Auth API integration and secret keys are valid, and that the signature is being generated properly. 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.

    DECLARE @integrationKey nvarchar(4000)
    SELECT @integrationKey = 'DIMS3V5QDVG9J9ABRXC4'
    DECLARE @secretKey nvarchar(4000)
    SELECT @secretKey = 'HWVQ46nubLBxhnRlKddTltWIi3hL0fIQF2qTvLab'

    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, 'Accept', 'application/json'

    -- Use your own hostname here:
    DECLARE @url nvarchar(4000)
    SELECT @url = 'https://api-a03782e1.duosecurity.com/auth/v2/check'

    EXEC sp_OASetProperty @http, 'Login', @integrationKey
    EXEC sp_OASetProperty @http, 'Password', @secretKey

    DECLARE @jsonStr nvarchar(4000)
    EXEC sp_OAMethod @http, 'QuickGetStr', @jsonStr OUT, @url
    EXEC sp_OAGetProperty @http, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        RETURN
      END


    EXEC sp_OAGetProperty @http, 'LastStatus', @iTmp0 OUT
    PRINT 'status code = ' + @iTmp0

    PRINT @jsonStr

    -- Sample successful output:

    -- status code = 200
    -- {"response": {"time": 1632358829}, "stat": "OK"}

    EXEC @hr = sp_OADestroy @http


END
GO