Tcl
Tcl
Configure OAuth 2.0 Authentication for REST
See more REST Examples
Demonstrates Rest.SetAuthOAuth2, which associates an OAuth2 provider containing a valid access token so Chilkat adds the bearer token to the Authorization header.
Background. OAuth 2.0 bearer-token authentication attaches the access token to each request. The token is typically obtained separately through an OAuth 2.0 authorization flow before being assigned to the provider.
Chilkat Tcl Downloads
load ./chilkat.dll
set success 0
set rest [new_CkRest]
set bTls 1
set bAutoReconnect 1
set success [CkRest_Connect $rest "example.com" 443 $bTls $bAutoReconnect]
if {$success == 0} then {
puts [CkRest_lastErrorText $rest]
delete_CkRest $rest
exit
}
# Configure OAuth 2.0 bearer-token authentication. The provider must contain a valid access token.
set oauth2 [new_CkOAuth2]
# Normally you would not hard-code secrets in source. You should instead obtain them from an
# interactive prompt, environment variable, or a secrets vault.
CkOAuth2_put_AccessToken $oauth2 "OAUTH2_ACCESS_TOKEN"
# Associate the provider so Chilkat adds the bearer token to the Authorization header.
set success [CkRest_SetAuthOAuth2 $rest $oauth2]
if {$success == 0} then {
puts [CkRest_lastErrorText $rest]
delete_CkRest $rest
delete_CkOAuth2 $oauth2
exit
}
set responseText [CkRest_fullRequestNoBody $rest "GET" "/api/resource"]
if {[CkRest_get_LastMethodSuccess $rest] == 0} then {
puts [CkRest_lastErrorText $rest]
delete_CkRest $rest
delete_CkOAuth2 $oauth2
exit
}
puts "$responseText"
delete_CkRest $rest
delete_CkOAuth2 $oauth2