[Geoserver-users] GeoServer 2.3.4 way to automate password changes and others immediately upon war deployment?

GeoServer GeoServer User
1

I am trying to completely automate the deployment of GeoServer with such changes already in place:

  1. master password changed

  2. admin password changed

  3. password encryption changed from weak pbe to digest

  4. new role created

  5. default role service changed to have the new role created as the Administrator Role

  6. new j2ee role authentication filter added

  7. update filter chains with the new j2ee authentication filter used

  8. a new oracle data store with the password updated to the current database password.

Now my plan was to lay down the xml files that were created when I went thru the manual configuration, but what do I need to do with the keystore and the xml files to make the deployment a working application upon completion???

Thanks,
Melody

Melody Ballance, Senior Software Engineer
Northrop Grumman ISS/DSD
468 Viking Drive
Virginia Beach, VA 23452
(757)498-5508 - office
(757)498-5670 - fax
melody.ballance@anonymised.com - email

“There are two ways to be fooled. One is to believe in what isn’t true; the other is to refuse to believe what is true.” Soren Kierkegaard

2

Normally, a configuration application can use the GeoServer REST API to configure GeoServer. Unfortunately, the security system has no REST API (lack of time).

Security configuration data is stored in GEOSERVER_DATA_DIR/security. You can try to copy the whole security directory.

Cheers
Christian

···

On Tue, Aug 27, 2013 at 10:12 PM, Ballance, Melody (IS) <melody.ballance@anonymised.com> wrote:

I am trying to completely automate the deployment of GeoServer with such changes already in place:

  1. master password changed

  2. admin password changed

  3. password encryption changed from weak pbe to digest

  4. new role created

  5. default role service changed to have the new role created as the Administrator Role

  6. new j2ee role authentication filter added

  7. update filter chains with the new j2ee authentication filter used

  8. a new oracle data store with the password updated to the current database password.

Now my plan was to lay down the xml files that were created when I went thru the manual configuration, but what do I need to do with the keystore and the xml files to make the deployment a working application upon completion???

Thanks,
Melody

Melody Ballance, Senior Software Engineer
Northrop Grumman ISS/DSD
468 Viking Drive
Virginia Beach, VA 23452
(757)498-5508 - office
(757)498-5670 - fax
melody.ballance@anonymised.com - email

“There are two ways to be fooled. One is to believe in what isn’t true; the other is to refuse to believe what is true.” Soren Kierkegaard

Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

DI Christian Mueller MSc (GIS), MSc (IT-Security)
OSS Open Source Solutions GmbH