[ https://issues.apache.org/jira/browse/DRILL-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634155#comment-17634155 ]
ASF GitHub Bot commented on DRILL-8357: --------------------------------------- jnturton commented on PR #2705: URL: https://github.com/apache/drill/pull/2705#issuecomment-1314766932 > I had question about the token and cookie? Are these fields something that we'd expect to be set in a config, or are they something that should be somehow populated dynamically? This seemed strange to me. I thought they might be set in the config _and_ dynamic i.e. the user's application obtains a token or cookie from Splunk and then updates the Drill config with it using the Drill REST API. Or in the config and static if the user [has gone to Splunk Web for a token](https://docs.splunk.com/Documentation/Splunk/latest/Security/CreateAuthTokens#Use_Splunk_Web_to_create_authentication_tokens) that lives for a long enough time that doing this would make sense. > Add new config options to the Splunk storage plugin > --------------------------------------------------- > > Key: DRILL-8357 > URL: https://issues.apache.org/jira/browse/DRILL-8357 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - Other > Affects Versions: 1.20.2 > Reporter: James Turton > Assignee: James Turton > Priority: Minor > Fix For: 2.0.0 > > > The following five new options can be added to the Splunk storage config. > {code:java} > // Whether the Splunk client will validates the server's SSL cert. > private final boolean validateCertificates; > // The application context of the service. > private final String app; > // The owner context of the service. > private final String owner; > // A Splunk authentication token to use for the session. > private final String token; > // A valid login cookie. > private final String cookie;{code} -- This message was sent by Atlassian Jira (v8.20.10#820010)