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
As far as I understood the code it is currently only possible to start an async file upload from a secured remote URL if the endpoint supports username + password authentication method by passing the URL in the format of https://<username>:<password>@url.com. It would be great to enhance this functionality to also be able to authenticate by e.g. Bearer. Any plans to support this?
The text was updated successfully, but these errors were encountered:
Could you provide more details on how you envision this feature? Specifically, would you like to pass a Cloud Foundry token, or do you prefer to provide a token manually?
I don't have any preference how this feature is implemented in the end. I was just wondering if there are any plans to support cases where a file is behind a secured remote URL e.g. Artifactory. Not all endpoints allow username + password as authentication method.
Description
As far as I understood the code it is currently only possible to start an async file upload from a secured remote URL if the endpoint supports username + password authentication method by passing the URL in the format of
https://<username>:<password>@url.com
. It would be great to enhance this functionality to also be able to authenticate by e.g. Bearer. Any plans to support this?The text was updated successfully, but these errors were encountered: