-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
support-trackerTrack a support event that occurred elsewhereTrack a support event that occurred elsewherevia-neurostarsreport origin is neurostars sitereport origin is neurostars site
Description
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
- Clarifying Qs asked or not needed
- Nature of the issue is understood
- Inform OP about resolution
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
support-trackerTrack a support event that occurred elsewhereTrack a support event that occurred elsewherevia-neurostarsreport origin is neurostars sitereport origin is neurostars site