swuferhong opened a new issue, #3473: URL: https://github.com/apache/fluss/issues/3473
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Fluss version 0.9.0 (latest release) ### Please describe the bug 🐞 When the readiness probe (or any standalone CLI tool) attempts to authenticate using a plugin-based protocol (e.g. RAM), it fails with "No plugin for the protocol 'XXX' is found in the classpath" because `AuthenticationFactory.loadClientAuthenticatorSupplier` only discovers plugins via ServiceLoader on the classpath (lib/), and does not scan the plugins/ directory. The server-side loadServerAuthenticatorSuppliers already uses `PluginUtils.createPluginManagerFromRootFolder `to discover plugins from the plugins/ folder, but the client-side path does not. ### Solution _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
