Single Sign-On (SSO) Configuration
What is SSO and why should you use it?
Single Sign-On (SSO) is an authentication mechanism that allows users to access multiple independent applications and systems using the same central set of login credentials (e.g., a corporate Microsoft Azure AD, Google Workspace, or Okta account).
Implementing SSO in CustomerHero brings three key benefits:
Convenience for users: Your team members don't need to create or remember another password for a new system. Logging in is instant, often requiring just a single click.
Increased security: The risk of using weak or reused passwords is reduced. The entire authentication process takes place entirely on the side of your trusted identity provider.
Easier management (IT): Administrators in your company can conveniently manage employee access from one place (e.g., automatically revoking access to all tools, including CustomerHero, when an employee leaves the company).
OIDC Integration in CustomerHero
We base authorization integration in CustomerHero on the modern and secure OIDC (OpenID Connect) standard. The implementation process requires close collaboration with your IT department or identity system administrator.
Below you will find information on how to set up this connection step by step.
Data needed to set up the connection
To start the configuration on the CustomerHero side, we need your company to generate and provide three key parameters from your Identity Provider:
Discovery endpoint (URL address containing the
.well-knownconfiguration)Client ID
Client Secret
Step-by-step configuration process
Step 1: Secure data transfer
Send the collected configuration data to our support team at contact@customerhero.com.
Important (Security Rules): To maintain the highest security standards, please appropriately secure all data before sending. Do not send parameters (especially the Client Secret) in plain text in an email. Use secure transfer channels, such as single-use, encrypted links (e.g., One-Time Secret, Bitwarden Send, a corporate password manager) or send the data in a password-protected ZIP archive (providing the password via a separate channel).
Step 2: Receiving the Redirect URI and login link
After processing your request, the CustomerHero team will generate and send you two key pieces of information in a reply:
Redirect URI – pass this to the person responsible for SSO system administration in your company; it will be necessary to finalize the configuration on your side.
Dedicated SSO login link – a unique address through which your team will access the platform.
Step 3: Test login
Once the settings on both sides (CustomerHero and your identity provider) are implemented, you must use the previously received dedicated link to perform a test. The verification is conducted on a selected user from your package to ensure that data mapping and authorization proceed smoothly.
Step 4: Providing access to the team
After successfully completing the test login, the integration process is finalized. From this moment on, you can safely share the dedicated link with your team, enabling them to log in to CustomerHero with a single click using their corporate credentials.