Skip to content
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

Add a token store for MongoDB #295

Merged
merged 5 commits into from
Nov 18, 2017
Merged

Add a token store for MongoDB #295

merged 5 commits into from
Nov 18, 2017

Conversation

jvanderkallen
Copy link
Contributor

@jvanderkallen jvanderkallen commented Mar 7, 2017

This pull request contains a token store for MongoDB. I have tried to make sure the token store properly deals with concurrency which is a little tricky since MongoDB doesn't support transactions. Feel free to let me know if I missed something.

Let me know what you think about this pull request.

@abuijze abuijze added this to the Release 3.1 milestone Apr 5, 2017
@abuijze abuijze added the Type: Feature Use to signal an issue is completely new to the project. label Apr 5, 2017
@smcvb smcvb added Type: Enhancement Use to signal an issue enhances an already existing feature of the project. and removed Type: Enhancement Use to signal an issue enhances an already existing feature of the project. labels Aug 1, 2017
@Hronom
Copy link

Hronom commented Oct 8, 2017

When?

Instead of having an instance for each components, now a single
MongoTemplate instance is used for all mongo based components. The old
implementations still exist, but are deprecated and will be removed
in a future release.

This commit also contains some improvements on the implementation of
the MongoTokenStore.
@abuijze abuijze merged commit 5ed910e into master Nov 18, 2017
@abuijze abuijze deleted the mongo-token-store branch November 19, 2017 13:29
@smcvb smcvb requested review from smcvb and abuijze February 28, 2019 10:49
@smcvb smcvb added Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. labels Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants