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 new CacheProvider to store data in LDAp under ou=session #83

Closed
yurem opened this Issue Jul 4, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@yurem
Contributor

yurem commented Jul 4, 2018

In 4.0 we added Couchbase support. It allows to store specific portion of data in Memcached. Hence there is no sense to use external Memcahed, Redis, etc in case if organization selected to use Couchbase. We need additional CacheProvider which should store data under ou=sessions.

@yuriyz

This comment has been minimized.

Contributor

yuriyz commented Jul 4, 2018

@yurem I propose to put it under ou=cache since we put in cache not only sessions but many other entities. What do you think?

@afroDC

This comment has been minimized.

afroDC commented Jul 6, 2018

Hence there is no sense to use external Memcahed, Redis, etc

This could cause issues as memcached is not clusterable/replicatable. So for full redundancy you would still need to fall back to redis-cluster or utilize couchbase for cache, tokens and session data.

@yurem

This comment has been minimized.

Contributor

yurem commented Sep 26, 2018

We did this in 3.1.4 already

@yurem yurem closed this Sep 26, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment