-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Subscriber Authentication #14
Conversation
Signed-off-by: Emmanuel Lampe <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
@crackthecodeabhi can you review this PR and make a patch release for it? I'm in desperate need for this for my project and Kreds would be perfect (for my current use case) if this feature was added. Thanks in advance :) |
You can download my fork and install it in your local maven repository, if you need it urgent. I think the author doesn't maintain it further. |
I have just been in contact with the author and he said the following: But I will probably do what you said until the new release is available |
@rexlManu @TomTruyen will be reviewing and merging the issue ASAP. been busy lately. Give me sometime. |
Is there an ETA on this? The PubSub functionality is almost useless without it... I am stuck on project because of this issue |
There needs to be some work done on this PR, the current PR will cause a dead lock since the reader coroutine is not pre-empted before writing on the connection. Will update as soon i fix it and run some tests. |
I didn't get a dead lock when using @rexlManu his version. Does the dead lock only happen in specific scenario's? |
I'm currently using my version pretty much and didn't run in any issues. Maybe share a example where it occurs. |
@rexlManu the subscriber coroutine suspends [waititng to read messages from redis] after it locks the mutex on the Konnection. if the user subscribes to a channel, and then tries to execute any connection command, it will block indefinitely. Hence, a clean approach would be to , accept optional auth parameters while building the subscriber client, and authenticate against redis before doing anything else, this ensure all other commands work as usual with no change. also correction on my part, it won't be a dead lock but unintended blocking of the coroutine indefinitely. |
After calling the subscribe command on the subscriber client, call any other connection command, the coroutine will block |
I tried to use the subscriber client with a redis instance thats password-protected and found out by #8 that authentication is missing.