Back to Collection Items
-- 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)
-- This example assumes the Chilkat API to have been previously unlocked.
-- See Global Unlock Sample for sample code.
DECLARE @http int
-- Use "Chilkat_9_5_0.Http" for versions of Chilkat < 10.0.0
EXEC @hr = sp_OACreate 'Chilkat.Http', @http OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
DECLARE @success int
DECLARE @req int
-- Use "Chilkat_9_5_0.HttpRequest" for versions of Chilkat < 10.0.0
EXEC @hr = sp_OACreate 'Chilkat.HttpRequest', @req OUT
EXEC sp_OAMethod @req, 'AddParam', NULL, 'response_type', 'code_credentials'
DECLARE @jsonParam2 int
-- Use "Chilkat_9_5_0.JsonObject" for versions of Chilkat < 10.0.0
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @jsonParam2 OUT
EXEC sp_OAMethod @jsonParam2, 'Emit', @sTmp0 OUT
EXEC sp_OAMethod @req, 'AddParam', NULL, 'client_id', @sTmp0
DECLARE @jsonParam3 int
-- Use "Chilkat_9_5_0.JsonObject" for versions of Chilkat < 10.0.0
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @jsonParam3 OUT
EXEC sp_OAMethod @jsonParam3, 'Emit', @sTmp0 OUT
EXEC sp_OAMethod @req, 'AddParam', NULL, 'redirect_uri', @sTmp0
EXEC sp_OAMethod @req, 'AddParam', NULL, 'scope', ''
EXEC sp_OAMethod @req, 'AddHeader', NULL, 'Auth-Verification-Type', 'email'
EXEC sp_OAMethod @req, 'AddHeader', NULL, 'Auth-Request-Type', 'user-registration'
EXEC sp_OAMethod @req, 'AddHeader', NULL, 'Authorization', 'Basic <base64Encoded identifier:otp>'
DECLARE @resp int
EXEC sp_OAMethod @http, 'PostUrlEncoded', @resp OUT, 'https://login.salesforce.com{{site}}/services/oauth2/authorize', @req
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
EXEC @hr = sp_OADestroy @req
EXEC @hr = sp_OADestroy @jsonParam2
EXEC @hr = sp_OADestroy @jsonParam3
RETURN
END
EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
PRINT @iTmp0
EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @resp
EXEC @hr = sp_OADestroy @http
EXEC @hr = sp_OADestroy @req
EXEC @hr = sp_OADestroy @jsonParam2
EXEC @hr = sp_OADestroy @jsonParam3
END
GO
Curl Command
curl -X POST
-H "Auth-Request-Type: user-registration"
-H "Auth-Verification-Type: email"
-H "Authorization: Basic <base64Encoded identifier:otp>"
--data-urlencode 'response_type=code_credentials'
--data-urlencode 'client_id={{clientId}}'
--data-urlencode 'redirect_uri={{redirectUrl}}'
--data-urlencode 'scope='
https://login.salesforce.com{{site}}/services/oauth2/authorize
Postman Collection Item JSON
{
"name": "Registration - Authorize",
"request": {
"auth": {
"type": "noauth"
},
"method": "POST",
"header": [
{
"key": "Auth-Request-Type",
"value": "user-registration",
"description": "Required for User Registration"
},
{
"key": "Auth-Verification-Type",
"value": "email",
"description": "Must match init/registration, email or sms"
},
{
"key": "Authorization",
"value": "Basic <base64Encoded identifier:otp>",
"description": "Base64 encoded <Identifier:OTP>"
}
],
"body": {
"mode": "urlencoded",
"urlencoded": [
{
"key": "response_type",
"value": "code_credentials",
"type": "text"
},
{
"key": "client_id",
"value": "{{clientId}}",
"type": "text"
},
{
"key": "redirect_uri",
"value": "{{redirectUrl}}",
"type": "text"
},
{
"key": "scope",
"value": "",
"description": "Comma seperated list of scopes, optional",
"type": "text"
}
]
},
"url": {
"raw": "{{url}}{{site}}/services/oauth2/authorize",
"host": [
"{{url}}{{site}}"
],
"path": [
"services",
"oauth2",
"authorize"
]
},
"description": "After you send your registration data to initialize, this request allows you to process that registration data, and as a part of this request you also verify the users email or sms number. The request itself is a authorization call for the Code and Credential flow. It includes 3 specific headers: `Auth-Request-Type` which is set to `user-registration`, `Auth-Verification-Type` which is set to email or sms, and an Authorization Basic header, which is the base 64 encoded result of `identifier:otp` where `identifier` is the value returned in your initialize registration call, and `otp` is the value sent to the end user via email or sms.\n\nThe response from this API is the Auth Code, which is then exchanged for the Access Token."
},
"response": [
]
}