2094153 - Candidate Single Sign-On - Recruiting Execution

SAP Knowledge Base Article - Public

2094153 - Candidate Single Sign-On - Recruiting Execution

Symptom

  • Historically, candidates or external users who utilize Recruiting Marketing (RMK) must create a username and password that is separate from the Applicant Tracking System (ATS) that they are eventually being sent to complete their application process. For candidates, it's confusing to have to manage a login for both the Talent Community as well as for the Applicant Tracking System.
  • For customers who have both Recruiting Management and Recruiting Marketing, a feature called Candidate Single Sign-On can be enabled. This permits candidates who apply for a job with RMK to be carried directly into RCM, their profile already partially setup and ready for them to complete their application. This feature removes not only the confusing double-login procedure, but also removes a full 4 clicks from the job apply process. Furthermore, changes that a candidate makes in one system will be reflected in the other (where applicable--for example, name or email changes).

Environment

  • Recruiting

Resolution

Prerequisites

There are only two configuration prerequisites to enabling this.

  • SSL must be enabled on your RMK site
  • Your instance must be enabled to utilize email as the external applicant user ID
  • Social sourcing for Recruiting Marketing must be enabled
    • Specifically, this means that Jobvite integration must be disabled - you cannot have both Jobvite and Recruiting Marketing enabled at the same time
  • CAPTCHA must be disabled on Recruiting Management
  • The password policy must be modified to match RMK requirements (see below)

 

Candidate Experience and Workflow

Candidate Single Sign-On was created with candidate experience and ease-of-usage between both RCM and RMK. Here's what the workflow would look like for candidates coming to a job on the RMK site.

1.png

Step 1: A candidate finds a job and wants to apply to it. They click the 'Apply Now' button.

2.png

Step 2: A candidate is presented with the choice to either login to their existing account, or alternatively to create a new account. In this instance, they select 'Create' (if they signed in here, they'd be moved to Step 4 below).

3.png

Step 3: The candidate fills out their Talent Community profile, soon to be their RCM Candidate Profile data as well. At this stage, when they select 'Next', their account is then created in the RCM system.

4.png

Step 4: The candidate is brought to the Candidate Profile, with their email address, first and last name pre-populated.

 

Enabling Candidate Single Sign-On

To enable this functionality, please submit a case in the Support portal to begin the process to enable this feature. There are several configuration steps that the SuccessFactors team will need to take to be able to enable this:

  • Configuration changes to both RCM and RMK

Furthermore, there is also a configuration step that you, the RCM/RMK customer, must undertake: the password policy must be modified to reflect these requirements:

  • Minimum Length: 6
  • Maximum Length: 20
  • Maximum Successive Failed Login Attempts: 0 (this needs to be disabled)
  • Password Reset Email: BLANK (does not matter since account lockout is disabled)
  • Case Sensitive (recommended): ENABLED
  • Mixed Case required: DISABLED
  • Non-alpha characters required: DISABLED

Keywords

KBA , sf sso , LOD-SF-RCM , Recruiting Management , How To

Product

SAP SuccessFactors HCM Core all versions