Use a destination to store the CF API credentials

[gregorwolf]

Use a destination to store the CF API credentials

[saphanaacademy]

Hi Gregor,

Thanks for sharing the sample.

The latest version of the saphanaacademy-saas (0.0.5) and saphanaacademy-cap (0.0.60) generators now support accessing the CF API via a destination and Cloud SDK rather than via environment variables or SAP Credential Store. An instance destination appname-cfapi is created during MTA deployment (see the definition in mta.yaml).

After app deployment but before subscribing/unsubscribing a tenant, the instance destination appname-cfapi needs to have the user and password set (technical user recommended) and also the token service URL should have "login" changed to "uaa" at the beginning.

NB: The BTP cockpit requires fresh values for password and client secret whenever a URL is changed however client secret should be empty! Workaround this by entering a value for client secret and saving then re-editing and setting the client secret back to empty and saving again.

Hands-on video tutorials showing the whole process to come...

Best regards,
Philip

[piejanssens]

Hi Philip,

Just a quick FYI regarding this topic:

• The secret being mandatory (while not indicated as mandatory): I filed this in incident 4093127 / 2022
• Using uaa instead of login in the URL does not seem to make a difference, so this instruction can be left out. If there is a difference, I'd be interested to know how it differs.

Best regards,

Pieter

[saphanaacademy]

Hello Gregor,

Thanks for your feedback and the suggestion. Indeed using environment variables is not a great option.

The equivalent capability in the CAP generator already offers the possibility to use the SAP Credential Store rather than environment variables.

However using the destination service is another excellent option - we'll look at incorporating that in the future.

Best regards,
Philip

[gregorwolf]

Hi Philip,

please find here a first sample how to call the Cloud Foundry API using a Destination

const { executeHttpRequest } = require("@sap-cloud-sdk/core");

const destination = {
  destinationName: process.env.CFAPI_DESTINATION || "CFAPI",
};

async function getOrganizations() {
  const response = await executeHttpRequest(destination, {
    method: "get",
    url: "/v3/organizations",
  });
  return response.data;
}

module.exports = { getOrganizations };

The configuration is straight forward. Please note that the Client Secret is empty:

Don't think that Credential Store is the right option as then you still have to maintain the URL and Token Service URL somewhere else.

Best Regards
Gregor

[saphanaacademy]

Here's the accompanying hands-on Video Tutorial