Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hello I Want To Know That Without Any Access To The Webserver Component, Is It Possible To Use Clearml? I’M Asking From A Security Perspective.. Paraphrasing: Can An Intruder With Access To Clearml-Api Do Anything They Want? How Are They Limited? (With

Hello
I want to know that without any access to the webserver component, is it possible to use ClearML?
I’m asking from a security perspective..

Paraphrasing:
Can an intruder with access to clearml-api do anything they want? How are they limited?

(with no Web Login Authentication)

  
  
Posted 2 years ago
Votes Newest

Answers 31


No it doesn’t work from entirely new browser too. 😞
As this is a staging instance. let me remove and deploy without these changes.

  
  
Posted 2 years ago

btw - if you didn't login, the UI probably used a previous token. changing the session secret might have messed that up 🙂

  
  
Posted 2 years ago

image

  
  
Posted 2 years ago

Sure 🙂

  
  
Posted 2 years ago

Awesome info! Thanks!
What env variable should I use?
Also maybe I can block unauthenticated access to that endpoint too, I guess clearml-agent doesn’t use it!

  
  
Posted 2 years ago

no. apparently changing these variables causes something to fail.

  
  
Posted 2 years ago

Well, actually it's used by both ClearML SDK and agent since both start with credentials but generate a token as soon as possible (more secure and faster)

  
  
Posted 2 years ago

Env vars for the webserver:
USER_KEY: some access key USER_SECRET: some secret key COMPANY_ID: "d1bd92a3b039400cbafc60a7a5b1e52b"
Env vars for the apiserver:
CLEARML__SECURE__CREDENTIALS__WEBSERVER__USER__KEY: same as the above key CLEARML__SECURE__CREDENTIALS__WEBSERVER__USER__SECRET: same as the above secret

  
  
Posted 2 years ago

Thanks a million SuccessfulKoala55 😍

  
  
Posted 2 years ago

The dashboard doesn’t load

  
  
Posted 2 years ago

CLEARML__SECURE__HTTP__SESSION_SECRET__APISERVER
Does this one need to be changed?

  
  
Posted 2 years ago

Oh, sorry! both user_key and user_secret are with a single underscore :)

  
  
Posted 2 years ago

CLEARML__SECURE__HTTP__SESSION_SECRET__APISERVER

No, this is unrelated

  
  
Posted 2 years ago

Oh well it doesn’t work for me then… I keep getting errors.

  
  
Posted 2 years ago

Ok I think I might have found the problem.

  
  
Posted 2 years ago

are you sure you're using the latest docker images?

  
  
Posted 2 years ago

It’s probably unrelated 😬 I’ll keep you posted.

  
  
Posted 2 years ago

yep it was unrelated.. sorry
Thanks for your help

  
  
Posted 2 years ago

ah ok. So only solution is changing the hardcoded one…
I will be looking into docs to find the right env variable. If you know it I’d appreciate you telling me 😄 SuccessfulKoala55

  
  
Posted 2 years ago

Where exactky?

  
  
Posted 2 years ago

Can you show exactly what you changed in the docker compose?

  
  
Posted 2 years ago

I’m using cloud-ready helm chart (with some modifications)
So for api-server deployment:

  
  
Posted 2 years ago

Is this after doing a user login in the UI?

  
  
Posted 2 years ago

webserver deployment:

  
  
Posted 2 years ago

I might be wrong about the company_id 🙂 - but in case I'm wrong, you'll see it quickly since you won't be able to login with new users to the UI 🙂

  
  
Posted 2 years ago

SuccessfulKoala55 I’m getting 405 on api calls with the configuration you proposed. (btw I think USER_KEY is right, with a single underscore)

  
  
Posted 2 years ago

The login prompt doesn’t appear (I tried removing cookies and all too)

  
  
Posted 2 years ago

Well, it should appear (if you cleared all cookies)

  
  
Posted 2 years ago

Huh it works now…!

  
  
Posted 2 years ago

with the changes?

  
  
Posted 2 years ago