Overview¶
EasySDI Proxy is an EasySDI module able to relay and securize various OGC services and enables access control and content filtering. It stores in a configuration file informations about the service name, type (WMS, WFS, CSW...), the target service to interface. Each configuration has a config Id which is unique and will be part of the final service URL, like this:
http://myAppServer.com:port/WebappName/servletname/config_Id
For each config Id, EasySDI PROXY affects on or more policies. The policy contains user access definition and filters for all layers of the remote service, so that we can choose who can access which layer of this service. A policy refers only to one specific service, because of the layer access definition; each service has different layers.
For each policy you may affect several users or roles. The user source can be file or db based, LDAP, just a source your application container supports.
This pages describe how to install and configure EasySDI PROXY. The targeted audience are people how have some skills in client-server technologie, and have to manage software infrastructure.Therefore it is assumed that you are familiar or have basic notions of:
- Service management on a server Platform (specially yours!).
- How application containers work (ex: Tomcat).
- WMS 1.1.0, 1.1.1 & 1.3.0 (since version 2.2.0)
- WFS 1.0.0
- CSW 2.0.0, 2.0.1 & 2.0.2
- WMTS 1.0.0 (KVP)
Installation guide¶
Advanced configuration¶
- Setting filters for policies
- Securing datas with SSL layer
- Services with anonymous access
- Cache management
- Activating data compression on your servlet container
- Supported projections
- Logs
- XSL transformation
- Configuring Geonetwork
Development docs¶
Translation status¶
- English - not yet availabale
- French - available
- German - not yet available
Help !¶
Ask for support on PROXY forum
or report bugs