-
Notifications
You must be signed in to change notification settings - Fork 163
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
JWT remote mode acl route issue #284
Comments
You're absolutely right, for some reason I made the option available in the HTTP backend but not in the JWT that's hardcoding it to 5 seconds here: https://github.com/iegomez/mosquitto-go-auth/blob/master/backends/jwt_remote.go#L155 I'll try to add the option soon. |
I opened the PR for adding a custom parameter The PR is in |
Thanks for opening a PR. There are a few issues and I need to check why tests are not running on external PRs, probably some misconfigured setting on my side. |
I ll fix them. Tks |
let me know the test file where you expect the test. |
Sry for the issues but I am not very skilled in go. |
Addressed by #285. |
Hi,
I am using JWT remote mode with
user
,superuser
andacl
route checks.Right now I am using only the
acl
route for checking the permissions. The permission is provided by a remote service so it takes sometimes (depending on the network traffic or parallel requests).The problem is that if the
acl
route not responds before 5 seconds I gotread ECONNRESET
from mqtt client. otherwise everything works as expected.I tried it mocking the remote permission services with a timeout and I can confirm that if the timeout is less then 5000 ms everything is ok otherwise I got the error above.
Likely, I think it is a timeout problem but I can't find any general configuration options to enlarge it or a workaround to solve it.
Opening the container where Mosquitto resides I see:
context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Thanks
AP
The text was updated successfully, but these errors were encountered: