You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please fill out the issue checklist below and provide ALL the requested information.
[ x] I reviewed open and closed github issues that may be related to my problem.
[ x] I tried updating to the latest version of the CF CLI to see if it fixed my problem.
I attempted to run the command with CF_TRACE=1 to help debug the issue.
I am reporting a bug that others will be able to reproduce.
Describe the bug and the command you saw an issue with
Command CF login
I have an application that calls cf cli internally.
I run cf login -u username -p password
When the password has special characters , cf login fails.
For eg.,
for demo purpose let's say imaginary password "-ig@ZlHDVZl_"
Please fill out the issue checklist below and provide ALL the requested information.
CF_TRACE=1
to help debug the issue.Describe the bug and the command you saw an issue with
Command CF login
I have an application that calls cf cli internally.
I run cf login -u username -p password
When the password has special characters , cf login fails.
For eg.,
for demo purpose let's say imaginary password "-ig@ZlHDVZl_"
cf login -o myOrg -s mySpace -u devUser1 -p "-ig@ZlHDVZl_"
What happened
It throws following error
This error seems to differ for different passwords. Escaping the characters didn't work as well.
But the same password works via interactive cf login.
Expected behavior
cf login should work via -u and -p options when password has special characters
Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:
cf login -u username -p password
with plenty of special characters in password especially "?" and "$_"Provide more context
What could be the reason for this behaviour? Do you have any recommendations on special characters in passwords when used directly in shell command?
The text was updated successfully, but these errors were encountered: