We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Before filing this issue, please ensure you're using the latest CLI by running swa --version and comparing to the latest version on npm.
swa --version
# node --version v22.14.0 # npm --version 10.9.2 # swa --version 2.0.3
Are you accessing the CLI from the default port :4280 ?
:4280
Describe the bug after the login via az login the login via swa login with the option --clear-credentials fails.
To Reproduce Steps to reproduce the behavior:
Expected behavior The client can connect to swa with different credentials.
Screenshots
# swa login --tenant xxx --client-id xxx --client-secret xxx- -subscription-id xxx --resource-group rg-test-we --app-name swa-test-we --clear-credentials --verbose=silly Welcome to Azure Static Web Apps CLI (2.0.3) Getting config file options from "swa-cli.config.json"... Config file does not exist at "swa-cli.config.json" Checking Azure session... Executing authenticateWithAzureIdentity - details: - tenantId: xxx - clientId: xxx - clientSecret: xxx - useKeychain: true Keychain is enabled Executing swaCliPersistencePlugin Clearing keychain credentials Clearing credentials cache Machine ID: <hidden> Invoking crypto service deleting credentials from keychain - fullKey: xxx Deleting credentials from native keychain Getting keychain reference isKeychainEnabled: true KeychainCache: undefined Attempting to load native keychain ✖ Failed to setup project: Cannot delete credentials ✖ If you believe this behavior is unexpected, please raise a GitHub issue at: https://github.com/Azure/static-web-apps-cli/issues/new/choose
Desktop (please complete the following information):
Additional context N/A
The text was updated successfully, but these errors were encountered:
I raised the ticket with more details similar to #923
Sorry, something went wrong.
No branches or pull requests
Before filing this issue, please ensure you're using the latest CLI by running
swa --version
and comparing to the latest version on npm.Are you accessing the CLI from the default port
:4280
?Describe the bug
after the login via az login the login via swa login with the option --clear-credentials fails.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The client can connect to swa with different credentials.
Screenshots
Desktop (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: