Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tailor SCS error message for the OS #2008

Open
gejohnston opened this issue Jan 5, 2024 · 2 comments
Open

Tailor SCS error message for the OS #2008

gejohnston opened this issue Jan 5, 2024 · 2 comments
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have

Comments

@gejohnston
Copy link
Member

Is your feature or enhancement request related to a problem or limitation? Please describe

A failure to save credentials displays an error message that includes instructions which may not apply on the OS on which you are running.

Describe your enhancement idea

The following command failure shows the existing message.

$ zowe auth login apiml --user YourUserName--password YourPassword
Unable to perform this operation due to the following problem.
Unable to securely save credentials.

Diagnostic Information
Possible Solutions:
 - Reinstall Zowe CLI. On Linux systems, also make sure to install the prerequisites listed in Zowe CLI documentation.
 - Ensure Zowe CLI can access secure credential storage. Zowe CLI needs access to the OS to securely save credentials.
 - Instead of secure storage, rerun this command with the "--show-token" flag to print the token to console. Store the token in an environment variable ZOWE_OPT_TOKEN_VALUE to use it in future commands.
  • When on Windows, the Linux instructions are irrelevant.
  • However, when on Windows, we could alternatively instruct the user that if their secure vault is corrupt, they could remove the "Windows Credentials - Zowe/secure_config_props" entry from Windows Credential Manager and try again.

Summary: Some of the "Possible Solutions" should be displayed conditionally based on the OS on which the user is running.

Describe alternatives you've considered

Provide any additional context

@gejohnston gejohnston added enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have new The issue wasn't triaged yet labels Jan 5, 2024
Copy link

github-actions bot commented Jan 5, 2024

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

Copy link

github-actions bot commented Apr 4, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the Stale label Apr 4, 2024
@zFernand0 zFernand0 removed the new The issue wasn't triaged yet label Apr 9, 2024
@github-actions github-actions bot removed the Stale label Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have
Projects
Status: Low Priority
Development

No branches or pull requests

2 participants