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
We are getting the key from secure vault. When the value of the password key contains a special character like @, the file connector will not work. Workaround is to url encode the password and place it in the secure vault.
If a different team is managing the enviornment (i.e Manage Services Team), if we see a special character in password, we need to specifically instruct them to url encode the password. Or be default, they always need to url encode. This is a special instruction for them. The developer who attends to this should know this edge case. Thus, these is a chance to miss this.
What if we fix at the connector level, always we url encode the password and take it in.
Description
Please consider below SFTP connection made for the file connector.
We are getting the key from secure vault. When the value of the password key contains a special character like
@
, the file connector will not work. Workaround is to url encode the password and place it in the secure vault.If a different team is managing the enviornment (i.e Manage Services Team), if we see a special character in password, we need to specifically instruct them to url encode the password. Or be default, they always need to url encode. This is a special instruction for them. The developer who attends to this should know this edge case. Thus, these is a chance to miss this.
What if we fix at the connector level, always we url encode the password and take it in.
Describe your task(s)
No response
Related issue(s) (optional)
https://github.com/wso2-enterprise/wso2-mi-internal/issues/711
Suggested label(s) (optional)
Product : WSO2MI 4.2.0
Update level : 56
Opened by : hasithah@wso2.com
Suggested assignee(s) (optional)
No response
The text was updated successfully, but these errors were encountered: