Is SASL Authentication Supported For Memcached Access?
(Doc ID 2632315.1)
Last updated on JANUARY 27, 2020
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
Is SASL authentication supported for memcached access?
A directive from an Information Security team requires that if memecached is accessible on the network (i.e. not just listening on the loopback interface), then SASL authentication must be used.
The documentation does not mention any information pertaining to SASL authentication being possible from the Messaging Server when using memcached for mappings, sieve, autoresponse tracking, etc.
Is this possible?
Currently the feasibility of using memcached and/or redis to store information for a deployment change is being explored, which is the reason for this inquiry - i.e. to ascertain whether the use of either of these is practical given the internal security requirements that need to be adhered to.
Is the use of memcached/Redis (instead of Metermaid for newer deployments) recommended over Metermaid? If so, is it for performance reasons or because Oracle would like to deprecate Metermaid since there are other, third-party technologies which can provide a similar function, etc?
Also, from the Oracle perspective, is there a preferred choice between memcached and redis?
External references for memcached SASL usage:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document