[FEATURE REQUEST] Add additional authentication methods for async file upload from secured remote

[stotz89]

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?

[IvanBorislavovDimitrov]

Hello,

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?

Best regards,
Ivan

[stotz89]

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.

[Yavor16]

Hello!

For now we don't have plans for implementation but we are open for ideas! Can you tell us more about your use case?

Best regards,
Yavor

[stotz89]

@Yavor16 The use case is actually as described above. Let's assume the artifact you want to deploy lies behind a protected URL (e.g. JFrog Artifactory). Currently you can only use the artifact if the remote endpoint supports Basic Auth in form of https://<username>:<password>@url.com. If this is not supported I can't sue the deploy service to fetch my artifact.