With Single Sign-On (SSO), users can access multiple apps and websites using a single set of credentials. This simplifies the login experience while also strengthening security. Instead of managing separate usernames and passwords, authentication is centralized through the organization’s SSO system.
When Single Sign-On (SSO) is enabled for your organization, it centralizes account authentication by bypassing traditional email confirmation. Instead of a confirmation email, users are authenticated directly through their organization’s SSO system. This streamlined login process eliminates the need for email-based account verification.
To request the transition from a standard login to SSO, reach out to your Account Manager, who will be in charge of supporting you during the procedure.
SSO Activation Procedure
We'll start an exchange of authentication and authorization data between parties (SAML).
Talkpush will share the following data with your IT Team:
Identifier (Entity ID)
Reply URL (Assertion Consumer Service URL)
Your IT Team must share the following data with Talkpush:
IDP SSO Target URL
IDP Certificate
Disclaimer: Make sure the UID configured in your SSO app is the email address of the user; other identifiers (for example, an alphanumeric UID) will not be supported as a valid authentication method.
After the exchange of data, our engineering department will coordinate a meeting with your company's IT team to test in a production or staging environment the success of the activation process.
⚠️ Can't log in to Talkpush while using your SSO app?
To log in to Talkpush using SSO, go to the Talkpush login page, enter your work email address, and follow the SSO authentication steps. Once redirected and authenticated successfully, you gain access to your account without requiring email confirmations.
When trying to log in, you or a teammate may have issues and be redirected to the login screen repeatedly. This can be solved by informing the person in charge of your SSO credentials and ensuring the user's email address is properly included.
If the issue persists, ensure to double-check that you are entering the correct work email address registered in your SSO system. Alternatively, contact your IT team as they manage SSO configurations. They can help update or correct the settings to resolve authentication problems.
Q: Why have I been logged out? A: Logged-in users time out after 72 hours of inactivity. Enabling SSO means you won't receive a confirmation email as authentication occurs directly through your work email credentials.
Q: Can users from my company use different domains? |
