Hi Team, I recently enabled metadata access token on my frontend and gms, Now i can’t seem to ingest my tableau metadata to the datahub, It throws authentication error. As far as I understand I probably need to supply metadata token for the ingestion. But is there way I can keep metadata authentication token generation (I use it to make delete request) and not have to authenticate when I ingest data?

failed to write record with workunit container-urn:li:container:2380f5d80f130b57eeeee5016d8c18b7-to-urn:li:chart:(tableau,885b1266-5bd9-4338-745e-c480bc7f0168) with ('Unable to emit metadata to DataHub GMS', {'message': '401 Client Error: Unauthorized for url:

Hello Siddharth, No. When enabling metadata authentication all requests require an auth token. From that auth DataHub matches a user who may or may not have permissions to execute a given task.

Hey @incalculable-ocean-74010 Thanks for reply. We were using 0.8.31 gms version before this, and we were able to ingest data without auth token. As well as generate metadata_token. Is this change of all requests to require an auth token introduced in newer versions ? Also, In earlier deployment of 0.8.31 we did not mention any specific environment variable for enabling GMS token and we were still able to generate token from UI. Is that also only introduced in newer version?

The change to all request was the original design, it is possible that is wasn't implemented fully by 0.8.31

@incalculable-ocean-74010 That would mean we would have to use access token for ingestion, On UI I only see the maximum token validity to be 3 months. Is there a way to increase this validity? Or make the token no expire at all. Because this would lead to refreshing all the config files every 90 days.

There is a work in progress to have eternal access tokens, until that is out 3 months is the best we can do

okay. Thanks!