Ping Identity
Identity security software offering Single Sign-On and Multi-Factor Authentication for large businesses
ABOUT
As an Interaction Designer at Ping Identity, my job is to turn technical requirements into easy and intuitive experiences for two user groups: administrators (our customers) and end-users (our customers’ customers), with a primary focus on the admin interface. I’ve worked on dozens of projects for Ping, mostly focusing on two of their cloud-based products, PingOne for Customers and PingOne for Enterprise. The visual design and UI patterns were mostly established before I began working at Ping, so many of my designs use components and patterns from an existing UI library.
The online identity security world deals with specific technology and language that is often difficult to fully understand as a person new to the industry. This role has challenged and necessitated me to continuously expand my knowledge of our products, competitors, users, and interactions, and has ultimately made me a stronger designer and empathizer.
Below are some of the most challenging and fun projects I’ve worked on. Enjoy!
Drag & drop FLOW MANAGER
Ping Compass
The flow manager is a work in progress and a key new feature for Ping in 2020. Taking on a new design system called Astro, flow manager will live outside of all Ping products but be usable within each product. The need is for our users to be able to build complex policies, such as MFA registration policies. Taking cues from customer interviews and similar products on the market, the flow manager is still very much a work in progress but has started to come together.
Configuring an ldap Gateway
PingOne for Customers
PROJECT overview:
My designs for this project came from a need to allow administrators to migrate user credentials from an external repository into PingOne for Customers. I designed a wizard to walk the user through creating an LDAP Gateway, as well as the “view” screens after a Gateway had been established.
REQUIREMENTS:
Below is an overview of the requirements given to me for this assignment. In total, the requirements were written out in detail in a 4-page Google doc. Because most of this technology was foreign to me, I asked hundreds of questions throughout the design process.
Name
Type of LDAP directory
Information about the servers themselves. We need to support multiple here.
Host & port
If the LDAP connection TLS (aka SSL) & not
If the LDAP connection is TLS, how to determine what TLS certificates are trusted
Trust all certificates (for demo/troubleshooting only)
Trusted TLS certificates
Bind DN & password
Base DN for searching for users
How to correlate a PingOne user with an LDAP user
Simplified : Just select a username attribute
Powerful : LDAP filter where $username$ is dynamically filled in with the username that the user logs in with
DESIGN PROCESS:
My design team has a large Sketch library of UI components and patterns, including the wizard I used for this project. My primary focus on this project was to gain a full understanding of how a user would expect to see the process broken into steps. I did this by asking hundreds of questions to the two Product Managers I was working with, making design changes based on their feedback, reviewing with the PMs, and iterating again. See my final designs below.
ADDING A CUSTOM DOMAIN
PingOne for Customers
project overview:
This feature allows PingOne for Customers admins to replace all standard URLs associated with their Ping account with their own domain name, building a better experience for their customers.
Requirements & design process:
Although the final result of this project is only 15 screens, the requirements changed a handful of times during the design process, taking me through three major iterations before handing off my final mocks.
This project posed a unique challenge. To add a custom domain, the user has to complete 3 steps: 1. add their custom domain, 2. copy and paste a CNAME into their DNS record, and 3. add the SSL certificate. However, between steps 2 and 3, they need to wait an unknown period of time (up to 24 hours) for the changes to their domain configuration to propagate through the internet. This means they need to leave the process and return later to complete it. To complicate it further, it is often three different people completing one step each of the process. Because of this, I knew a traditional wizard wouldn’t work.
SOLUTION:
See below for how I solved this problem.
User clicks “Add Custom Domain”
User types in custom domain
Save button becomes active
Save button turns green and says “Saved” for ~ 1-2 seconds
Modal pops up with instructions for user
If user clicks “Close” out of modal, they are taken to this screen
User is taken to this screen after verifying domain
Modal when user clicks “Add SSL Certificate”
Text field pops out while typing
Custom domain is successfully set up
Branded Sign-On Templates
PingOne for Customers
PROJECT OVERVIEW:
This project allowed me to be more creative than I’m usually able to be, which was a fun change of pace. My PM asked me to create a series of out-of-the-box templates our users could choose from for their sign-on screens. Our users can choose one of the templates, and brand some of the elements: the background image or color, button color, logo etc.
Requirements:
I had to create screens for the following scenarios: Sign-on, Forgot Password, Create Your Profile, Error, Progressive Profiling, Welcome Back, and Social Sign-on. I was not able to change the content on any of the screens.
See below for some samples of my work.
I am happy to share more of my work upon request.