David, The REST API should not be affected. As you note, the encryption only affects the storage representation. The datastore passwords are encrypted on write and decrypted on read via the XStreamPersister. Therefore any code that uses the Catalog or XStreamPersister directly will require no changes.
Nor will it will not affect REST API clients as authentication uses the same subsystem as web ui, just a different approach to verifying password. I POSTED to a local instance and verified this behavior. There is currently no test in the REST Config module to verify this, but there is no test to verify that a JDBC data store that accepts a passwd parameter is successful either. -Ian On Thu, Aug 18, 2011 at 7:12 AM, David Winslow <dwins...@opengeo.org> wrote: > Since this proposal changes the representation used to store datastore > configurations, will it affect the REST API? ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
