Replacement for DestinationServiceTokenExchangeStrategy.LOOKUP_ONLY

[ErwanAirone]

Issue Description

With the deprecation of DestinationServiceTokenExchangeStrategy.LOOKUP_ONLY, fetching a destination always retrieves the authencation token, this leads to destination not found error when the destination needs to be fetched with invalid credentials.

Important information:

• Your code

  DestinationOptions options = DestinationOptions
                  .builder()
                  .augmentBuilder(
                          DestinationServiceOptionsAugmenter
                                  .augmenter()
                                  .retrievalStrategy(retrievalStrategy))
                  .build();

• Expected outcome A way to retrieve the destination without the token.
• Actual outcome Cloud sdk will also fetch the token and if unsuccessful, the destination is not found.

Impact / Priority

Affected development phase: Production Customers are now seeing destination not found when the token can not be fetched successfuly by the cloud sdk.

Impact: Inconvenience

Project Details

• SDK Version: 5.11.0
• Link to GitHub repo: <irpa_commonlib>
• Project type, for example:
  • [ ] CAP Project
  • [x ] SDK Maven Archetype
  • [ ] None of the above:
• Platform:
  • [ x] Cloud Foundry
  • [ ] Deploy with Confidence (Cloud Foundry)
  • [ ] None of the above:

---

[MatKuhr]

For only reading destination properties, without performing auth flows, please follow this documentation:

Collection<DestinationProperties> allDestinationProperties = service.getAllDestinationProperties();
DestinationProperties individualProperties = service.getDestinationProperties("my-destination");

[ErwanAirone]

Alternative proposed. Thank you.