|
All content with label cache+security.
Related Labels:
best-practices
, expiry
, re-entrant
, coherence-web
, namedcache
, concurrency
, cache-topologies
, production-environment
, coherence-cache-config
, cluster
, extend
, cachestore
, core-concept
, expiration
, hibernate
, network
, semantics
, serialization
, query
,
example
, topology
, transactions
, faq-coherence-web
, loading
, pre-loading
, operating-system
, object-model
, colocate
, configuration
, hardware
, distributed-loading
, bulk-loading
, chainedextractor
, configuration-elements
, faq-code-examples
, near-cache
, local-cache
more »
( - cache
, - security
)
How can I restrict a Coherence*Extend client's access to a cache?
(Coherence FAQ)
attached example security.jar demonstrates how to authenticate a CoherenceExtend client and pass the client's identity to the cluster, where it is used to enforce entitlements on a target {{NamedCache}}. The attached JAR file includes both .NET and Java sample clients. A CoherenceExtend client authenticates ...
|
|
|