You can have different SAML and JSON Web Token (JWT) SSO methods for agents and end users. Each group will have their own remote login pages; however, the authentication method is not segregated. Agents and end users can authenticate by either method because they are both configured to use SSO.
Zendesk redirects unauthenticated users when they click the Sign in link in Help Center or navigate directly to the sign-in page in Zendesk.
Note that Zendesk can only redirect unauthenticated users to one of the two remote login pages. The redirect URL that Zendesk uses is the remote login URL of the SSO method you configure last in Admin Center. For example, if you configure JWT SSO for end users first and SAML SSO for staff members (agents, admins) second, then Zendesk uses the SAML remote login URL to redirect users. For the best customer experience, you should configure the SSO method for end users last to ensure they get the benefit of the redirect.
The group that must use the other remote login page must navigate to it on their own. Make sure to provide them with the URL. Another solution is asking your web team to add a link on the redirect login page that the group can use to access their login page.
Although Zendesk implements both methods, when you view the security pages for Team members and End users, the last configured method will appear for both agents and end users. This is because Zendesk redirects both groups to that method's remote login page.
Example set up
In Admin Center, you set up SAML SSO for your agents first and JWT SSO for your end users second. The JWT remote login page for end users is your company's customer login page. The SAML remote login page for agents is your corporate employee login page.
Although SAML SSO is enabled for Zendesk agents, when you review the authentication settings in Admin Center, JWT appears as the authentication method for both end users and agents. Zendesk redirects both groups to the same JWT remote login page.
End users who try to sign in through your Help Center are redirected to the JWT login page -- your company's customer login page. After signing in, they're redirected back to your Help Center.
Agents who try to sign in through your Help Center are also redirected to the customer login page. From there, they can click an I am an agent link directing them to the corporate employee login page. Your web team is responsible for adding the I am an agent link to the customer login page.
9 Comments
What would those URL be for SAML or JWT respectively?
You can also update the article with that you have now implemented a link to switch which method is "Primary".
Hi Niclas Kårlin! In this case, the URL in question would be the remote login for the "non-primary" method. I'll flag this article to be updated with the new functionality, thanks for mentioning this!
This functionality seems broken. Whatever is the primary SSO method is the only one that works. If JWT is primary, then it's the only one that seems to work. I can't even do IDP-initiated SSO without Zendesk redirecting to whatever is primary.
I'm trying to use Azrure AD for agents and JWT for customers. But when I make JWT the primary, there's no way for my agents to log in with Azure. The same is true vice versa. Any suggestions?
Hey Frank,
It looks like you have a ticket open with our Customer Care team related to this issue and they're currently investigating to find a solution. Once they have more information they will follow-up with you in the ticket.
Thanks for taking the time to share this with us!
Cheers!
We're having similar problems setting this up as the the advice listed here doesn't seem to work for us either.
It seems that whatever method is set as primary takes precedent, even if you try and navigate to the login url that isn't the primary, it still redirects you to whichever happens to set as primary at the time. Is this actually working for anyone?
Hey Brett Bowser,
We have a case where we're using JWT for customers and SAML for agent. What we're expecting is, when we register a new end-user, the user gets a verification link. when this verification url is accessed, It does not take the user to be verified, but asks the user to login to my SAML configured SSO page. (Also, my SAML is the primary SSO ) .
How do I avoid this get my user to verify normally and create a new password to access zendesk?
Hi Milton,
I will create a ticket from your comment so that our team can take a closer look at your issue.
Hi Raghav,
When a user is added to a Zendesk account, an automatic email notification will be sent to the user. Because they're authenticated with a non-Zendesk password, the profile is created without a password because they don't need to sign in to Zendesk. Since you've set up external authentication and the users don't use Zendesk credentials to sign in, to avoid any confusion, we recommend to:
- In the Account emails section, deselect Also send a welcome e-mail when a new user is created by an agent or admin
- In Allow users to change their passwords, deselect this option.
Its been half a year since this was updated, so what is the URL to get a valid saml SAMLRequest token when JWT is primary?
Please sign in to leave a comment.