(12%)|Latest Update Graded A+
You want to give your end users an authentication option that doesn't require them to create a new
password, but you don't have the resources for a custom single sign-on (SSO). What can you do?
You can use Zendesk's native option with social login, allowing users to authenticate their identity by
logging onto their Twitter, Facebook, Google, or Microsoft accounts. Providing additional sign-in
choices tends to improve the user experience because it makes the process seamless. Instead of
creating a password before they move on, end users can simply use one of their social accounts to
continue with their activity.
What is the Team member authentication
options?
Team member authentication
(1) Zendesk authentication: Team members will sign in with an email and password.
Zendesk recommends keeping Zendesk authentication active as a backup. End users will have another
way to sign in if external authentication goes down. Learn about external authentication downtime.
(2) External authentication: Team members can sign in using third-party services.
- Microsoft
- Single Sign-on > Select one or more SSO methods for end users. The Single sign-on page is where you
create and manage these configurations. Go to the Single sign-on page. When you use SSO, you must
verify your identity and email address.
What are the SSO Methods?
SSO METHODS: SAML and JSON Web token >If I select both methods, I can set a Primary Method!
Security Assertion Markup Language (SAML) is an open standard for exchanging credentials and user
information with an identity provider.
JSON Web Token is an open standard that uses a shared secret to encrypt credentials and user
information.
What are the End users authentication
options?
(1) Zendesk authentication: Team members will sign in with an email and password.
(2) Social login
End users can sign in with Social accounts
- Microsoft
(3) External authentication
End users can sign in using third-party services: SSO