Login fails when the service principal key starts with '-'
See original GitHub issueWhen the service principal secret starts with -
, a known bug in the az cli is triggered, and the login action fails with:
Error: : argument --password/-p: expected one argument
The workaround is to use the -p=<the_secret>
syntax instead of -p <the_secret>
.
I see there’s actually already an open PR that would fix this.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:8
Top Results From Across the Web
az login fails with Azure AD service principal and certain client ...
When attempting to login using az cli using Azure AD service princiapal, certain client secrets are causing errors.
Read more >How to fix 'Unable to login as the service principal' exception ...
I have another domain user devuser that is a member of a group named tc-webapp-users which is inturn within an OU named tomcat-ou....
Read more >Sign in with Azure CLI — Login and Authentication
A CERTIFICATE must be appended to the PRIVATE KEY within a PEM file. For an example of a PEM file format, see Certificate-based...
Read more >Overview of Service Principal Name and Kerberos ...
This article gives an overview of Service Principal Name (SPN) for using the Kerberos authentication in SQL Server connections.
Read more >Azure Provider: Authenticating via a Service Principal and a ...
tenant is the tenant_id defined above. Finally, it's possible to test these values work as expected by first logging in: az login --service-principal...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry for the delayed response. We shall take a look and let you know about the changes. Thanks!
This issue is idle because it has been open for 14 days with no activity.