Splunk Cloud Platform

Use Ingest Processors

Manage users for the Ingest Processor solution

The Ingest Processor service is accessed from your Splunk Cloud Platform deployment and uses an identity provider for single sign-on (SSO). As a result, use the same login credentials as the Splunk Cloud Platform deployment.

If you configured Splunk Cloud Platform to use another service as the identity provider for single sign-on (SSO), then use your SSO credentials when logging in to the tenant.

All of the users on that Splunk Cloud Platform deployment can access the Ingest Processor service and view the general user interface. However, if a user's account does not have the necessary capabilities, then they cannot view, create, update, or delete resources such as pipelines, destinations, and source types. To allow a user to make full use of the Ingest Processor solution, you must grant them the admin_all_objects capability in your Splunk Cloud Platform deployment.

See Define roles on the Splunk platform with capabilities in the Securing Splunk Cloud Platform manual for more information.

See Invite users in the Splunk Cloud Console manual for more information on adding users to your Splunk Cloud platform deployment.

Last modified on 20 August, 2024
First-time setup instructions for the Ingest Processor solution   System requirements for Ingest Processor

This documentation applies to the following versions of Splunk Cloud Platform: 9.1.2308, 9.1.2312, 9.2.2403, 9.2.2406 (latest FedRAMP release)


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters