Eploy’s candidate portals are enhanced by using either:

• a custom careers focussed root domain whether that be an existing or new one e.g. yourcompanycareers.com
• a subdomain e.g. careers.yourcompany.com
• a subfolder of your website (via reverse proxy), whether it be a corporate site or dedicated careers site. E.g. yourcompany.com/careers

Your candidates, in effect ‘stay’ on one of your domains and are not being transferred to an unknown domain (i.e. an Eploy domain).

Which option you opt for will depend on a few different factors. It’s important to consider how you will ‘route’ traffic to your candidate portal. Details of the options and use case examples are below.

It’s important to note the following when making your choice:

• Your Agency (Vendor) Portal will also run in a folder of the same domain
• Your Hiring Manager Portal will run on a separate Eploy domain (independent of your Core System).
• If your careers site is already using a subdomain, then Eploy can either run on your current sub-domain, if the whole careers site and all content will be replaced with an Eploy powered version. Or, if you will be keeping content on your existing site, you can have Eploy running on a different subdomain. For example, if your careers site currently uses https://careers.yourcompany.com then Eploy could use: https://apply.yourcompany.com

Your Implementation Manager will be happy to discuss the options with you and offer guidance on best practice based on your requirements.

Root Domain

If your Candidate Portal will be using a root domain, you will need to do the following:

• Add an A Record on the DNS with the target set to your Eploy system IP address (*Eploy will provide the details to you).
• Add a  CNAME Record on the DNS for the www. version of the domain. This will create a subdomain that Eploy will use for Cloudflare, e.g. www.customer.com The target should be set to your Eploy system URL (your Implementation Manager will provide this to you). An example of this would be: customerwebeploy.net
• Provide an SSL in Eploy or use Let's Encrypt (see the section on SSLs).

Subdomain

If your Candidate Portal will be using a subdomain, you will need to do the following:

• Add a CNAME record on the DNS – the name will be the subdomain (e.g. careers.company.com). The target should be set to your Eploy system URL (your Implementation Manager will provide this to you). An example of this would be: customerwebeploy.net
• Provide an SSL in Eploy (this can be an SSL for the subdomain or a wildcard) (see the section on SSLs) or use Let's Encrypt.

Subfolder (Reverse Proxy)

If your Candidate Portal will be using a subfolder, you will need to do the following:

• A reverse proxy needs to be running on the root domain and forward subfolder requests to Eploy. How this is achieved depends on what you are using (e.g. Akamai/Nginx/Apache mod_proxy/IIS URL Rewrite)
• Set the Edge Hostname - your Eploy Implementation Manager will provide this to you.
• Set the Forward Host Header - your Eploy Implementation Manager will provide this to you.

If when clicking around the site you end up back on an eploy.net domain then this is not setup correctly. Places to test for this are:

• Sign In → Register for Account. 
• Single Sign In → Linked In → Cancel. 
• Try to upload a cloud file. This won't work at all.
• Try to select rows in a grid in the clientarea, if they select fine then it works.

Note: Each of these is a different test, if all 3 of these work then the Forward Host Header has been set up correctly. One common mistake is that instead of setting the Forward Host Header up you setup a hard replace on all content for systemnameweb.eploy.net to yourcompany.com. This will not work where Eploy encrypts the URL in links - such as with Single Sign On.

• Ensure that the eploy.net SSL certificate is trusted (please be aware that this will change as we renew it). Please ensure you do not hardcode a specific SSL.

Example Config Issues with Proxy Software

Additionally, you may need to check and/or configure the following if using these:

IIS                    IIS URL Rewrite must be installed. In IIS settings under "Application Request Routing" make sure that "Reverse rewrite host in response header" is unchecked. If there is no Application Request Routing option, install the extension. Create an empty folder for the subfolder being used. IIS will error without this. Make sure the presrveHostHeader setting is set to “true”. To stop proxy errors the following registry key needs to be set SECURITY_FLAG_IGNORE_CERT_CN_INVALID (0x00000100)

Apache           mod_proxy – set ProxyPreserveHost to Yes

Nginx              proxy_set_header Host to your root domain (e.g. yourcompany.com)

Issues with Content Management Systems (CMS)

Please let us know what CMS you are using. For instance, there are some known issues with Umbraco. You will also need to make sure you have the subfolder listed in the Umbraco config option: umbracoReservedPaths