Testing your SSO is as simple as trying to access Eploy using your SSO credentials – if it lets you in, it works. If it doesn’t, something hasn’t been configured properly.
Key things you’ll need to conduct your test:
- A suitable user to test – this can be either a Hiring Manager or Core System User
- The Username field of your user must match the attribute option you selected when configuring the SSO
- Core System users must have a Role assigned to them within Eploy – if you don’t have a Role assigned to your user, you won’t be able to log in (this does not apply to Hiring Managers)
- The login URL for the part of the system you’re trying to log-in to e.g. https://[YOUREPLOYSYSTEMNAME].eploy.net or https://[YOUREPLOYSYSTEMNAME]hm.eploy.net
Things to check if your test fails
If you’ve tried to use your SSO and it’s not worked, there are several possible causes. Here are some common troubleshooting ideas to look at:
- Double-check your SSO provider settings – make sure you’ve configured the Eploy application within your SSO provider correctly. As part of this, you’ll also want to double-check that the user you’re trying to log in as has been added to the permitted user group. Also, double-check that the claim/attribute is set to username (all in lower case), and that the username of the user you’re testing with matches the attribute within your SSO provider (see Check the username field of your test user in Eploy, below)
- Double-check the SSO settings within Eploy – once you’ve checked the settings within your SSO provider, it’s always a good idea to double-check that the required information has been entered into Eploy correctly, including the certificate used
- Have you added SSO settings to the correct user type? – In this guide, we’ve shown you how to add SSO settings for Core System users (Standard Users). If your Hiring Managers will also be accessing Eploy using the same SSO provider, you’ll need to add the same settings within Admin > Security Settings > Hiring Managers
- Check the username field of your test user in Eploy – have you spelt the username correctly? Pay close attention to spaces and special characters. These are valid characters within Eploy e.g. if there’s a space before or after the username, Eploy will assume the space is part of the username. Sometimes, when copying and pasting a username or email address, you can accidentally add a space
- Check the URL you’ve used – is the URL correct? Are you using the correct URL for the user type? The URL for the Hiring Manager portal contains the letters HM just after your system name ([YOUREPLOYSYSTEMNAME]hm.eploy.net). You need to use the correct URL for the user type. Tip if you see the word web, you’re trying to access either the Candidate or Vendor portal!
- Is your user Active? This one is unlikely, especially if you’re still in Implementation, but you never know! If you try to log in using the details of a user who is not active within Eploy, you won’t be able to. There are two things to check. Within the User record in Eploy, look at the Login Access Settings section – if any of this has been filled in, you’ll need to make sure you’re trying to access the system within the confines of these settings, otherwise, you won’t be able to log in. The second thing to check is right down in the bottom left-hand corner of the page – is there a button labelled Activate? If there is, that means your user is not Active and therefore cannot log in. Click Activate then try logging in again
- Have you restricted access to a specific IP address range? If you have, you won’t be able to log in unless your IP Address is within the IP Address Range set. You can check for IP Address restrictions by looking at Admin > Security Settings > Standard Users/Hiring Managers
If you’ve checked all these things and everything appears to be ok, you’ll need to raise it with your Implementation Manager or the Customer Success team (firstname.lastname@example.org) for them to investigate further.