fix: credentials: only decrypt credentials in the context(s) needed #908
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.
There is some serious slowness in credentials when encryption is on and the number of stored credentials is greater than approximately 100. This is caused by a call to
Get
in theGetAll
function in our credential store implementation. CallingGet
for a credential results in a decryption operation. Even when trying to list credentials in just one context, the implementation ofGetAll
was resulting in the server decrypting every credential in the database, instead of just the ones in the requested context. This PR fixes that, byGet
ing only the credentials that will actually be returned to the user.