Opened 14 years ago

Closed 14 years ago

Last modified 13 years ago

#3091 closed defect (fixed)

GDAL WCS driver should support authentification (username and password)

Reported by: gaopeng Owned by: warmerdam
Priority: normal Milestone: 1.7.0
Component: GDAL_Raster Version: 1.6.1
Severity: normal Keywords: WCS


ArcGIS online services are secured services. Creating WCS layer with these URL will fail. To repro:

Use this string for Make WCS layer input Then you will be prompted to enter user name/password ISUser/ags After this, the tool should work, but it does not pass validation for the input.

Change History (6)

comment:1 by warmerdam, 14 years ago

Resolution: fixed
Status: newclosed

I have added support for the HttpAuth and UserPwd elements in the WCS control file to enable authentication. It seems that this server is using "NTLM" authentication - something specific to Microsoft. My linux based curl does not use this authentication by default, so I have to force it to use this authentication. This can be accomplished with the following .wcs control file:


One of the supported values for HttpAuth is "ANY" which is supposed to use any of the authentication schemes, but pick the strongest. For some reason this does not work for me against your server so it may be that you need to specifically set NTLM for some servers. Behavior may be somewhat different with windows based libcurl.

Support implemented in trunk (r17920,r17921). Ported into 1.6-esri branch (r17922).

comment:2 by gaopeng, 14 years ago

I confirmed that the fix resolved my problem.

comment:3 by gaopeng, 13 years ago

Frank, The recent JPIP change overwrote the HTTP user/password support. I merged the HTTP user/password back, and committed the change. Could you review?

comment:4 by warmerdam, 13 years ago


Your re-incorporation of HTTP user/password support (r29444) looks fine. I'm not sure what lead to me accidentally removing it during the jpip work (r19111). Sorry.

comment:5 by warmerdam, 13 years ago

Ahem, that was r20444, not r29444.

comment:6 by warmerdam, 13 years ago

I have migrated this feature back to the 1.4-esri tree (r20476) and done some minimal testing.

Note: See TracTickets for help on using tickets.