You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When creating the service, do we support submitting the SSL certificate so we can satisfy with requireClientCert?
When enabled, the third party connecting to splunkd must present a valid certificate:
requireClientCert =
Whether or not an HTTPS client which connects to a splunkd
server must possess a certificate that a certificate authority
signed to complete the connection.
Multiple services can use this setting, including but not
limited to distributed search and distributed deployment clients.
Splunk platform indexers must use this setting to connect to
other Splunk platform indexers.
Deployment clients must present certificates to deployment
servers before they can poll the servers for new configurations
or applications.
A value of "true" means that a client can connect only if it
has a certificate that was signed by a certificate
authority that the splunkd server trusts.
A value of "false" means that there is no certificate requirement
to connect to services on another Splunk platform instance.
Default: false
I have found the following issue from some years ago:
Is your feature request related to a problem? Please describe.
When creating the service, do we support submitting the SSL certificate so we can satisfy with requireClientCert?
When enabled, the third party connecting to splunkd must present a valid certificate:
requireClientCert =
server must possess a certificate that a certificate authority
signed to complete the connection.
limited to distributed search and distributed deployment clients.
other Splunk platform indexers.
servers before they can poll the servers for new configurations
or applications.
has a certificate that was signed by a certificate
authority that the splunkd server trusts.
to connect to services on another Splunk platform instance.
I have found the following issue from some years ago:
#123
Describe the solution you'd like
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: