BUG - Secure store unable to read the key for a Trial BTP ABAP env.

[ravish-garg]

Related Feature

Feature request: #654

Description

Secure store unable to read the key for a Trial BTP ABAP env. ABAP Trial environment added to saved SAP Systems using Fiori Tools in VSCode.

Generate a new Fiori Elements app against an OData service and serve the app. Fails to start with the following error:

Could not get hold of vscode
warn backend-proxy-middleware Dummy store. Trying to retrieve for service: fiori/v2/system, key: https://XXXXXXXXXXXX.abap.us10.hana.ondemand.com
error fiori-tools-proxy Failed to register backend for /sap. Check configuration in yaml file.
error fiori-tools-proxy         Error: Cannot connect to ABAP Environment on BTP without service keys.

Steps to Reproduce

Steps to reproduce the behavior:

1. Connect to an ABAP Trial Environment in SAP Fiori Tools, via the add system wizard. System connected & saved.
2. Generate a new FE app using application generator and pick one of the exposed OData service from the trial environment
3. Serve the app using npm start.
4. Proxy middleware reports error in serving the app.

Version/Components/Environment

FIori Tools updated to latest version. VSCode OS:

• [X] Windows
• Works find on MacOS

Root Cause Analysis

Problem

{describe the problem}

Fix

{describe the fix}

Why was it missed

{Some explanation why this issue might have been missed during normal development/testing cycle}

How can we avoid this

{if we don’t want to see this type of issues anymore what we should do to prevent}

[tobiasqueck]

@zdravko-georgiev would you have time to have a look at this one?

[zdravko-georgiev]

@tobiasqueck Yes, I will have a look.

[zdravko-georgiev]

Hi @ravish-garg, I am not able to reproduce the issue. Could you please provide more information on how to reproduce the issue? Also could you please share which version of the backend-proxy-middleware you are using?

Thanks and best regards, Zdravko

[ravish-garg]

Hi @zdravko-georgiev I updated all the extensions to the latest versions and no longer encounter the same error.