Splunk turns to Ping Identity

Splunk has selected Ping Identity to provide its customers with simple and secure access to the Splunk customer portal.

  • Thursday, 21st November 2013 Posted 11 years ago in by Phil Alsop

Customer service is a priority at Splunk. To better serve Splunk’s more than 6,000 customers, the company launched a single sign-on initiative to simplify access to all of its web properties and cloud-based apps, including a support portal on Salesforce.com Service Cloud. To eliminate multiple login requests from the individual applications inside the portal, Splunk selected Ping Identity to provide secure, standards-based single sign-on and identity federation. Now every Splunk customer has one-click access to the portal without ever exposing their identities or passwords to third-party vendors.


“Our customer portal has to be a seamless extension of the Splunk experience. After a customer logs in, one-click access to all the portal’s resources and apps is a must,” said Christopher Nelson, senior director of IT business applications, Splunk. “Now we have a continuous user interface, while maintaining tight security. And, because Ping Identity does not store passwords and identities, our customer information never leaves the Splunk environment – another requirement of the Splunk experience.”


In under a week, Ping Identity was able to implement a SAML-based SSO connection from Salesforce.com Service Cloud Portal to Splunk’s customer portal. The identity bridge eliminates the need to log in to multiple applications in order to open a customer ticket or access the Splunk help desk.
“Splunk is a great example of a customer that needed an enterprise-grade, identity security solution to address the increasingly complex interplay between cloud applications and identities,” said Loren Russon, vice president of product management and design for Ping Identity. “We responded with a solution that was fast to implement, cost-effective and secure. And that will easily scale with future identity and access management requirements.”