-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Possibility of disabling Redis SSL/TLS certificate validation #15077
Comments
@ovekaaven you can submit a PR with a new configuration option "DisableSSLCertificate" which disables the validation after the parsing. |
Ok, but if I'm supposed to write this myself it might take a while, because in order to test it I'd first have to upgrade our deployment to the newest version of Orchard Core, which probably won't happen right away. But once that happens, I can look at it if nobody else has by then, I suppose. |
@ovekaaven you can use the OC source and configure it to point to your Redis server for testing. Then you can make the change you want and submit a PR after you fix it. This can be done without touching or involving your project. |
I suppose you're right. I've never before tried running Orchard Core directly from its own source tree instead of from a separate project, but it turns out it's not that hard if you choose to build and run the OrchardCore.Cms.Web project within the source directory. Pull request created, hopefully it's OK. |
We'd like to use "Heroku Data for Redis", which offers Redis connections with and without TLS. However, the server certificate is self-signed and the Heroku documentation states you have to disable certificate verification. This can't be done with the connection string, according to StackOverflow answers it can only be done by changing the StackExchange.Redis connection options after parsing but before connecting. But I can't find a way to do that in Orchard Core. Could it be done, or are we stuck with unencrypted Redis connections?
The text was updated successfully, but these errors were encountered: