Thanks for the detailed reply, Justin.
We may change the design to avoid the need for LDAP authentication, but if
not then it's good to know about the built-in LDAP Auth.
We'll be working on this in about a month, so may have more questions then.
Martin
On Wed, Mar 6, 2013 at 8:51 PM, Justin
Hi Martin
First I would recommend to invest in Geoserver 2.3 because the security
subsystem in 2.2.x is a little bit experimental.
The architecture of the new security subsystems allows to add custom
authentication mechanisms including configuration pages for the admin GUI.
Unfortunately there
Thanks for the info, Christian.
Do you mean that the code we would write for 2.2.x will need to be changed
for 2.3.x? Or just that 2.3 is more functional than 2.2? I ask because it
may not be an option to move straight to 2.3 yet, so we will have to make a
decision about which version to target
Hey Martin!
If i can interject I think what Christian is trying to say is that there
have been some good improvements to the new security authentication
subsystem going from 2.2 to 2.3. Mostly surrounding authentication filters.
Since one of the classes you mentioned is a filter class you may be
We have a custom authentication/authorization plugin developed for use with
GeoServer 2.1. It uses the Netegrity SiteMinder security proxy and a custom
authorization provider called WebADE. It consists of the following classes
implementing various Spring Security interfaces:
