(Tcl) Okta Client Credentials FLow

The Client Credentials flow is recommended for use in machine-to-machine authentication. Your application will need to securely store its Client ID and Secret and pass those to Okta in exchange for an access token. At a high-level, the flow only has two steps:

• Your application passes its client credentials to your Okta authorization server.
• If the credentials are accurate, Okta responds with an access token.

Note: This example uses "customScope". You'll replace it with whatever scope(s) you've defined for your app. Scopes are defined in your Authorization Server. See Okta Authorization Server / Scopes

For more information, see https://developer.okta.com/docs/guides/implement-client-creds/use-flow/

Chilkat Tcl Extension Downloads Chilkat Tcl Extension Downloads

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]

# Implements the following CURL command:

# curl --request POST \
#   --url https://{yourOktaDomain}/oauth2/default/v1/token \
#   --header 'accept: application/json' \
#   --user "client_id:client_secret" \
#   --header 'cache-control: no-cache' \
#   --header 'content-type: application/x-www-form-urlencoded' \
#   --data 'grant_type=client_credentials&scope=customScope'

CkHttp_put_Login $http "client_id"
CkHttp_put_Password $http "client_secret"

set req [new_CkHttpRequest]

CkHttpRequest_put_HttpVerb $req "POST"
CkHttpRequest_put_Path $req "/oauth2/default/v1/token"
CkHttpRequest_put_ContentType $req "application/x-www-form-urlencoded"
CkHttpRequest_AddParam $req "grant_type" "client_credentials"
CkHttpRequest_AddParam $req "scope" "customScope"

CkHttpRequest_AddHeader $req "accept" "application/json"

# resp is a CkHttpResponse
set resp [CkHttp_PostUrlEncoded $http "https://{yourOktaDomain}/oauth2/default/v1/token" $req]
if {[CkHttp_get_LastMethodSuccess $http] == 0} then {
    puts [CkHttp_lastErrorText $http]
    delete_CkHttp $http
    delete_CkHttpRequest $req
    exit
}

set sbResponseBody [new_CkStringBuilder]

CkHttpResponse_GetBodySb $resp $sbResponseBody
set jResp [new_CkJsonObject]

CkJsonObject_LoadSb $jResp $sbResponseBody
CkJsonObject_put_EmitCompact $jResp 0

puts "Response Body:"
puts [CkJsonObject_emit $jResp]

set respStatusCode [CkHttpResponse_get_StatusCode $resp]
puts "Response Status Code = $respStatusCode"
if {$respStatusCode >= 400} then {
    puts "Response Header:"
    puts [CkHttpResponse_header $resp]
    puts "Failed."
    delete_CkHttpResponse $resp

    delete_CkHttp $http
    delete_CkHttpRequest $req
    delete_CkStringBuilder $sbResponseBody
    delete_CkJsonObject $jResp
    exit
}

delete_CkHttpResponse $resp

# Sample JSON response:
# (Sample code for parsing the JSON response is shown below)

# {
#   "access_token": "eyJraWQiO ... B2CnCLj7GRUW3mQ",
#   "token_type": "Bearer",
#   "expires_in": 3600,
#   "scope": "customScope"
# }

# Sample code for parsing the JSON response...
# Use the following online tool to generate parsing code from sample JSON:
# Generate Parsing Code from JSON

set access_token [CkJsonObject_stringOf $jResp "access_token"]
set token_type [CkJsonObject_stringOf $jResp "token_type"]
set expires_in [CkJsonObject_IntOf $jResp "expires_in"]
set scope [CkJsonObject_stringOf $jResp "scope"]

delete_CkHttp $http
delete_CkHttpRequest $req
delete_CkStringBuilder $sbResponseBody
delete_CkJsonObject $jResp