It's a bit more work, but what about embedding a simple database in the
application itself for managing usernames, passwords, privileges, etc.
We've had good luck including this db right in our applications and it
provides a lot of flexibility for doing fancier stuff down the road.
You can include it prepopulated along with default users in the
geoserver install.
Quoting John Zastrow <jcz@anonymised.com>:
It's a bit more work, but what about embedding a simple database in the
application itself for managing usernames, passwords, privileges, etc.
We've had good luck including this db right in our applications and it
provides a lot of flexibility for doing fancier stuff down the road.
You can include it prepopulated along with default users in the
geoserver install.
It would also nice to make use of the "usual" web server security model, I just
could not figure out how to do so at the time. So I rolled my own. I think such
things are controled as part of the web.xml file but I have had a hard time
figuring out the details.
Cheers,
Jody