Removing Security 2.x-3.0.x

The security features of the Pentaho BI Platform cannot be removed. However, they can be effectively removed using the following steps. Essentially, the idea is to create a single user and role and give system-wide access to that user. The anonymous processing filter provides a nice way of guaranteeing that even unauthenticated users have a username and role.

Define the anonymous role. Note that this is already defined by default. If you must change it, change it here. Note also that the username assigned by the anonymous processing filter is not relevant to Pentaho security code that runs later in the request. Only the anonymous role is relevant. In this example, the anonymous username is anonymousUser and the anonymous role is Anonymous. Note where the role Anonymous occurs in subsequent examples. Note finally that role names are case-sensitive.
applicationContext-acegi-security.xml
```
<bean id="anonymousProcessingFilter" class="org.acegisecurity.providers.anonymous.AnonymousProcessingFilter">
  
  <property name="userAttribute" value="anonymousUser,Anonymous" />
</bean>
```

Allow anonymous access to all web resources by editing the objectDefinitionSource on the FilterSecurityInterceptor to look like the example below.

Note: Why does Authenticated appear in XML below? Because some client tools (for example, Schema Workbench) require a username and password to publish to the server. If you supply a username and password, then you are no longer anonymous.

applicationContext-acegi-security.xml

<bean id="filterInvocationInterceptor"
  class="org.acegisecurity.intercept.web.FilterSecurityInterceptor">
  <property name="authenticationManager">
    <ref local="authenticationManager" />
  </property>
  <property name="accessDecisionManager">
    <ref local="httpRequestAccessDecisionManager" />
  </property>
  <property name="objectDefinitionSource">
    <value>
      <![CDATA[
        CONVERT_URL_TO_LOWERCASE_BEFORE_COMPARISON
        \A/.*\Z=Anonymous,Authenticated
      ]]>
    </value>
  </property>
</bean>

Use PentahoAllowAnonymousAclVoter as your IAclVoter implementation. You configure your IAclVoter implementation partially in pentahoObjects.spring.xml and partially in pentaho.xml. When configuring this voter, you will define the anonymous user and role. That user and/or role should be used when assigning ACLs.

pentaho.xml

<pentaho-system>

  <!-- omitted -->

  <anonymous-authentication>
    <anonymous-user>anonymous</anonymous-user>
    <anonymous-role>Anonymous</anonymous-role>
  </anonymous-authentication>

  <!-- omitted -->

</pentaho-system>

pentahoObjects.spring.xml

<beans>

  <!-- omitted -->

  <bean id="IAclVoter" class="org.pentaho.platform.engine.security.acls.voter.PentahoAllowAnonymousAclVoter" scope="singleton" />

  <!-- omitted -->

</beans>

Assign ACLs using the user and role defined in the previous step. Use these steps along with the settings below. Be sure to remove any active override entries.

Note: Why does Authenticated appear in XML below? Because some client tools (for example, Schema Workbench) require a username and password to publish to the server. If you supply a username and password, then you are no longer anonymous.
pentaho.xml
```
<pentaho-system>

  

  <acl-publisher>
    <default-acls>
      <acl-entry role="Anonymous" acl="ADMIN_ALL" />
      <acl-entry role="Authenticated" acl="ADMIN_ALL" />
    </default-acls>

    
  </acl-publisher>

  
</pentaho-system>
```
Finally, tell Pentaho the role that should be treated as the Pentaho administrator. In this case, it's the anonymous role mentioned earlier.
pentaho.xml
```
<pentaho-system>

  

  <acl-voter>
    <admin-role>Anonymous</admin-role>
  </acl-voter>

  

</pentaho-system>
```