[Umbrella] Introduce Fluss Authentication and authorization

[loserwang1024]

Search before asking

• I searched in the issues and found nothing similar.

Motivation

Currently, Fluss lacks any form of authentication and authorization mechanisms. This means that anyone can read data, write data, or alter tables without any restrictions. Without these essential security features, Fluss is not suitable for production environments where data security and access control are critical.
In this document, we will discuss how to implement plugin authentication and authorization mechanisms in Fluss to ensure that only authorized users can access and modify data. This will significantly enhance the security and reliability of the system, making it suitable for production use.

Solution

Google Docs: Fluss Authentication and authorization

Anything else?

This issue will be split into multiple tasks：

1. Fluss server supports internal port to listen internal connection.
2. Support plugin Authenticator (and a sasl Authenticator implement)
3. Support pluginAuthorizer.

Willingness to contribute

• I'm willing to submit a PR!

[loserwang1024]

@wuchong , CC

[wuchong]

Thanks @loserwang1024 for proposing the design of Auth and ACL. +1 for it.