This message was deleted.
# general
s
This message was deleted.
z
Today it requires client auth I believe if TLS is enabled, but it wouldn't be hard to make that optional
Actually. If you override the has access interfaces you can make it so probably
e
as currently TLS auth is the only way to configure ACL I think that I will have to stick to it at least initially
so you provision TLS certificates to each client ? both ingest jobs and clients of the router ?
z
Yup.
e
makes sense, thanks
in order to implement other authentication mechanisms we will have to add new protocol data units on the wire protocol, so it is not a trivial change
z
Can this be made easier with an interface change?
e
Not only with Java code. Because there should be some authentication handshake. This is done by the TLS layer currently. Usually you need a request PDU inwhich you padd a token, a username/password pair or something more complicated
z
This might be doable today if I learn a bit more. We have the utility for adding additional netty handlers to the routers request pipeline by means of configuration. if you can link me something I can maybe connect the dots.
e
I will post some ideas on a GH issue tomorrow