TIBCOSoftware / TIBCOSoftware/be-contribution
BE cannot use one-way SSL with Redis Store.
Open
@kagrawal-tibco is already working on this.
Since Jan 29, 2021.
- Dominant language
- Java
- Stars
- 0
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Version Information
| Software | Version(s) |
|---|---|
| BusinessEvents | 6.1.0 |
| OS Type? | Linux |
What is the expected behavior?
The Redis server should be configurable with one-way ssl.
What is the actual behavior?
It is not working as per steps mentioned in Redis documentation (https://redis.io/topics/encryption).
It seems that currently BE can only use two-way SSL with Redis.
Please provide a unit test that demonstrates the bug.
- Start Redis server with SSL certifictes and pass parameter 'tls-auth-clients no' in the command as shown below :
redis-server --tls-port 6379 --port 0 --tls-cert-file ./tests/tls/redis.crt --tls-key-file ./tests/tls/redis.key --tls-ca-cert-file ./tests/tls/ca.crt --loadmodule redisearch.so - Start Redis-cli with wrong cert or key ---> The cert/key should be ignored and connection should be fine but here redis-cli fails to connect as shown below :
redis-cli --tls --cert ./tests/tls/redis2.crt --key ./tests/tls/redis.key --cacert ./tests/tls/ca.crt
Could not negotiate a TLS connection: Invalid client certificate
Other notes on how to reproduce the issue?
https://github.com/redis/redis/issues/7437
Refer this for more info ---> https://github.com/bitnami/bitnami-docker-redis-cluster/issues/5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.