MammothGoat53 just realized I simply omitted the https
part 😆
Now I'm getting Invalid token (invalid jwt token): reason=Invalid crypto padding
And I'm a bit confused b/c I thought the official python client was doing these same REST calls
- The curl data option needed 2 dashes,
--data
Can you please elaborate how to change what I have? I'm setting this: -H "Authorization: Bearer $CLEARML_TOKEN" \
Oh, cool, now I'm wondering why it didn't work for me 😄
You're absolutely correct - I guess we just don't use projects.get_by_id
😞
Ah interesting. So I should try another API method?
The two things I fixed:
The token had quotes around it. I changed from jq
to jq --raw-output
They're usually issued for 30 days, but you can simply check the embedded jet exp
claim
Hi MammothGoat53 , I believe your code is correct, and that this is some regression bug related to the projects.get_by_id endpoint (I just tried that myself) - I'll make sure we check that out as soon as possible.
Hi MammothGoat53
Basically what you are missing are the headers with the Token you have:
https://blog.logrocket.com/secure-rest-api-jwt-authentication/
You can use projects.get_all
with the ids
parameter (a list of IDs) and just pass a single ID - it works for me
well if you copy pasted my command maybe the -data
vs --data