11/18/2023 0 Comments Splunk login urlYou can configure the platform with settings that are specific to your IdP. The Splunk platform supports many different types of identity provider for logins that use SAML for authentication. XML and manage the Duo Multifactor configuration.You can configure the Splunk platform to use the Security Assertion Markup Language (SAML) as an authentication scheme for single sign-on (SSO), using information that your SAML identity provider (IdP) supplies. If sslVerifyServerCert is true, this path must be provided to ensure successful certificate validation. If set to true, provide a sslRootCAPath to ensure successful certificate validation.įull path of the certificate to be used for certificate verification. Defaults to Splunkd useClientSSLCompression.īoolean that indicates if Duo server certificate verification is required. Boolean indicating if client side SSL compression is enabled. Alternate name to verify if sslVerifyServerCert is true. Common name to verify if sslVerifyServerCert is true. Full path of the certificate to be used for certificate verification. If set to true, provide a sslRootCAPath to ensure successful certificate validation. Indicates if Duo server certificate verification is required. ECDH curve value to use for accessing the Duo REST API. Cipher suite to use for accessing the Duo REST API. SSL version to use for accessing the Duo REST API. Positive integer indicating the Duo connection timeout, in seconds, for declaring the Duo service unavailable. Indicates whether Splunk should bypass the Duo service if it is unavailable. Must be a random generated hex of length 40 or more. Duo REST API endpoint used by Splunk for multifactor authentication Shared secret key between Splunk and Duo. home/mkandaswamy/git/splunkApp/etc/auth/DigiCertHighAssuranceEVRootCA.pem $1$A3t8AvuwwoDzSgUgB1x50FesOpd0ZKBWaHR5xY6uqWeaB02vsuFh4KQ= $1$cQdFd4+XlOrAfgBgQEwe+VevD/MOOfFTIA4vwoaFnCX0V0TO8ZsCsKQ= Defaults to Splunkd useClientSSLCompression. Defaults to false.įull path of the certificate to be used for certificate verification if sslVerifyServerCert is true.Ĭommon name to verify if sslVerifyServerCert is true.Īlternate name to verify if sslVerifyServerCert is true.īoolean indicating if client side SSL compression is enabled. Defaults to Splunkd ecdhCurves.īoolean indicating if Duo server certificate verification is required. Defaults to Splunkd cipherSuite.ĮCDH curve value to use for accessing the Duo REST API. Defaults to Splunkd sslVersion.Ĭipher suite to use for accessing the Duo REST API. Must be a random generated hex of length 40 or more.īoolean indicating whether Splunk should bypass the Duo service if it is unavailable. Shared secret key between Splunk and Duo.ĭuo REST API endpoint used by Splunk for multifactor authentication Duo only works with local auth types.ĭuo integration key for Splunk. Requires the change_authentication capability.ĭisable any SSO configurations, such as SAML, before enabling Duo authentication for the first time. See Access requirements and limitations for the Splunk Cloud Platform REST API in the REST API Tutorials manual for more information.Ĭonfigure Duo Multifactor authentication. Free trial Splunk Cloud Platform accounts cannot access the REST API. If necessary, submit a support case using the Splunk Support Portal to open port 8089 on your deployment. Use the following URL for Splunk Cloud Platform deployments. Splunk Cloud Platform has a different host and management port syntax than Splunk Enterprise. Splunk Cloud Platform URL for REST API access For more information about specifying a namespace, see Namespace in the REST API User Manual. Typically, knowledge objects, such as saved searches or event types, have an app/user context that is the namespace. To determine the capabilities assigned to a role, select Settings > Access controls and click Roles. To view the roles assigned to a user, select Settings > Access controls and click Users. Users with an administrative role, such as admin, can access authorization information in Splunk Web. Splunk users must have role and/or capability-based authorization to use REST endpoints. Username and password authentication is required for access to endpoints and REST operations. For more information see Access Control List in the REST API User Manual. To check Access Control List (ACL) properties for an endpoint, append /acl to the path. Usage details Review ACL information for an endpoint
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |