Osuka-san, yeah, it can be Basic Auth. For all the endpoints, like gRPC (examples), HTTPS etc. Just don't do that Google-based auth, because what if your Cete cluster is offline in some datacenter... 😉

Essentially would be cool if you could move all the CLI options also to some YAML-like config and so we could just run it as so:

cete -c /etc/cete.conf`

Done! And so then you have inside something like:

auth:
  token: some_very_secret_token_to_connect_to_everything

general:
  mode: master
  grpc: :8888
  https: :8080
  ssl: true

...and so on.

So as a start, we could just share that very secrect token across the cluster (e.g in HTTPS you can carry it on in header) in configs and that's it for starter. Then later on we could add RSA-based auth.

Since you are basically resembling TiKV (which makes your effort very cool!), then why not just steal the authentication ideas from them? :-) Essentially, for my project I need something like TiKV, but it is written in Rust and is a pig-size binary (about 0.5GB !!!). So Cete could do the job perfectly and I think do it very well.

Authentication? HTTPS? #23

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions