[Owasp-csrfguard] Location of the configuration files

[Chris Hyzer]

It doesn't cover that use case (from JNDI), but you can have a file on the filesystem not on the classpath:

Have the Owasp.CsrfGuard.properties that has all the defaults in the classpath.  Then have the Owasp.CsrfGuard.overlay.properties on the classpath that has an entry that says which files to look at in which order.  First the Owasp.CsrfGuard.properties on the classpath, then some file on the file system file:/opt/whatever/csrfguard/conf/Owasp.CsrfGuard.server.properties, something like that.

You can configure as many overlays as you want.  i.e. you can have a base config, an overlay for the application, and another overlay for the environment of the application.   However you want to organize it.

Thanks,
Chris


From: owasp-csrfguard-bounces at lists.owasp.org [mailto:owasp-csrfguard-bounces at lists.owasp.org] On Behalf Of Jasmin Amidzic
Sent: Thursday, May 08, 2014 9:21 PM
To: owasp-csrfguard at lists.owasp.org
Subject: [Owasp-csrfguard] Location of the configuration files

Hi,
    I would like to read configuration files,  Owasp.CsrfGuard.properties and  Owasp.CsrfGuard.overlay.properties,  from a location on a application server instead of reading them from the classpath. Ideally, the information about location of the files would come from a JNDI entry on the app server.
I did some search



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-csrfguard/attachments/20140509/67432f84/attachment.html>