Skip to content

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

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

Open
stotz89 opened this issue Feb 14, 2025 · 2 comments

Comments

@stotz89
Copy link

stotz89 commented Feb 14, 2025

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
Copy link
Contributor

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
Copy link
Author

stotz89 commented Mar 25, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants