Dear Support,
We use X509 certificates provided by our customer certificate authority, in order to use HTTPS protocol for web pages and to encrypt the communication between instances in TLS 1.2.
- Modification of the file /opt/splunk/etc/system/local/web.conf for the Web Pages
- Modification of the file /opt/splunk/etc/system/local/server.conf for the encryption of the communication between the instances
If these certificates are expired, can you tell us if an issue is expected or if the solution will still work in a degraded mode, with warning messages indicating that the certificates are expired?
Thank you in advance for your answer.
BR
Malik GHALEB
This is not Splunk Support. Splunk Support is a service you pay for.
This is a community forum. We share knowledge out of our own free will.
Ok, we got this out of the way.
If you have a certificate installed for the web server it's up to the client who connects to the server to decide whether he wants to connect to a server which presents an invalid certificate or not.
There is an option for server.conf and outputs.conf called sslVerifyServerCert but I'm not sure if it disables expiry verification or only name/CA verification.
Anyway, you don't want expired certificates. Keep your environment current and secured.
For TLS if the certificate expires you will not get data sent.
This is not Splunk Support. Splunk Support is a service you pay for.
This is a community forum. We share knowledge out of our own free will.
Ok, we got this out of the way.
If you have a certificate installed for the web server it's up to the client who connects to the server to decide whether he wants to connect to a server which presents an invalid certificate or not.
There is an option for server.conf and outputs.conf called sslVerifyServerCert but I'm not sure if it disables expiry verification or only name/CA verification.
Anyway, you don't want expired certificates. Keep your environment current and secured.