Hi team - I am using Airbyte open source. Source: Elastic Search Destination : SQL However, I am getting this error while setting up the connection: "2022-11-09 091420 ERROR i.a.w.i.DefaultAirbyteStreamFactory(validate):87 - Validation failed: {"error":{"root_cause":[{"type":"security_exception","reason":"no permissions for [indices:admin/get] and User [name=product, backend_roles=[naive-user], requestedTenant=null]"}],"type":"security_exception","reason":"no permissions for [indices:admin/get] and User [name=product, backend_roles=[naive-user], requestedTenant=null]"},"status":403}" Btw, I am using OpenSearch1.3 as source and we have already added this permission on OpenSearch. How to proceed?

Are you able to manually (i.e. with cURL) do a GET on the index name with the user that you are connecting from Airbyte with? https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-get-index.html

Hey Alex, yes we’re able to do a get request using just the index name using cURL this is the request I tried.

curl --location --request GET 'our-host-name/indexName?pretty' \
--header 'Authorization: Basic ourToken'

And you are passing that same authorization via airbye? From the above error message, it looks like you are using a user called “product” — but I am not familiar with the meaning of that error message , so could be mistaken

yes, we’ve put the same auth credentials in the Airbyte UI as well

Have you tried it (temporarily) with the root/admin user, to rule out permissions issues ?

No I haven’t. Will that be necessary? Don’t really feel comfortable putting the admin credentials anywhere. 😅 Alternatively, is there a list of permissions which are compulsory for setting up this sync?

No, that will not be necessary — but it can help you to figure out if it is a permissions issue. I.e. if it works with admin, then you know that there is something wrong with the roles you have assigned to the user that you are using with Airbyte

Thanks. We were able to make the connection by amking it admin. However, the sync is failing. Getting the error of "Failure Origin: source, Message: Something went wrong within the source connector". PFA the error logs.

Hi Chetan, I’m responding to your new question to send it to the channel to see if anyone may know what caused that error.

@Chetan Dalal I've seen this error when there is not enough memory available to the container.

Source process exited with non-zero exit code 137

Hello Chetan Dalal, it's been a while without an update from us. Are you still having problems or did you find a solution?