[MapProxy] mapproxy auth
apestereva at aerialservicesinc.com
Wed Mar 12 15:35:32 PDT 2014
I have two questions regarding authentication and authorization for
We tried enabling basic authentication via OpenLDAP on the directory with
Mapproxy configuration files. Without adding any authorization logic it
works great for WMS, WMTS and TMS services and capabilities, but for
several demo links (e.g. html viewers for WMS, WMS-C and TMS layer
capabilities) we still see 401 errors in error logs.
*Q1: is basic authentication on WSGI application configuration folder not
sufficient as approach, or are we just missing something in configuration?
Could you please point us in a right direction, if this at all is meant to
On authorization side, I attempted a simple version very similar to the sample
code on Mapproxy
just using environ['REMOTE_USER'] when comparing to the layers prefixes.
This works great for WMS service, but for WMTS and TMS services (and a few
demo links) we see errors in error logs related to reading the
"remote_user" variable in authorization code: KeyError: 'REMOTE_USER'.
*Q2: how to make sure that "remote_user" variable is populated and
available when accessing all services, not just WMS? Should some other
variable be used to catch authenticated user? - again, if it at all makes
sense to use basic authentication for mapproxy. *
Thank you very much, I will really appreciate any help with any of the
*Anna Pestereva | Application Developer & Cartographer*
*Aerial Services, Inc. (ASI) *
Office: (319) 277-0436 | Direct: (319) 553-0261 | Mobile: (319) 830-6340 |
Fax: (866) 800-4799
6315 Chancellor Drive | Cedar Falls, Iowa 50613
APestereva at AerialServicesInc.com <apestereva at AerialServicesInc.com> |
*www.AerialServicesInc.com* <http://www.aerialservicesinc.com/> |
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MapProxy