We run a reverse proxy in front of GeoServer to handle authentication via Windows Integrated Auth. We also expose some of our custom data sources via hand-rolled WFS interfaces, which also require authentication using said proxy.
If I want to expose some of these custom data sources to GeoServer’s WMS via Cascaded WFS, would GeoServer automatically forward authentication headers from the client through the WMS and out to the WFS backend request?
If not, would you recommend a way to implement that?
Hey Jason, this question may be more suitable to the user list (the devel list is focused on working on the geoserver codebase itself). It is a bit tough to ask for public feedback on your custom data sources - perhaps you would like to check the support page for a vendor in your neck of the woods?
For the specific functionality you are looking at you will want to dive deep on the GeoTools codebase for WFSDataStore and WebMapServer client. They are fairly extensible, and I have seen the used with a federated security model as past of a OGC testbed (this involved passing security details through as part of a cascade).
We run a reverse proxy in front of GeoServer to handle authentication via Windows Integrated Auth. We also expose some of our custom data sources via hand-rolled WFS interfaces, which also require authentication using said proxy.
If I want to expose some of these custom data sources to GeoServer’s WMS via Cascaded WFS, would GeoServer automatically forward authentication headers from the client through the WMS and out to the WFS backend request?
If not, would you recommend a way to implement that?