Chilkat Online Tools

TCL / Salesforce Platform APIs / Registration - Authorize

Back to Collection Items

load ./chilkat.dll

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

set http [new_CkHttp]

set req [new_CkHttpRequest]

CkHttpRequest_AddParam $req "response_type" "code_credentials"

set jsonParam2 [new_CkJsonObject]

CkHttpRequest_AddParam $req "client_id" [CkJsonObject_emit $jsonParam2]

set jsonParam3 [new_CkJsonObject]

CkHttpRequest_AddParam $req "redirect_uri" [CkJsonObject_emit $jsonParam3]
CkHttpRequest_AddParam $req "scope" ""

CkHttpRequest_AddHeader $req "Auth-Verification-Type" "email"
CkHttpRequest_AddHeader $req "Auth-Request-Type" "user-registration"
CkHttpRequest_AddHeader $req "Authorization" "Basic <base64Encoded identifier:otp>"

# resp is a CkHttpResponse
set resp [CkHttp_PostUrlEncoded $http "https://login.salesforce.com{{site}}/services/oauth2/authorize" $req]
if {[CkHttp_get_LastMethodSuccess $http] == 0} then {
    puts [CkHttp_lastErrorText $http]
    delete_CkHttp $http
    delete_CkHttpRequest $req
    delete_CkJsonObject $jsonParam2
    delete_CkJsonObject $jsonParam3
    exit
}

puts [CkHttpResponse_get_StatusCode $resp]
puts [CkHttpResponse_bodyStr $resp]
delete_CkHttpResponse $resp


delete_CkHttp $http
delete_CkHttpRequest $req
delete_CkJsonObject $jsonParam2
delete_CkJsonObject $jsonParam3

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": [
  ]
}