Access resources requiring authentication

[geopython]

Access resources requiring authentication

[hannesaddec]

What kind of authentication are you referring to ? HTTP, Cookies, SSL, Shibboleth OpenID, CAS?

[justb4]

At least HTTP Basic Auth is used a lot, that would be a start. I take it that you need the ability to add credentials for a Resource URL? You could try to encode it in the URL like http://username:[email protected]/, not sure this will work in GHC, but also exposes creds via UI.

So, good point: could start adding optional user/password fields for a Resource.

[justb4]

Finally this feature will be implemented! Planned:

• generic/extensible Resource Auth design
• implementation for HTTP Basic Auth

Current thinking:

• new column/field for Resource auth
• auth field stores encrypted JSON structure
• auth JSON structure identifies Auth Method and Data properties
• Auth Method id drives implementation

Something like:

{
method: 'basicauth',
data: {
   username: 'rscuser',
   password: 'rscpasswd'
 }
}

The method id basicauth will direct the implementation to a BasicAuth class to use which fills in the proper headers etc.

[justb4]

Fixed via #259 , available on https://demo.geohealthcheck.org/

[samperd]

@justb4, thanks so much for considering this feature in the latest stantec sponsored development activity.

[justb4]

@samperd yes, you opened this a very long time ago! Does the current implementation work for you?

[justb4]

Re-opening: in some scenarios, e.g. WMS Editing, getting WMS metadata (Capabilities) is not applying auth headers when calling OWSLib WebMapService (or other OWSLib services).

Solution

Any Probe calling OWSLib Metadata should set (optional) auth headers via this e.g. call for WMS:

WebMapService(resource.url, version=version,
                             headers=self.get_request_headers())

Complications

This can currently only be applied to WMS, as other OWSLib services like WFS, TMS etc do not supply a headers parameter in their constructors. See this OWSLib issue

[justb4]

We are quite far, need to await Py2->Py3 migrate to use latest OWSLib with fixes for at WFS, CSW etc.

[borrob]

With the py3 migration fixed in #280: is there more to do for this issue?

[justb4]

We need to upgrade OWSLib from 0.17.0 to the latest version: https://github.com/geopython/OWSLib/releases (now 0.18.0), which should fix Resource auth for WFS and more (this issue) and some WFS3 fixes. Mainly quite some testing needed.

[borrob]

With PR #312 there is an update to OWSLib 0.19.

[justb4]

And now even to OWSLib 0.20.0. Want to first bring out 0.8.0 and quickly move to 0.8.1 for this one and related PRs.

[justb4]

Closing: via #333 : OWSLib is upgraded to 0.20.0, so Auth Headers should work with WFS and TMS as well. Please open specific issues for Auth problems/features.