Question

I’m working on a Web Service project to provide data to a partner. Our app is really light weight and has only a handful of APIs. Because of time constraint and in-house pre-existing knowledge we went the Spring MVC / Spring Security path to serve those restful APIs.

At any rate this is a B2B project where we are expecting only that partner to hit our servers. So it seems a little over kill to modify are very small db schemas to add tables that would contain only 1 user access record for that partner…

Heard someone say though that it’s possible to use an encrypted file, or at least a file where the password information is encrypted, instead of the database to hold the Spring Security user access information… Is that true? If it is can anyone point me to some references? I couldn’t find anything relevant on Google at first glance… 🙁

Thanks.

Answer 1

http://www.mularien.com/blog/2008/07/07/5-minute-guide-to-spring-security/

See the ” under the authentication-provider; this allows you to use encrypted passwords (use sha). If you only have a single user and you wanted the information in an external file, then you could use a property file configuration placeholder to simply specify
${user.1.id} ${user.1.passwordenc},etc… kinda hacky, but it would work.