Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

  1. Make a backup copy of pentaho/WEB-INF/classes/log4j.xml.
  2. Open log4j.xml. Remove any Threshold param that occurs in all of the appenders (i.e. PENTAHOFILE or PENTAHOCONSOLE).
    Code Block
    xml
    xml
    titlelog4j.xmlxml
    <appender name="PENTAHOFILE" class="org.apache.log4j.DailyRollingFileAppender">
      <!-- THRESHOLD REMOVED -->
    </appender>
    
    <appender name="PENTAHOCONSOLE" class="org.apache.log4j.ConsoleAppender">
      <!-- THRESHOLD REMOVED -->
    </appender>
    
  3. Staying in the same file, find the root logger definition. Add or change the existing priority to WARN, ERROR, or FATAL. All loggers will inherit this level except where it is overridden (which is done in the next step).
    Code Block
    xml
    xml
    titlelog4j.xmlxml
    <root>
      <priority value="WARN" />
      <appender-ref ref="PENTAHOCONSOLE"/>
      <appender-ref ref="PENTAHOFILE"/>
    </root>
    
  4. Staying in the same file, add the following loggers before the root element. This will enable debug-level output in security-related classes.

    Note: When you add category elements, be sure to add them before the root element. Otherwise, you will violate the DTD for log4j.xml.

    Code Block
    xml
    xml
    titlelog4j.xmlxml
    <!-- all Spring Security classes will be set to DEBUG -->
    <category name="org.springframework.security">
      <priority value="DEBUG" />
    </category>
    
    <!-- all Pentaho security-related classes will be set to DEBUG -->
    <category name="org.pentaho.platform.engine.security">
      <priority value="DEBUG" />
    </category>
    <category name="org.pentaho.platform.plugin.services.security">
      <priority value="DEBUG" />
    </category>
    
  5. Now open pentaho-solutions/system/applicationContext-spring-security-<back-end>.xml where <back-end> is one of memory, jdbc, ldap, or hibernate. Which one you open will depend on the type of security back-end you've configured in web.xml. Add a property called hideUserNotFoundExceptions with value false to the bean with id daoAuthenticationProvider. Your modified bean should look like the bean below. Note that existing properties and constructor-args elements for this bean should be left unmodified.
    Code Block
    xml
    xml
    titleapplicationContext-spring-security-<back-end>.xmlxml
    <bean id="daoAuthenticationProvider" class="...">
      <!-- other properties/constructor-args not shown -->
      <property name="hideUserNotFoundExceptions" value="false" />
    </bean>
    
  6. Save the file and restart your servlet container or application server.

...