Set up a SAP SuccessFactors connector

Capabilities

Resource	Sync	Provision
Accounts
Groups

Gather SuccessFactors credentials

Configuring the connector requires you to pass in credentials generated in SuccessFactors. Gather these credentials before you move on.

An administrator with the ability to Manage OAuth2 Client Applications in SuccessFactors must perform this task.

Grant the admin user the necessary permissions

Give the admin user who will configure the connector the necessary Manage Identity Account and Group permissions.

Navigate to Admin Center > Manage Permission Groups.

Create a new permission group that includes the admin user.

Next, navigate to Manage Permission Roles and create a new permission role.

Give the permission role the following Manage Identity Account and Group permissions:

Read Access to SCIM User API
Read Access to SCIM Group API
Edit Access to SCIM Group API for Membership Assignment

Assign the newly created permission role to the permission group you created.

You’ll also need the User ID of the admin user when configuring the connector.

Look up your company ID

Navigate to your profile menu and select Show version information.

Carefully copy and save the Company ID.

Look up your instance URL

Refer to the SAP SuccessFactors documentation and look up your API server.

Carefully copy and save the API server URL.

Register an OAuth2 client application and generate an API key

In SuccessFactors, navigate to Admin Tools > Manage OAuth2 Client Applications and click Register Client Application.

Fill out the form, providing:

Application name, such as “ConductorOne Connector”.
Application URL, such as https://www.conductorone.com/. Carefully copy and save this URL, it will be used later as the Issuer URL when setting up the connector.
X.509 Certificate. Make sure to create, sign, and upload your own certificate, as certificates generated by SAP SuccessFactors cannot be used by the connector. When uploading a self-generated certificate, remove the lines -----BEGIN CERTIFICATE----- and -----END CERTIFICATE-----.

Click Register.

Click Edit in the list of registered applications to view the new application’s API key.

Carefully copy and save the API key. When setting up the connector, you’ll use this API key as both the Client ID and the SAML API key.

That’s it! Next, move on to the connector configuration instructions.

Configure the SuccessFactors connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of SuccessFactors credentials generated by following the instructions above

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

In ConductorOne, navigate to Admin > Connectors and click Add connector.

Search for SuccessFactors and click Add.

Choose how to set up the new SuccessFactors connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

Click Next.

Find the Settings area of the page and click Edit.

In the Company ID field, enter your SuccessFactors company ID.

In the Client ID field, enter the API key.

In the Public key and Private key fields, enter these credentials.

In the Instance URL field, enter your API server URL.

In the Issuer URL field, enter the application URL used to set up the OAuth2 application.

In the Subject name ID field, enter the user ID of the admin user that will be added to the SAML subject.

In the SAML API key field, enter the API key a second time.

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your SuccessFactors connector is now pulling access data into ConductorOne.

Follow these instructions to use the SuccessFactors connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Set up a new SuccessFactors connector

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Click Next.

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your SuccessFactors connector deployment:

Secrets configuration

# baton-successfactors-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-successfactors-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # SuccessFactors credentials
  BATON_CID: <SuccessFactors client ID (use the SAML API key for this value)> 
  BATON_COMPANY_ID: <SuccessFactors company ID> 
  BATON_SUBJECT_NAME_ID: <SuccessFactors subject name ID>
  BATON_PRIVATE_KEY: <SuccessFactors private key>
  BATON_PUBLIC_KEY: <SuccessFactors public key>
  BATON_SAML_API_KEY: <SuccessFactors SAML API key> 
  BATON_INSTANCE_URL: <SuccessFactors domain, such as https://successfactorsserver.com>
  BATON_ISSUER_URL: <SuccessFactors SAML Issuer URL, such as https://www.conductorone.com/> 

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-successfactors.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-successfactors
  labels:
    app: baton-successfactors
spec:
  selector:
    matchLabels:
      app: baton-successfactors
  template:
    metadata:
      labels:
        app: baton-successfactors
        baton: true
        baton-app: successfactors
    spec:
      containers:
      - name: baton-successfactors
        image: ghcr.io/conductorone/baton-successfactors:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-successfactors
        envFrom:
        - secretRef:
            name: baton-successfactors-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the SuccessFactors connector to. SuccessFactors data should be found on the Entitlements and Accounts tabs.

That’s it! Your SuccessFactors connector is now pulling access data into ConductorOne.

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Set up a SAP SuccessFactors connector

Capabilities

Gather SuccessFactors credentials

Grant the admin user the necessary permissions

Look up your company ID

Look up your instance URL

Register an OAuth2 client application and generate an API key

Configure the SuccessFactors connector

Step 1: Set up a new SuccessFactors connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

​Capabilities

​Gather SuccessFactors credentials

​Grant the admin user the necessary permissions

​Look up your company ID

​Look up your instance URL

​Register an OAuth2 client application and generate an API key

​Configure the SuccessFactors connector

​Step 1: Set up a new SuccessFactors connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather SuccessFactors credentials

Grant the admin user the necessary permissions

Look up your company ID

Look up your instance URL

Register an OAuth2 client application and generate an API key

Configure the SuccessFactors connector

Step 1: Set up a new SuccessFactors connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector