Azure Redis (with SSL) connection could not be made
See original GitHub issueEE 5.2.3.201810261805
When trying to connect to Azure Redis, the connection fails with:
Could not get a resource from the pool
javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
Connection has been shutdown: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
Connection has been shutdown: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
**the trustAnchors parameter must be non-empty**
the trustAnchors parameter must be non-empty
I’ve used https://www.htbridge.com/ssl/ to check if SSL connection could be established and server cert is without issues. It didn’t find anything wrong with it.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Troubleshooting Azure Redis Connectivity Issues
You can test the connectivity for REDIS for your machine on non-SSL port 6379 and SSL port 6380 using REDIS CLI tool.
Read more >Azure Redis connection failure when using SSL - Stack Overflow
It looks like the JedisConnectionFactory is deprecating some of those fields. Did you remove your RedisStandaloneConfiguration bean entirely? – ...
Read more >Not able to connect Azure Redis cache when SSL = "True ...
In Dot Net MVC web application, in developer code, when we set SSL = "True", Port = "6380", we are not able to...
Read more >Secure SSL Redis connections - ServiceStack Docs
First we'll need a Redis instance to connect to, for this example we will be using Azure, so you will need an active...
Read more >Azure Redis SSL protocol change to TLS 1.2
Azure Redis Cache version TLS change and its effects on Sitefinity. ... Error.log when Sitefinity cannot establish a connection via TLS 1.2 ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It works well if you have client certificate/key:
It also works with just client SSL certificate (private key and CA certificate are optional). But it doesn’t work without certificate at all.
I’m testing with stunnel SSL proxy on server-side.
@jdvor Sorry, missed this ticket. Well, current implementation requires explicit certificate. Self-signed (aka auto-generated) certs are not secure at all (and make whole SSL model senseless). However, in some cases it is necessary (e.g. when SSL is the only way to connect and you don’t have a client certificate).
Anyway, please create a feature request for self-signed SSL certificates support for Redis.