A question has been asked about handling of credentials in the context of datalad addurls.
A response was given, suggesting use of datalad (DataLad core), or uncurl (DataLad-next) special remote, and highlighting that in either case the urls need to be handled by a special remote with access to DataLad's credential system.
The original question included a suggestion of using username:password in URLs, which should be technically correct and should work. I was not sure why it didn't, but didn't investigate due to the alternatives seeming more natural.
For this issue, the question remains whether a KBI about the role of special remotes for URL handling is needed.
TODO (not necessarily to be performed in this order)
[ ] Inform OP/Add reference to this issue at origin
Origin: https://neurostars.org/t/how-do-i-add-urls-to-add-that-require-authentication-using-datalad-addurls/26301
A question has been asked about handling of credentials in the context of
datalad addurls.A response was given, suggesting use of
datalad(DataLad core), or uncurl (DataLad-next) special remote, and highlighting that in either case the urls need to be handled by a special remote with access to DataLad's credential system.The original question included a suggestion of using
username:passwordin URLs, which should be technically correct and should work. I was not sure why it didn't, but didn't investigate due to the alternatives seeming more natural.For this issue, the question remains whether a KBI about the role of special remotes for URL handling is needed.
TODO (not necessarily to be performed in this order)