Skip to content

FEATURE - Prevent overwriting of saved system credentials by default via generator #3718

@mikicvi-SAP

Description

@mikicvi-SAP

As a developer,
I want to be able to use the generator with a saved system that does not contain credentials,
so that I can still have the system without the credentials after generation.

Description

  1. User sets up a new ABAP On Premise system using SAP saved systems without entering the user credentials
    Generate the application using the same system, and a message is shown to add user credentials
    The user credentials added while app-generation should not be saved in the system details

  2. If the user credentials are saved for the system, but there is an auth error while generating the app, the user enters the correct credentials, and the app is generated, the updated user credentials are saved in the system details.

Technical Design

  • Functionality is related to:
    • @sap-ux/odata-service-inquirer
    • @sap-ux/fiori-app-sub-generator

Acceptance Criteria

  • Given I generate a new application using my ABAP on-prem system for which the username is saved, then this username will be populated in the username prompt when connecting to the system during generation, regardless of whether there is an associated invalid password stored.
  • Given I generate a new application using my ABAP on-prem system for which the username/password are not saved, I see the message to add my user credentials on generating the app, the user credentials are not saved in the system details
  • Given I get a login error for a saved system, I enter the new credentials and generate the application, the updated user credentials are now saved with the system details
  • User message "This stored system has no credentials. Please provide them. They will not be saved with the system details."
  • Warning message:'Passwords are stored in your operating system's credential manager and are protected by its security policies.'

Notes

  • Related to internal issue: 35929

Tasks

  • Unit Tests added
  • Test Cases defined

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions