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

Connecting to "Secure" Redis #419

Open
whigley opened this issue May 22, 2020 · 3 comments
Open

Connecting to "Secure" Redis #419

whigley opened this issue May 22, 2020 · 3 comments

Comments

@whigley
Copy link

whigley commented May 22, 2020

What is the URL to use the session manager to connect to secure AWS ElastiCache Redis

className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
memcachedNodes="redis://master.secure-xxxxxxxxxxxx:6379"
sticky="true"
enabled="true"
sessionBackupAsync="false"
requestUriIgnorePattern=".*.(ico|png|gif|jpg|css|js)$"
storageKeyPrefix="context.hash,webappVersion"
transcoderFactoryClass="de.javakaffee.web.msm.serializer.kryo.KryoTranscoderFactory"

I tried using "rediss://" instead of "redis://" ... but no luck.

It works fine with non-secure redis node

@LLY-SC
Copy link

LLY-SC commented Nov 7, 2023 via email

@pawelpytelpoznan
Copy link

Hi,
for me it's working with pattern as below:
redis://:{password}@{ip_address}:{port}
https://github.com/redis/lettuce/wiki/Redis-URI-and-connection-details

Security concern:

@magro but there is one huge security concern then - the MemcachedSessionService logs this secure data in INFO log, from startInternal method
_log.info( getClass().getSimpleName() + " starts initialization... (configured" + " nodes definition " + _memcachedNodes + ", failover nodes " + _failoverNodes + ")" )

This memcachedNodes variable contains senstiive data. Could we somehow overcome this issue?

@LLY-SC
Copy link

LLY-SC commented Sep 30, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants