Cache should be multi application safe

[yurem]

There are at least 3 applications now which reuses same cache implementation. All of them put data into same caching server or DB. This can led to key conflicts. We need to add key prefix for each application.
Also another aspect is data clean up. Now 3 applications trigger NativePersistence cache clean up to do global clean up. We need to allow to do clean up only application keys.

[yurem]

This issue becomes priority. We have few apps which reuse cache classes. As result cleaner job can't clean specif service data. It do global clean up.

For me each cache entry should have appllication_id attribute. Also if DB supports tree based model we need to use base DN like this:
ou=application_id,ou=cache,o=gluu.

For DB which support tree based model we can use base DN. For rest DB we can use new attribute to find application specific entries.

[yuriyz]

I'm not sure how additional attribute is going to help to make cache application safe.
If let say we have scope DN, key would be the same for both oxauth and oxtrust for example (CB). Thus it may overwrite each other (with underlying attributes). We can unify it by prefixing key with additional symbol for example. Then for different apps even with same key underlying CacheService will make it different/translate (depending on ApplicationType).
E.g. DN scope1 for oxauth would be ascope1 and for oxtrust tscope1 (or maybe add it as suffix scope1a/scope1t). The drawback is that we double some entries while in reality it is same data.
Re: independent clean up, for Couchbase we have TTL. Open question is only for LDAP (tree based persistence). I guess idea of ou=oxauth,ou=cache,o=gluu should work.