-
Notifications
You must be signed in to change notification settings - Fork 594
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
cloudFoundryDeploy fails when SAP password contain special characters #4989
Comments
in which secret store do you store the password ?, is it jenkins / vault or something else |
I am storing it in Jenkins' jenkins-library/pkg/cloudfoundry/Authentication.go Lines 43 to 50 in 7090297
As you can see, the password will be appended to -p verbatim. Thus is the password is abc$123 , the appended string will become -p abc$123 which will be an issue in both linux and windows shells. Same is also true if the username contains a special character.
|
thanks for pointing it out, will get to you |
Thank you for your contribution! This issue is stale because it has been open 60 days with no activity. In order to keep it open, please remove stale label or add a comment within the next 10 days. If you need a Piper team member to remove the stale label make sure to add |
not stale @SAP/jenkins-library-team |
we are facing a similar issue, the SAP support told us it could be related to the technical user password, we removed any special characters but it does not work (CICD CF login via technical user with a custom IDP like IAS) ... however we can log in via the CLI without any problem with the same technical user |
Hello
I am encountering an issue where the library step
cloudFoundryDeploy
fails if the password contains special characters. Below is a snippet of the relevant log with some data redactedIn fact, I checked how cf CLI would behave if I omit quoting my password in my local desktop and the logs are the same. Locally, quoting my password was enough to get things working. Moreover, when I changed my password to remove all special characters, this error didn't happen in Jenkins and the login was successful.
Related to #32.
The text was updated successfully, but these errors were encountered: