Connector Builder: NoSuchKey Callback

Help Integration Service
, , ,
1

I’ve been attempting to use the Connection builder using OAuth 2 with an Authentication token. However, it’s been getting caught up on the callback.

I’ve been receiving the error:

{name: 'Unauthorized', 
message: 'Failed to exchange a code for an access token',
providerMessage: '{
    "error":"invalid_client"
}', 
errOriginatedService: 'soba'}

Inspecting the page as it attempts to connect and going back before it hits the ‘invalid client’ bit:

--General:
Request URL:
https://cloud.uipath.com/{company}/defaulttenant/provisioning_/callback?code={code}&state={state}&realmId={here}
`
Request Method:
GET

Status Code:
404

--Res Headers:
x-amz-error-code: NoSuchKey
x-amz-error-detail-key: callback
x-amz-error-message: The specified key does not exist.
x-cache: Error from cloudfront

--Req Headers:
:authority: cloud.uipath.com
:method: GET
:scheme: https
accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9

When inspecting the information it’s passing back and forth, it all seems correct. Is it a limitation of the content type header only accepting application/json?