Set up a SAP Cloud Identity connector

C1 provides identity governance and just-in-time provisioning for SAP Cloud Identity. Integrate your SAP Cloud Identity instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

Capabilities

The SAP Cloud Identity connector syncs the following resources:

Resource	Sync	Provision
User
Group

• User: SCIM 2.0 directory users with email, login, status, MFA status, structured name, and SAP-specific profile fields. Supports account create/delete and enable/disable lifecycle actions.
• Group: SCIM 2.0 directory groups with a static member entitlement and membership grant/revoke. SAP classifies groups by type (userGroup, authorization, role, deepLinkActivationPermission, license), surfaced as sap_group_type in the resource profile so access reviewers can distinguish user groups from authorizations and roles.

Additional functionality: The SAP Cloud Identity connector supports automatic account provisioning.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.

Action name	Additional fields	Description
enable_user	user_id (string, required)	Activates a user in SAP Cloud Identity (sets SCIM active=true)
disable_user	user_id (string, required)	Deactivates a user in SAP Cloud Identity (sets SCIM active=false)

Gather SAP Cloud Identity credentials

To configure the SAP Cloud Identity connector, you need administrator permissions in SAP Cloud Identity to create a SCIM technical user with read/write access to Users and Groups.

1. Navigate to the SAP Cloud Identity administration console for your tenant.

2. Create a SCIM technical user (or use an existing one) with access to the Identity Directory SCIM endpoints:

   1. In the admin console create an API credential named C1 (or similar).
   2. Grant it SCIM read/write access to Users and Groups.
   3. Copy the username and password and save them securely.

Configure the SAP Cloud Identity connector

Cloud-hosted

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

1. In C1, navigate to Integrations > Connectors and click Add connector.

2. Search for SAP Cloud Identity and click Add.

3. Choose how to set up the new SAP Cloud Identity 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 C1)
   • Add the connector to a managed app (select from the list of existing managed apps)
   • Create a new managed app
4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Paste the credentials into the relevant fields:

   • Tenant URL: HTTPS base URL of the SAP Cloud Identity tenant (for example https://YOURTENANT.accounts.ondemand.com).
   • SCIM Username: HTTP Basic username for the Identity Directory SCIM API.
   • SCIM Password: HTTP Basic password for the Identity Directory SCIM API.
8. Click Save.

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

Done. Your SAP Cloud Identity connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the SAP Cloud Identity connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Step 1: Set up a new SAP Cloud Identity connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new SAP Cloud Identity 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 C1)
   • Add the connector to a managed app (select from the list of existing managed apps)
   • Create a new managed app
4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. 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 SAP Cloud Identity connector deployment:

Secrets configuration

# baton-sap-cloud-identity-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-sap-cloud-identity-secrets
type: Opaque
stringData:
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  BATON_SAP_CLOUD_IDENTITY_TENANT_URL: <tenant base URL, e.g. https://YOURTENANT.accounts.ondemand.com>
  BATON_SAP_CLOUD_IDENTITY_SCIM_USERNAME: <SCIM API username>
  BATON_SAP_CLOUD_IDENTITY_SCIM_PASSWORD: <SCIM API password>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

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

Deployment configuration

# baton-sap-cloud-identity.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-sap-cloud-identity
  labels:
    app: baton-sap-cloud-identity
spec:
  selector:
    matchLabels:
      app: baton-sap-cloud-identity
  template:
    metadata:
      labels:
        app: baton-sap-cloud-identity
        baton: true
        baton-app: sap-cloud-identity
    spec:
      containers:
      - name: baton-sap-cloud-identity
        image: public.ecr.aws/conductorone/baton-sap-cloud-identity:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-sap-cloud-identity
        envFrom:
        - secretRef:
            name: baton-sap-cloud-identity-secrets

Step 3: Deploy the connector

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

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

Done. Your SAP Cloud Identity connector is now pulling access data into C1.

All versions of this connector are available at dist.conductorone.com.