feat(auth): add support for function for password#1985
Open
slukes wants to merge 1 commit intoredis:mainfrom
Open
feat(auth): add support for function for password#1985slukes wants to merge 1 commit intoredis:mainfrom
slukes wants to merge 1 commit intoredis:mainfrom
Conversation
|
Yes please. |
Author
|
Hello 👋 any chance of a review please |
|
Please review the pr, the feature is very needed |
|
Would this work properly in case of reconnects? |
Contributor
|
At first glance this looks okay, however the checks are failing @slukes please make sure the tests pass and then request a review again |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When working with elasticache with IAM (and probably other providers), it is necessary to use a token that is only valid for 15 minutes as a password, as a result subsequent reconnects need to be done with a newly generated password.
There are at least these two issues discussing this:
#1738
#1810
Up until now we had been using an
on('ready,...)event listener to manage this in our code, but since migrating from bull to bullmq which usesduplicatemethod which does not copy the event listeners and what is more applies it's own on ready listener which makes this option unusable.Rather than continuing with the (quite hacky) work around suggested in the above two issues, I would like to propose that we accept a function instead of a string for the password.