hi all, we just ran into a pretty unfortunate issu...
# troubleshoot
w
hi all, we just ran into a pretty unfortunate issue where the CLI is entirely broken when working with systems that have system auth enabled. filed a bug for it here, but wanted to also reach out and provide a direct heads up: https://github.com/datahub-project/datahub/issues/7852
📖 1
🔍 1
l
This content can't be displayed.
a
Thanks for the heads up! @bulky-soccer-26729 could you take a look here?
b
hey Tim! did you export your auth token in your CLI so it knows to use it? ie.
export DATAHUB_GMS_TOKEN=ey123...the token you generated
if that works for you, then this might be an issue with documentation and not a bug
w
hey chris, i did not, i was attempting to use ther system authentication tokens (which were in the environment). i expected these system auth creads to work because of https://github.com/datahub-project/datahub/blob/master/metadata-ingestion/src/datahub/cli/cli_utils.py#L37-L38 aand https://github.com/datahub-project/datahub/blob/master/metadata-ingestion/src/datahub/cli/cli_utils.py#L167
a
gotcha gotcha - yeah you need to set that token variable up as well if you have metadata auth enabled. if you give that a try let us know! then some docs should be updated here regardless
w
hmm okay, thanks. if we need that token, why were we able to CURL the endpoints without it?
b
hm you didn't need it in the curl request? what did your auth header look like?
w
Like the basic auth header that function i linked did. Just the two system auth parts with a colon between
These were calls internal to the network, not from externally via the front end, so I think it mirrored auth that like MCE and such use to talk to GMS?