---
schema_version: "1"
id: ec59aa868ff76d3ae2b764e09cd3dd8bfb3c1dce19b3319f6f8ffb7ea0d222b5
title: SAP SuccessFactors 5.0 - Additional Configuration Information
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/sap-successfactors-connector/latest/sap-successfactors-connector-config-topics.md
canonical_url: https://docs.mulesoft.com/sap-successfactors-connector/latest/sap-successfactors-connector-config-topics
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 5dfa33579c124633ef614e3cf5460b6ab8168d484c18ea214ff63595f41acb6b
description: MuleSoft Documentation Site
release: "5.0"
latest: true
---
---
product: SAP SuccessFactors Connector
version: 5.0
is-latest-version: true
---

# SAP SuccessFactors 5.0 - Additional Configuration Information

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Perform additional configuration for Anypoint Connector for SAP SuccessFactors (SuccessFactors
Connector), such as using a query as a filter.

## Use a Query as a Filter

To configure the **Query** operation to perform queries over entities of a specified type, follow
these steps:

1.  Select the **Query** operation on the canvas.

2.  In the **General** properties tab, select **Query value** from the **Filter** drop-down.

3.  In the **Value** field, enter the filter options using the format described in the
    [ODATA URI Conventions](https://www.odata.org/documentation/odata-version-2-0/uri-conventions/)
    site, item 4.5.

4.  Select the **Entity set name** from the list.

The following are some example queries:

- `startswith(username, 'Mule') eq true`

- `startswith(username, 'JA') eq true or endswith(username, 'n3') eq true`

- `username eq 'Mike'`

The **Query value** is only used for the **Filter** field. The actual query is built by the
connector.

## Generate a Keystore File

In SAP SuccessFactors Connector 5.0 and later, **The private key from the X.509 certificate.** is
removed from OAuth SAML Bearer Assertion Authentication. You can migrate your existing
public-private certificates into a keystore file. These steps show how to generate a Java keystore
(JKS) file.

1.  Go to your Mule workspace and open the command prompt (for Windows) or Terminal (for Mac).

2.  Enter this command:

    ```none
    keytool -genkeypair -alias successfactors-cert -keyalg RSA -keystore successfactors-cert.jks
    ```

3.  Enter the following information:

    - Password for the keystore

    - Your first name and last name

    - Your organization unit

    - Your city and state, and the two-letter code for your country

      The system generates a Java keystore file (JKS format) that contains a private or public key
      pair in your workspace.

4.  Provide the file path for the keystore in your connector configuration.

    Enter this command:

    ```none
    keytool -exportcert -alias successfactors-cert -file successfactors-cert.crt -keystore successfactors-cert.jks
    ```

    The system exports the public key from the keystore into the workspace. This is the public key
    to enter in your SuccessFactors instance.

5.  Verify that you have both the keystore (`successfactors-cert.jks`) and the public key
    (`successfactors-cert.crt`) files in your workspace.

## Next Step

After you complete configuring the connector, you can try the
[Examples](https://docs.mulesoft.com/sap-successfactors-connector/latest/sap-successfactors-connector-examples).

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Salesforce Help](https://help.salesforce.com)