Fix: Supporting Database Strategies with Credentials Provider #13292
+43
−20
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.
Fix: Supporting Database Strategies with Credentials Provider
☕️ Reasoning
EN
When using the Credentials Provider with a database strategy, sessions were not being persisted and authentication did not work as expected.
This change updates the logic to properly store sessions in the database.
(I'm a Japanese student so I can't speak English well... Sorry...)
JA
🧢 Checklist
🎫 Affected issues
Resolves: #11088
Resolves: #10280
📌 Resources