zhouzb
zhouzb
@qzhuyan The user has not deployed LB
@qzhuyan I think you mean that for two-way authentication, it is allowed not to explicitly set CACert, so that EMQX can find it from the OS dir and provide clear...
> So if it is set, EMQX must find it otherwise error log it. I agree that EMQX must ensure that the specified file exists. But in the current implementation,...
您好，您的邮件已经收到，我会及时处理。 如有急事，请电话联系。 by 周子博.
@qzhuyan Now the disconnection reasons include `protocol_error`, `unspecified_error`, etc. It seems that EMQX will convert the Reason Code in the MQTT 5.0 DISCONNECT packet into the corresponding meaning. But `malformed_packet`...
After this issue is fixed, there is still a risk of crash. In function `replace_placeholder` of module `emqx_authn_jwt.erl`: ```erlang replace_placeholder(L, Variables) -> replace_placeholder(L, Variables, []). replace_placeholder([], _Variables, Acc) -> Acc;...
@zmstone But EMQX documentation does not mention that the placeholders supported by JWT authn are different from other authn: [authentication-placeholders](https://docs.emqx.com/en/enterprise/latest/access-control/authn/authn.html#authentication-placeholders)
I found it: [JWT AuthN](https://docs.emqx.com/en/emqx/latest/access-control/authn/jwt.html) Maybe it's time to support it.
@zmstone The PR #13216 just fixed issue [#13185](https://github.com/emqx/emqx/issues/13185), this issue is talking about another thing. I want the generated Client ID to have a predictable suffix, so that I can...
@zmstone I don't think so, the default value of this option in the configuration file is also false.