Re: [gdal-dev] OGC services and credentials

2024-10-29 Thread Even Rouault via gdal-dev
Michał, Why service credentials (username & password) can not be entered with open options (*-oo UserPwd=user:pass*) when working with OGC services (tested against WMS)? The usual answer: because nobody has implemented that yet / contributions welcome.  The bulk of the development of the WM

Re: [gdal-dev] OGC services and credentials

2024-10-29 Thread Michał Kowalczuk via gdal-dev
Dear Laurentiu, I don't use command line tools. I use GDAL API. I only used them here to show the problem. For similar reasons I wouldn't even like to use global configuration options :-) In my opinion, the most clean way to do it is to hide credentials in dataset instance. Michał wt., 29 paź 202

Re: [gdal-dev] OGC services and credentials

2024-10-29 Thread Laurențiu Nicola via gdal-dev
Hi, It's unlikely to be a problem for you, but credential passing via command-line arguments is considered an anti-pattern because they're visible by other users who might be looking at the running process list. Environment variables are better because other users can't inspect them. Of course

Re: [gdal-dev] OGC services and credentials

2024-10-29 Thread Michał Kowalczuk via gdal-dev
OK, I understand. I'm not a C/C++ programmer, but I might try to contribute to GDAL in the future. Last time I gave up trying to build GDAL from source. The CMAKE setup was beyond me, so i started to use conda binaries. regards Michał wt., 29 paź 2024 o 14:35 Even Rouault napisał(a): > Michał,

[gdal-dev] OGC services and credentials

2024-10-29 Thread Michał Kowalczuk via gdal-dev
Hi GDAL friends! Why service credentials (username & password) can not be entered with open options (*-oo UserPwd=user:pass*) when working with OGC services (tested against WMS)? I know there is a config option *GDAL_HTTP_USERPWD=value* but it's not clean solution in my opinion. Credential should