# SAP SuccessFactors

<!-- BEGIN GENERATED:intro -->

The SAP SuccessFactors connector is a [Palantir-provided driver](../../data-integration/foundry-provided-drivers/index.md) for SAP SuccessFactors.

To create a new SAP SuccessFactors source, follow the [standard setup flow for Palantir-provided drivers](../../data-integration/foundry-provided-drivers/index.md#setup), then use the sections below for SAP SuccessFactors-specific configuration and networking. For the complete property reference, see the [official SAP SuccessFactors driver documentation ↗](https://cdn.cdata.com/help/GBK/jdbc/pg_connectionj.htm).

<!-- END GENERATED:intro -->

<!-- BEGIN GENERATED:capabilities -->

## Supported capabilities

| Capability | Status |
|---|---|
| Exploration | 🟢 Generally available |
| Batch syncs | 🟢 Generally available |
| Incremental | 🟢 Generally available |
| [OAuth 2.0 authentication](#oauth-20-authentication) | 🟢 Generally available |
| [Table exports](#table-exports) | 🟢 Generally available |

<!-- END GENERATED:capabilities -->

<!-- BEGIN GENERATED:configuration -->

## Configuration

The properties below are mandatory or recommended.

| Property | Required? | Description | Default |
|---|---|---|---|
| [`AuthScheme` ↗](https://cdn.cdata.com/help/GBK/jdbc/RSBSAPSuccessFactors_p_AuthScheme.htm) | Mandatory | The type of authentication to use when connecting to SAP SuccessFactors. | `Basic` |
| [`CompanyId` ↗](https://cdn.cdata.com/help/GBK/jdbc/RSBSAPSuccessFactors_p_CompanyId.htm) | Mandatory | Unique identifier of your company. This is required to authenticate. | — |
| [`URL` ↗](https://cdn.cdata.com/help/GBK/jdbc/RSBSAPSuccessFactors_p_URL.htm) | Mandatory | Set this to the URL of the server where your SAP SuccessFactors instance is hosted. | `https://api2.successfactors.eu` |
| [`InitiateOAuth` ↗](https://cdn.cdata.com/help/GBK/jdbc/RSBSAPSuccessFactors_p_InitiateOAuth.htm) | Recommended | Specifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working. | `REFRESH` |
| [`OAuthClientId` ↗](https://cdn.cdata.com/help/GBK/jdbc/RSBSAPSuccessFactors_p_OAuthClientId.htm) | Recommended | Specifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. | — |
| [`OAuthClientSecret` ↗](https://cdn.cdata.com/help/GBK/jdbc/RSBSAPSuccessFactors_p_OAuthClientSecret.htm) | Recommended | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server. | — |
| [`Password` ↗](https://cdn.cdata.com/help/GBK/jdbc/RSBSAPSuccessFactors_p_Password.htm) | Recommended | Specifies the password of the authenticating user account. | — |
| [`User` ↗](https://cdn.cdata.com/help/GBK/jdbc/RSBSAPSuccessFactors_p_User.htm) | Recommended | Specifies the user ID of the authenticating SAP SuccessFactors user account. | — |

<!-- END GENERATED:configuration -->

<!-- BEGIN GENERATED:networking -->

## Networking

The table below lists the domains that the source must be able to access to run.

For each domain, add a corresponding [egress policy](../../administration/configure-egress/index.md). If the source is hosted on-premises and not directly reachable from Foundry, use an [agent proxy egress policy](../../administration/configure-egress/index.md#agent-proxy-egress-policies) instead. The agent host itself must also be able to reach the listed domains. See [using an agent as a proxy](../../data-connection/agent-proxy/index.md) for details.

| Domain  | Required |
|--- |--- |
| \<URL> | Always. URL connection property |

<!-- END GENERATED:networking -->

<!-- BEGIN GENERATED:oauth -->

## OAuth 2.0 authentication

This connector supports OAuth 2.0 authentication. Follow the [OAuth 2.0 guidance for Palantir-provided drivers](../../data-integration/foundry-provided-drivers/index.md#oauth-20-authentication) to configure and authorize the connection.

<!-- END GENERATED:oauth -->

<!-- BEGIN GENERATED:table-exports -->

## Table exports

This connector supports table exports. Learn how to [set up a table export](../../data-connection/export-overview/index.md#table-exports).

<!-- END GENERATED:table-exports -->