New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
%c and %u not working with the dynamic security plugin. #2222
Comments
I'm afraid at the moment the |
The code in |
Hi, |
@ralight awesome, I'm looking forward to this as well! |
Just came across this as I've started using this plugin. Great plugin, thanks! would you know when this functionality be released? |
Is there any information about when 2.1 will be released? https://projects.eclipse.org/projects/iot.mosquitto shows it should've been released 4 months ago |
I just started to use the plugin and was hoping to use this functionality for creating my roles. Unfortunately 2.1 appears to be not released still?? |
I hope this will be in release soon |
The first relevant commit is this one: 0cd2619 You can find the commit history for that plugin since that commit here: https://github.com/eclipse/mosquitto/commits/develop/plugins/dynamic-security?since=2021-06-10&after=1bb2299b0f3e44624cf3057f773cb8235e7f09b3+104 |
For the roles assigned in the dynamic security plugin, the use of %c and %u are not working as expected as it's used with ACL file .
In the ACL file, the use of
pattern readwrite data/%u/#
allows the user named userone to access the topic data/userone/messages and similar for the other username but the same does not apply for the dynamic security plugin when used such characters.Given below is my sample role configuration which allows topic subscription and publishing using the characters "%u" itself only.
We can create separate roles for the individual users appending the respective username in the ACLs topic but looking for the generic implementation of the automatic username fetching features based on characters such as %c or %u to be used with the dynamic security plugin.
Are there any other ways to define the roles to achieve the same thing?
Note: using both acl_file with content
pattern readwrite %u/#
and dynamic security plugin with the above-mentioned role didn't achieve the expected result.The text was updated successfully, but these errors were encountered: