Hello everyone, We are trying to ingest data from the on-premise Tableau server. We made sure the user has all the permissions as specified in tableau pre-requisites here: https://datahubproject.io/docs/quick-ingestion-guides/tableau/setup but we are not able to ingest metadata yet wuing UI based ingestion recipe/scheduler. we keep getting this error, We know for sure username and passwords are correct, does anyone have idea on how do we resolve this SSL Certificate verify failed error?

"tableau-login": [
          "Unable to login (check your Tableau connection and credentials): HTTPSConnectionPool(host='172.25.160.82', port=443): Max retries exceeded with url: /api/2.4/auth/signin (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:997)')))"

With the same user, We can log in from UI fine. We also confirmed firewall is not blocking anything, the curl into the Tableau server IP address runs well from the datahub action pod. On the other hand, when I use exact same recipe on back end and run cli based ingestion manually, I get pass this error and get something else (some charts, tags, and projects ingested while some failed with this error.

{
  "error": "Unable to emit metadata to DataHub GMS: java.lang.RuntimeException: Unknown aspect browsePathsV2 for entity container",
  "info": {
    "exceptionClass": "com.linkedin.restli.server.RestLiServiceException",
    "message": "java.lang.RuntimeException: Unknown aspect browsePathsV2 for entity container",
    "status": 500,
    "id": "urn:li:container:00eafb6262a384f1fc4e9582f576ba3d"
  }
}

To get around SSL error, you can set config

ssl_verify: False

in recipe. About browsePathsV2 error, looks like your ingestion cli version does not align with gms version.. You'll need at least 0.10.3 for browsePathsV2 to work.

Thank you so much, i will try SSL setting out. I have cli version10.5x when i try to ingest from backend. For sure its slightly different from the server version. I think i can match cli version when doing from UI by providing desired cli version.