Summary
User is facing a 403 Forbidden error when trying to override Slack oauth credentials via the PUT oauthCredentials
API. User has confirmed that Slack credentials are correct.
Question
hey all I’m trying to override Slack oauth credentials via PUT oauthCredentials
API (https://reference.airbyte.com/reference/workspaceoauthcredentials|doc), but it always returns 403 Forbidden error and I’m not sure why. I checked slack credentials are correct - Anyone know whats going on here?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["slack", "oauth-credentials", "put-api", "403-forbidden-error"]
--url <https://api.airbyte.com/v1/workspaces/><workspace_id>/oauthCredentials \
--header 'authorization: Bearer <token>' \
--header 'content-type: application/json' \
--data '
{
"actorType": "source",
"name": "slack",
"configuration": {
"credentials": {
"client_id": "<ID>",
"client_secret": "<SECRET>"
}
}
}
'```
If you’re using Airbyte Cloud (which I’m assuming by your endpoint), I would put in a support request and you’ll likely get the fastest help that way.
But do be sure to post any insights from their help back here as I’m sure it would be useful to others!
No. I sent a support request but no response
Ah, that’s unfortunate. FWIW I found that that endpoint was not implemented: https://airbytehq.slack.com/archives/C021R3F2HUJ/p1724617016751239
Thanks for sharing the info! I wasted many hours debugging what was wrong on my side
<@U07HV0VSB6C> did you resolve this? I’m seeing a similar issue in Airbyte OSS.