Closed sh26masood closed 4 months ago
If you provide a git repo link to a demo application that reproduces your error, we can attempt to help you, but this issue is always a local environment issue and without direct access, we can't help you much.
Often this is some sort of a classpath issue where the properties file isn't pulled into the JVM's execution environment. That's as specific as I can get with the provided information. Maybe try writing some code to see if your JVM can even access the file. Maybe you don't have read permissions?
Closing as this isn't a bug.
See https://github.com/ESAPI/esapi-java-legacy/issues/831#issuecomment-1961515828 for additional details related to this.
java -Dorg.owasp.esapi.logSpecial.discard=true ...
So, this is not a bug, but a feature. See https://javadoc.io/doc/org.owasp.esapi/esapi/latest/org/owasp/esapi/reference/DefaultSecurityConfiguration.html for details of how ESAPI searches for the ESAPI.properties file.
Originally posted by @kwwall in https://github.com/ESAPI/esapi-java-legacy/issues/653#issuecomment-1016995464