client_key to be passed on requests to their authorize and token endpoints instead of
client_id. I have been able to set custom
options.authParams on the connection using the Management API for the authorize call (docs), but don’t see a way to do this for the token call, so the connection does not work with error
InternalOAuthError: Failed to obtain access token.
I have verified that the authorization code retrieved by Auth0 works if I use it in a manual cURL request to TikTok’s token endpoint with the params it expects.
TikTok docs: TikTok for Developers | TikTok
Welcome to the Auth0 Community!
From what I can tell, this isn’t possible. As you’ve already noticed, you can map new parameters on the call to authorize, but this doesn’t extend to the token endpoint call.
If you’d like to, you can create a Feature Request for it.
Ideally, TikTok would conform to OAuth2 specs and use
client_id. Using the term
client_key looks like a holdover from OAuth1, even though it appears Tik Tok has implemented other OAuth2 standards.
Thanks, I submitted the feature request. I am now trying to implement TikTok using a proxy for the token call but can’t get it to work. I have my proxy server successfully receiving params from Auth0, passing them to TikTok as required, retrieving an access token payload (appears to be spec-compliant), and returning it as JSON to Auth0. Auth0 just times out on the token call however when I test the flow and I don’t know why.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.