How to Configure

DocuSign Integration Setup

1. Provide the App Name and select Create App in DocuSign.
2. A new Integration Key is generated — store as DOCUSIGN_INTEGRATION_KEY (Application Constant).
3. Add additional details and click Save.
4. In Service Integration, generate RSA and store the private key as DOCUSIGN_PRIVATE_KEY (Application Constant).
5. Add required Redirect URIs, Origin URLs, and Allowed HTTP Methods.
6. To start DocuSign, call:

   https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id={integration_key}&redirect_uri={redirect_uri_specified}
   Replace {integration_key} and {redirect_uri_specified} as per your App Key.

Notes:

• Embedding signing is used — emails are not sent directly to recipients.
• The application generates the signing URL; the document is signed by the respective signer.

---

BDM - SuccessFactor Configuration (Config Server)

The application uses Config Server to fetch SuccessFactor details.

Property	Value
Config Server URL	https://cw-caf-configserver-sbx-dev.cfapps.eu10-004.hana.ondemand.com
Application Name	bdm-java-dev
Details Config File	runtimeConfig/SuccessFactorDetailsConfig.yaml
API Config File	runtimeConfig/SuccessFactorApi.yaml

All APIs written in Postman are available in Config Server. Update the SF API in these files as needed.

Java Code Flow:

1. Fetch the required request from the YAML file (e.g., SuccessFactors_FOR_EMPID from SuccessFactorDetailsConfig.yaml).
2. Fetch implementations from the composite API.
3. The response is returned from CompositeOutput().

---

Generate Token for Application (SAP BTP)

Authorization Token (with user details)

1. From XSUAA service → View Credentials → get url and clientid.
2. Form the URL:

   {url}/oauth/authorize?response_type=code&client_id={clientid}
3. Enter user details in the form and fetch the code from the redirect URL.
4. Generate the token:

   curl --location '{url}/oauth/token' \
     --header 'Content-Type: application/x-www-form-urlencoded' \
     --data-urlencode 'client_secret={clientsecret}' \
     --data-urlencode 'grant_type=authorization_code' \
     --data-urlencode 'response_type=token' \
     --data-urlencode 'client_id={clientid}' \
     --data-urlencode 'code={code}'
5. Decode the token at jwt.io to inspect user details.

Client Credentials Token (no user details)

curl --location '{url}/oauth/token' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'client_secret={clientsecret}' \
  --data-urlencode 'grant_type=client_credentials' \
  --data-urlencode 'response_type=token' \
  --data-urlencode 'client_id={clientid}'

This generates a token without user details.