ESAPI Configuration in AEM

K_PuneetH

09-04-2019

Hi,

We have requirement to use org.owsap.esapi pacakge in aem. So we added in related dependency in pom.xml and later we manually we made an bundle from esapi.jar and uploaded in system console. Still we are facing some issues. Below are the error in console when we ran java code:

Attempting to load ESAPI.properties via file I/O.

Attempting to load ESAPI.properties as resource file via file I/O.

Not found in 'org.owasp.esapi.resources' directory or file not readable: D:\Marketing Hub Latest Code\core\ESAPI.properties

System property [org.owasp.esapi.opsteam] is not set

System property [org.owasp.esapi.devteam] is not set

Not found in SystemResource Directory/resourceDirectory: .esapi\ESAPI.properties

Found in 'user.home' directory: C:\Users\617044\esapi\ESAPI.properties

Loaded 'ESAPI.properties' properties file

SecurityConfiguration for Validator.ConfigurationFile.MultiValued not found in ESAPI.properties. Using default: false

Attempting to load validation.properties via file I/O.

Attempting to load validation.properties as resource file via file I/O.

Not found in 'org.owasp.esapi.resources' directory or file not readable: D:\Marketing Hub Latest Code\core\validation.properties

Not found in SystemResource Directory/resourceDirectory: .esapi\validation.properties

Not found in 'user.home' (C:\Users\617044) directory: C:\Users\617044\esapi\validation.properties

Loading validation.properties via file I/O failed.

Attempting to load validation.properties via the classpath.

  • validation.properties could not be loaded by any means. fail. Exception was: java.lang.IllegalArgumentException: Failed to load ESAPI.properties as a classloader resource.

log4j:WARN No appenders could be found for logger (com.metlife.marketinghub.core.utils.Test).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

Expecting an example, how to configure esapi in AEM.

Thanks in advance.

Puneeth K.

View Entire Topic

Gaurav-Behl

MVP

27-08-2019

The version of esapi, servicemix and its dependencies could vary based on your AEM version. What version of AEM do you use?

There must be logs related to bundle not starting up due to some dependencies either in error.log or stderr.log Could you share that?

When you click on the "installed" bundle you'd see the unsatisfied dependencies along with versions. Could you share that?