zmstone
zmstone
This is not a bug, but a feature request. JWT authn only supports placeholders for `clientid` and `username` to check against the JWT claims. A workaround for now is to...
Okay. Keep this open then. There will be a feature to support a pool of pre-allocated client ids (not just suffix).
@ysfscream this is more of a frontend enhancement?
> Why do we even have this option? Is there a scenario when a user may want to allow plain tcp connection on SSL port? Good point.
> @zmstone I don't think so, the default value of this option in the configuration file is also false. We can change default value from backend, but frontend is independent...
Here is my proposal. In 5.8, we will only expose "verify peer" option in config and in dashboard, always force client to send certificate when "verify_peer". For backward compatibility, we...
> > Here is my proposal. In 5.8, we will only expose "verify peer" option in config and in dashboard, always force client to send certificate when "verify_peer". For backward...
@jasonccs thank you for the report. We'll follow up with a fix, but hard to commit which release.
So we need to find a place to store LSN, mnesia is probably the only option. But I am not entirely sure if it's necessary to use Mnesia to distribute...
I think it would benefit other application if there is a generic leadership among the core nodes. Maybe provided by `ekka` or `mria`, the leader process should have a incremental...