Issue with Airbyte API calls in self-managed community deployment

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

User is facing issues with Airbyte API calls in a self-managed community deployment and is inquiring about email authentication availability.


Question

Hi Guys,

I have deployed airbyte using Helm , ( self managed community ) Facing some issues while creating airbyte api calls.

Does the self managed community version has email authentication ?

Can you please help me with your views.


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

["airbyte-api-calls", "self-managed-community", "email-authentication"]
2

Do endpoints you call start with /api/public/v1/...?

3

Thank you for responding

I am currently using this api - “http://ipaddress:port/public/v1/sources”

I am getting this error {“message”:“Forbidden”,“_embedded”:{“errors”:[{“message”:“Forbidden”,“_embedded”:{},“_links”:{}}]},“_links”:{“self”:{“href”:“/public/v1/sources”,“templated”:false}}}

4

Does it point to server? webapp?

5

it is pointing towards server

6

When deploying through Helm, I believe basic auth is disabled by default (whereas with abctl it’s enabled by default).

You can either set up your own rules, or use platform-specific tools to authenticate and authorize API requests (e.g. Google Cloud IAP if you’re on GCP and want to authenticate with a Google account).

And note that you do want that /api/ prefix on the path to ensure that the requests are routed correctly (the documentation without it is generally referring to how it works in Cloud)