Hardening is a process of taking a finished application and making it more difficult to reverse engineer and tamper. Combined with secure coding practices, application hardening is a best practice for companies to protect their app’s IP and prevent misuse, cheating, and repackaging by bad users.<\/p>\n
The below steps to be followed to harden the Tomcat web server to secure the application.<\/p>\n
Open the tomcat application in firefox and verify the server info from firebug.
\nRemoving Server Banner from HTTP Header is one of the first things to do as hardening. Having server banner expose the product you are using and leads to information leakage vulnerability.<\/p>\n
i. Go to <tomcat installed directory>\/conf folder<\/p>\n
ii. Modify server.xml by using vim editor<\/p>\n
iii. Add following under Connector port and save the file<\/p>\n
Server =\u201d \u201c\n<Connector port=\"8080\" protocol=\"HTTP\/1.1\"\nconnectionTimeout=\"20000\"\nServer =\" \"\nredirectPort=\"8443\" \/><\/pre>\nUsage: Server banner information should be ignored, since It will protect the server from the hackers to launch Targeted attacks against our web server and version.<\/p>\n
Verification:<\/h4>\n
i. Open Firefox with firebug<\/p>\n
ii. Access Tomcat application<\/p>\n
iii. You will notice Server value is blank now.<\/p>\n
2. Starting Tomcat with a Security Manager<\/h4>\n
Security Manager protects you from an untrusted applet running in your browser. Running Tomcat with a security manager is definitely better than running without one.<\/p>\n
start tomcat with \u2013security argument\n<tomcat installed directory>\/bin# .\/startup.sh -security<\/pre>\nUsage:<\/strong> Security Manager protects you from an untrusted applet running in your browser, use of a SecurityManager, while running Tomcat can protect your server from trojan servlets, JSPs, JSP beans, and tag libraries. Or even inadvertent mistakes<\/p>\n
3. Enable access log logging<\/h4>\n
The default configuration doesn\u2019t capture access logs. The access log is very useful in troubleshooting to check request type, requester IP address, status code, etc.<\/p>\n
i. Go to <tomcat installed directory>\/conf<\/p>\n
ii. Modify server.xml by using vi<\/p>\n
iii. Go to the end of the file and uncomment Valve entry for valves.AccessLogValue<\/p>\n
iv. <Valve className=”org.apache.catalina.valves.AccessLogValve”<\/p>\n
v. directory=”logs”<\/p>\n
vi. prefix=”localhost_access_log.”<\/p>\n
vii. suffix=”.txt”<\/p>\n
viii. pattern=”common” resolveHosts=”false”\/><\/p>\n
ix. Restart Tomcat server and you should see localhost_access_log is created under <tomcat installed directory>\/logs folder
\nUsage: The default configuration doesn\u2019t capture access logs. The access log is very useful in troubleshooting to check request type, requester IP address, status code, etc.<\/p>\n4. Enforced HTTPS<\/h4>\n
It\u2019s good to force redirect all HTTP requests to HTTPS to ensure web application data transmission are over SSL Certification.<\/p>\n
i. Go to <tomcat installed directory>\/conf folder<\/p>\n
ii. Modify web.xml by using vim editor<\/p>\n
iii. Add following before <\/web-app> syntax<\/p>\n
iv. <security-constraint><\/p>\n
v. <web-resource-collection><\/p>\n
vi. <web-resource-name>Protected Context<\/web-resource-name><\/p>\n
vii. <url-pattern>\/*<\/url-pattern><\/p>\n
viii. <\/web-resource-collection><\/p>\n
ix. <user-data-constraint><\/p>\n
x. <transport-guarantee>CONFIDENTIAL<\/transport-guarantee><\/p>\n
xi. <\/user-data-constraint><\/p>\n
xii. <\/security-constraint><\/p>\n
xiii. Restart Tomcat and access web application to verify.<\/p>\n
Note:<\/strong> ensure Tomcat is configured to run on SSL else it will break the application accessibility.<\/p>\n
5. Add Secure flag in cookie<\/h4>\n
It is possible to steal or manipulate web application session and cookies without having a Secure flag in HTTP Header as Set-Cookie.<\/p>\n
i. Go to <tomcat installed directory>\/conf folder<\/p>\n
ii. Modify server.xml by using vi<\/p>\n
iii. Add following in Connector port<\/p>\n
Secure=\u201dtrue\"\n<Connector port=\"8080\" protocol=\"HTTP\/1.1\"\nconnectionTimeout=\"20000\"\nServer=\" \"\nSecure=\"true\"\nredirectPort=\"8443\" \/><\/pre>\nUsage :<\/strong> The secure flag is an option that can be set by the application server when sending a new cookie to the user within an HTTPS Response.<\/p>\n
The purpose of the secure flag is to prevent cookies from being observed by unauthorized parties due to the transmission of a the cookie in clear text.<\/p>\n
Verification:<\/strong><\/p>\n
i. Open Firefox with firebug<\/p>\n
ii. Access your application and check HTTP response header, you should see Secure flag<\/p>\n
6. Add HttpOnly in cookie<\/h4>\n
Best practice to have this enabled at application code level. However, due to bad programming or developer\u2019s unawareness, it comes to Web Infrastructure.<\/p>\n
i. Go to <tomcat installed directory>\/conf folder<\/p>\n
ii. Modify context.xml by using vi<\/p>\n
iii. Add following in Context directive<\/p>\n
usehttponly=\u201dtrue\u201d\n<context usehttponly=\"true\">\u2028...\u2028<\/context><\/pre>\nUsage:<\/strong> Adding Http only in cookies will prevent the webservers from the steal or manipulate web application session and cookies.<\/p>\n
Verification:<\/strong>
\nPress F12 \/ firebug , go to the Cookies tab to verify the tomcat application pages for HttpOnly.<\/p>\n7. Enable Secure Socket Layer (SSL)<\/h4>\n
To enable Tomcat to listen over HTTPS protocol, you must configure tomcat with SSL. This assumes you have SSL Certificate imported under keystore.<\/p>\n
i. Go to $tomcat\/conf folder<\/p>\n
ii. Modify server.xml by using vim editor<\/p>\n
iii. Add following under Connector port<\/p>\n
SSLEnabled=\u201dtrue\u201d scheme=\u201dhttps\u201d keystoreFile=\"conf\/keystore\" keystorePass=\"password\"\n<Connector port=\"8080\" protocol=\"HTTP\/1.1\"\nconnectionTimeout=\"20000\"\nServer=\" \"\nSecure=\"true\"\nSSLEnabled=\"true\" scheme=\"https\" keystoreFile=\"conf\/keystore\" keystorePass=\"password\" clientAuth=\u201dfalse\u201d sslProtocol=\u201dSSLv3\u201d\nredirectPort=\"8443\" \/><\/pre>\nUsage:<\/strong> It is a standard security protocol for establishing encrypted links between a web server and a browser in an online communication.<\/p>\n
The usage of SSL technology ensures that all data transmitted between the web server and browser remains encrypted and securedIt is a standard security protocol for establishing encrypted links between a web server and a browser in an online communication.<\/p>\n
The usage of SSL technology ensures that all data transmitted between the web server and browser remains encrypted and secured.<\/p>\n
Verification: <\/strong>Open the tomcat application in browser with https:\/\/\/, if you open the same with http:\/\/ then it will not allow you to view the application.<\/p>\n
8. Run Tomcat from non-privileged account<\/h4>\n
It\u2019s good to use a separate non-privileged user for Tomcat. The idea here is to protect other services running in case of any security hole.<\/p>\n
i. Create a UNIX user<\/p>\n
ii. Change <tomcat installed directory> ownership to newly created UNIX user<\/p>\n
Usage:<\/strong> For security purpose, tomcat should be run as a separate user with reduced permission, to protect other services running in case of any security hole.<\/p>\n
9. Remove default\/unwanted applications<\/h4>\n
By default, Tomcat comes with following web applications, which may or not be required in a production environment. You can delete them to keep it clean and avoid any known security risk with Tomcat default application.<\/p>\n
i. ROOT \u2013 Default welcome page<\/p>\n
ii. Docs \u2013 Tomcat documentation<\/p>\n
iii. Examples \u2013 JSP and servlets for demonstration<\/p>\n
iv. Manager, host-manager \u2013 Tomcat administration<\/p>\n
Usage:<\/strong> By default, Tomcat comes with sample web applications, which are not be required in a production environment. Clean up and avoid any known security risk with Tomcat default application.<\/p>\n
10. Change SHUTDOWN port and Command<\/h4>\n
By default, tomcat is configured to be shutdown on 8005 port. Do you know you can shutdown tomcat instance by doing a telnet to IP:port and issuing SHUTDOWN command?<\/p>\n
# telnet localhost 8005\nTrying ::1... telnet:\nconnect to address ::1:\nConnection refused Trying 127.0.0.1...\nConnected to localhost.\nEscape character is '^]'.\nSHUTDOWN Connection closed by foreign host.\n#<\/pre>\nYou see having default configuration leads to high-security risk. It\u2019s recommended to change tomcat shutdown port and default command to something unpredictable.<\/p>\n
i. Go to $tomcat\/conf folder<\/p>\n
ii. Modify server.xml by using vim editor<\/p>\n
<Server port=\"8005\" shutdown=\"SHUTDOWN\"><\/pre>\nUsage:<\/strong> Default shutdown port and commands leaves anyone to easily connect and shutdown the server, So the default shutdown port and command must be changed or it should be disabled.<\/p>\n
11. Replace default 404, 403, 500 page<\/h4>\n
Having default page for not found, forbidden, server error exposes Tomcat version and that leads to security risk if you are running with vulnerable version. Let\u2019s look at default 404 page.<\/p>\n
To mitigate, you can first create a general error page and configure web.xml to redirect to general error page.<\/p>\n
i. Go to $tomcat\/webapps\/$application<\/p>\n
ii. Create an error.jsp file<\/p>\n
#vi error.jsp\n<html>\n<head>\n<title>404-Page Not Found<\/title>\n<\/head>\n<body> That's an error! <\/body>\n<\/html><\/pre>\n\n
- Go to $tomcat\/conf folder<\/li>\n
- Add following in web.xml by using vi. Ensure you add before <\/web-app> syntax<\/li>\n<\/ul>\n
<error-page>\n<error-code>404<\/error-code>\n<location>\/error.jsp<\/location>\n<\/error-page>\n<error-page>\n<error-code>403<\/error-code>\n<location>\/error.jsp<\/location>\n<\/error-page>\n<error-page>\n<error-code>500<\/error-code>\n<location>\/error.jsp<\/location>\n<\/error-page><\/pre>\nRestart tomcat server. Now, let\u2019s test it.<\/p>\n
Usage:<\/strong> Default error page served by Tomcat can include the server and its configuration \/ path information that could be considered a vulnerability. To prevent this need to have a custom error page.<\/p>\n
Verification:<\/strong> Restart tomcat server. Now, let\u2019s test it.<\/p>\n
12. Session Timeout<\/h4>\n
The session timeout for all web applications must be set to 20 minutes.
\nThis can be done by editing the file in the $tomcat\/conf\/web.xml and setting the following configuration option:<\/p>\n<session-config>\n<session-timeout>20<\/session-timeout>\n<\/session-config><\/pre>\nUsage:<\/strong> Server terminates automatically, if sessions remains idle for a specific time period<\/p>\n
Pentaho+ Hardening<\/h3>\n
Disable Home Perspective Widgets<\/h4>\n
The default console Home perspective contains the Getting Started widget, which has easy instructions and tutorials for evaluators. The directions below show you how to hide not only the Getting Started widget, but also other Home perspective widgets, as needed:<\/p>\n
i. Shut down the Pentaho+ Server, if it is currently running.<\/p>\n
ii. If you have not deployed yet, navigate to the \/pentaho-platform\/user-console\/source\/org\/pentaho\/mantle\/home\/properties\/config.properties file.<\/p>\n
iii. If you have manually deployed and want to hide widgets at a later time, navigate to \/pentaho-server\/tomcat\/webapps\/pentaho\/mantle\/home\/properties\/config.properties file.<\/p>\n
iv. Find the line that starts with disabled-widgets= and type in the ID of the widget getting-started. You can also disable the Recents and Favorites widgets using the same method, as shown here. Save and close the file.<\/p>\n
v. disabled-widgets=getting-started,recents,favorites<\/p>\n
vi. Locate the \/pentaho-server\/tomcat\/webapps\/pentaho\/mantle\/home and open the index.jsp file with any text editor.<\/p>\n
vii. Find this line and comment it out, then save and close the file.<\/p>\n
viii. <script language='JavaScript' type='text\/javascript' src='https:\/\/admin.brightcove.com\/js\/BrightcoveExperiences.js'><\/script><\/pre>\nix. Start the Pentaho+ Server and log in to the User Console.<\/p>\n
You now have a Home page that is scrubbed of the specified widget(s).<\/p>\n
Turn Autocomplete Off for Web App Login Screen<\/h4>\n
\n
- The User Console’s login settings have autocomplete turned off by default; if you need to, here is how to manually disable the autocomplete.<\/li>\n
- Stop the Pentaho+ Server.<\/li>\n
- Navigate to the \/pentaho-server\/tomcat\/webapps\/pentaho\/jsp directory and open the PUCLogin.jsp file with any text editor.<\/li>\n
- Find the following two sections of text and change the autocomplete entry to off, as shown.<\/li>\n<\/ol>\n
<input id=\"j_username\" name=\"j_username\" type=\"text\" placeholder=\"\" autocomplete=\"off\">\n<input id=\"j_password\" name=\"j_password\" type=\"password\" placeholder=\"\" autocomplete=\"off\"><\/pre>\n\n
- Save and close the PUCLogin.jsp file.<\/li>\n
- Restart the Pentaho+ Server.<\/li>\n
- Autocomplete for user names and passwords is now disabled for the User Console login screen.<\/li>\n<\/ol>\n
Remove Sample Data from the Pentaho+ Server<\/h4>\n
By default, Pentaho+ provides a sample data source and a solution directory filled with example content. These samples are provided for evaluation and testing. Once you are ready to move from an evaluation or testing scenario to development or production, you can remove the sample content. Follow the instructions below to completely remove the Pentaho+ sample data and solutions:<\/p>\n
i. Stop the Pentaho Plus Server.<\/p>\n
ii. Delete the samples.zip file from the \/pentaho-server\/pentaho-solutions\/system\/default-content directory. If you performed a manual WAR build and deployment, then the file path is \/pentaho-server\/pentaho-solutions\/system.<\/p>\n
iii. Edit the \/pentaho\/WEB-INF\/web.xml file inside of the deployed pentaho.war. As laid down by the Pentaho Plus graphical installer and archive packages, this path should be \/pentaho-server\/tomcat\/webapps\/pentaho\/WEB-INF\/web.xml. If you performed a manual WAR build and deployment, then you must adjust the path to fit your configuration.<\/p>\n
iv. Remove the hsqldb-databases section from the \/pentaho\/WEB-INF\/web.xml file:<\/p>\n
v. BEGIN HSQLDB DATABASES<\/p>\n
<!-- [BEGIN HSQLDB DATABASES] -->\n<context-param>\n<param-name>hsqldb-databases<\/param-name>\n<param-value>sampledata@..\/..\/data\/hsqldb\/sampledata<\/param-value>\n<\/context-param>\n<!-- [END HSQLDB DATABASES] --><\/pre>\nvi. Remove the hsqldb-starter\u00a0section from the \/pentaho\/WEB-INF\/web.xml file:<\/p>\n
vii. BEGIN HSQLDB STARTER<\/p>\n
<!-- [BEGIN HSQLDB STARTER] -->\n<listener>\n<listener-class>org.pentaho.platform.web.http.context.HsqldbStartupListener<\/listener-class>\n<\/listener>\n<!-- [END HSQLDB STARTER] --><\/pre>\nviii. Remove the SystemStatusFilter:<\/p>\n
Note:<\/strong> This is not part of the Pentaho samples; it provides error status messages that are only useful for development and testing purposes, and should be removed from a production system.<\/p>\n
<filter>\n<filter-name>SystemStatusFilter<\/filter-name>\n<filter-class>com.pentaho.ui.servlet.SystemStatusFilter<\/filter-class>\n<init-param>\n<param-name>initFailurePage<\/param-name>\n<param-value>InitFailure<\/param-value>\n<description>This page is displayed if the Pentaho+ System fails to properly initialize.<\/description>\n<\/init-param>\n<\/filter><\/pre>\ni. Save and close the web.xml file.<\/p>\n
ii. Delete the \/pentaho-server\/data\/ directory. This directory does not exist if you installed Pentaho with the installation wizard. It contains a sample database, control scripts for that database, the environment settings it needs to run, and SQL scripts to initialize a new repository.<\/p>\n
iii. Restart the Pentaho+ Server.<\/p>\n
iv. Log on to the User Console with the administrator user name and password and go to the Browse Files page.<\/p>\n
\n
- In the Folders pane, expand the Public folder and click to highlight the folder containing the Steel Wheels sample data. Click Move to Trash in the Folder Actions pane and confirm the deletion.<\/li>\n
- Highlight the folder containing the Pentaho Plus Operations Mart sample data. Click Move to Trash in the Folder Actions pane and confirm the deletion.<\/li>\n<\/ol>\n
Your Pentaho+ Server instance is now cleaned of samples and development\/testing pieces, and is streamlined for production.<\/p>\n
Enable JPivot in the User Console<\/h4>\n
We recommend that you use Pentaho+ Analyzer for analytic reporting. However, perform the following steps if you need to enable JPivot on the Pentaho+ Server:<\/p>\n
Caustion:<\/strong> JPivot was deprecated in Pentaho 5.0 and is no longer supported by Pentaho Customer Support.<\/p>\n
i. Shut down the Pentaho Plus Server if it is currently running.<\/p>\n
ii. Navigate to \/pentaho-server\/pentaho-solutions\/system\/pentaho-jpivot-plugin-legacy\/plugin.xml file and delete file.<\/p>\n
iii. Rename the file called \/pentaho-server\/pentaho-solutions\/system\/pentaho-jpivot-plugin-legacy\/plugin.xml.enabled to \/pentaho-server\/pentaho-solutions\/system\/pentaho-jpivot-plugin-legacy\/plugin.xml and save it. You can either turn off the deprecation message for JPivot, or restart the Pentaho at this point.<\/p>\n
iv. Turn Off Deprecation Message for JPivot – Optional<\/p>\n
v. Shut down the Pentaho Plus Server if it is currently running.<\/p>\n
vi. Navigate to the \/pentaho-solutions\/system\/pentaho-jpivot-plugin-legacy\/settings.xml and open the file.<\/p>\n
vii. Change the Boolean value as shown and save the file.<\/p>\n
From:<\/p>\n
<show-deprecation-warning>true<\/show-deprecation-warning><\/pre>\nTo:\n<show-deprecation-warning>false<\/show-deprecation-warning><\/pre>\nRestart the Pentaho+ Server.<\/p>\n
The JPivot plug-in is enabled in the User Console and the deprecation message is turned off.<\/p>\n
Change the Location of the Server Log File<\/p>\n
If you are using Linux, the log4j.xml file is found in \/pentaho-server\/tomcat\/webapps\/pentaho\/WEB-INF\/classes\/.
\nModify the location as shown in the sample below, using the appropriate path to your installation:<\/p>\n<param name=\"File\" value=\"home\/pentaho\/server\/pentaho-server\/logs\/pentaho.log\"\/>\n<param name=\"Append\" value=\"true\"\/><\/pre>\nChange the Quartz Misfire Threshold<\/h4>\n
With Quartz, sometimes scheduled jobs, transformations, or reports might try to run several times when they are manually stopped and restarted, instead of running only once. This is typically caused by the misfireThreshold property in Quartz being set at too high of a number.<\/p>\n
These steps show how to reset the misfireThreshold to a lower numerical value.<\/p>\n
i. Stop the Pentaho+ Server.<\/p>\n
ii. Locate the \/pentaho-server\/pentaho-solutions\/system\/quartz directory.<\/p>\n
iii. Open the quartz.properties file with any text editor.<\/p>\n
iv. Find the property shown below and change the default to a smaller number, such as 5000. The default value represents the number of milliseconds.<\/p>\n
v. org.quartz.jobStore.misfireThreshold = 60000<\/p>\n
vi. Save and close the quartz.properties file.<\/p>\n
vii. Restart the Pentaho+ Server.<\/p>\n
Set System Max Row Limit for Interactive Reports<\/h4>\n
You can prevent too many resources from hitting your database server at once by setting a system-wide maximum row-limit for Pentaho Plus Interactive Reports. Your users can still define their own design-time row limits in PIR, but they will never be able to go over the maximum number of rows that you have specified while designing their reports.<\/p>\n
i. Shut down the Pentaho+ Server.<\/p>\n
ii. Locate the \/pentaho-server\/pentaho-solutions\/system\/pentaho-interactive-reporting directory.<\/p>\n
iii. Open the settings.xml file with any text editor.<\/p>\n
iv. Find the <query-limit> tag and change the default number of 100000 within the tags to the maximum number of rows desired.<\/p>\n
<!– The maximum number of rows that will be rendered in a report on PIR edit and view mode. A zero value means no limit. –><\/p>\n
<query-limit>100000<\/query-limit><\/pre>\ni. Save and close the settings.xml file.<\/p>\n
ii. Start the Pentaho Plus Server.<\/p>\n
If you are migrating content from a previous version, you will need to add the <query-limit> tag to your settings.xml for PIR.<\/p>\n
Roll Back System Max Row Limit<\/h4>\n
These instructions show you how to return the system maximum row limit to the Pentaho 5.3 settings.<\/p>\n
i. Shut down the Pentaho Server.<\/p>\n
ii. Locate the \/pentaho-server\/pentaho-solutions\/system\/pentaho-interactive-reporting directory.<\/p>\n
iii. Open the settings.xml file with any text editor.<\/p>\n
1. To change the maximum number of rows that will be rendered in a Pentaho Interactive Report in edit or view mode, find the <design-query-limit> tag and change the default number of 500 back to 25.<\/p>\n
FROM:<\/p>\n
<design-query-limit>500<\/design-query-limit><\/pre>\nTO:<\/p>\n
<design-query-limit>25<\/design-query-limit><\/pre>\n2. To turn the design-query-limit to be OFF by default, find the <design-query-limit-enabled> tags and change the value to false.<\/p>\n
<design-query-limit-enabled>false<\/design-query-limit-enabled><\/pre>\nSave and close the settings.xml file.<\/p>\n
Restart the server.<\/p>\n
Increase the CSV File Upload Limit<\/h4>\n
You may find that you need to increase the size of the upload limit for your CSV files. These steps guide you through this process.<\/p>\n
i. Go to \/pentaho-server\/pentaho-solutions\/system and open the pentaho.xml file.<\/p>\n
ii. Edit the XML as needed (sizes are measured in bytes):<\/p>\n
<file-upload-defaults>\n<relative-path>\/system\/metadata\/csvfiles\/<\/relative-path>\n<!-- max-file-limit is the maximum file size, in bytes, to allow to be uploaded to the server -->\n<max-file-limit>10000000<\/max-file-limit>\n<!-- max-folder-limit is the maximum combined size of all files in the upload folder, in bytes. -->\n<max-folder-limit>500000000<\/max-folder-limit>\n<\/file-upload-defaults><\/pre>\ni. Save your changes to the file.<\/p>\n
ii. In the User Console, go to Tools > Refresh System Settings to ensure that the change is implemented.<\/p>\n
iii. Restart the User Console.<\/p>\n
Change the Staging Database for CSV Files<\/p>\n
Hibernate is the default staging database for CSV files. Follow these instructions if you want to change the staging database.<\/p>\n
i. Go to \/pentaho-solutions\/system\/data-access and open the settings.xml file with any text editor.<\/p>\n
ii. Edit the settings.xml file as needed. The default value is shown in the sample below.<\/p>\n
iii. <!– settings for Agile Data Access –><\/p>\n
iv. <data-access-staging-jndi>hibernate<\/data-access-staging-jndi><\/p>\n
This value can be a JNDI name or the name of a Pentaho+ Database Connection.<\/p>\n
i. Save and close the file.<\/p>\n
ii. Restart the User Console<\/p>\n
Change the Karaf Startup Timeout Setting<\/h4>\n
Upon start up, the system waits for Karaf to install all of its features before timing out. If you modify Karaf and it now takes longer to install during start up, you may need to extend the default timeout setting to allow Karaf more time to install. The current default timeout is 2 minutes (120000 milliseconds).<\/p>\n
You can change this default timeout by editing the server.properties file.<\/p>\n
1. Stop the Pentaho+ Server.<\/p>\n
2. Navigate to the \/pentaho-server\/pentaho-solutions\/system directory.<\/p>\n
3. Open the server.properties file with any text editor, and search for the karafWaitForBoot parameter.<\/p>\n
4. Uncomment the line containing the parameter and set it to your desired wait time in milliseconds.<\/p>\n
# This sets the amount of time the system will wait for karaf to install all of
\n# it’s features before timing out. The default value is 2 minutes but can be
\n# overridden here.
\n#karafWaitForBoot = 120000<\/p>\n5. Save and close the file.<\/p>\n
6. Restart the Pentaho Plus Server.<\/p>\n
Change the Port Numbers for the Pentaho+ Server<\/h4>\n
Follow the instructions below to change the port through which the Pentaho+ Server runs:<\/p>\n
i. Stop the Pentaho+ Server.<\/p>\n
ii. Navigate to the \/pentaho-server\/tomcat\/conf\/ directory.<\/p>\n
iii. Open the server.xml file with any text editor, and search for the value for Define a non-SSL HTTP\/1.1 Connector. Change the port number in the connector port element below from 8080 to your preferred port number.<\/p>\n
<!-- Define a non-SSL HTTP\/1.1 Connector on port 8080 -->\n<Connector port=\"8080\" maxHttpHeaderSize=\"8192\"\nmaxThreads=\"150\" minSpareThreads=\"25\" maxSpareThreads=\"75\"\nenableLookups=\"false\" redirectPort=\"8443\" acceptCount=\"100\"\nconnectionTimeout=\"20000\" disableUploadTimeout=\"true\" \/><\/pre>\ni. Save and close the server.xml file.<\/p>\n
ii. Navigate to the \/pentaho-server\/pentaho-solutions\/system directory and open the server.properties file with any text editor.<\/p>\n
iii. Change the fully-qualified-server-url entry to match the new port number you specified in server.xml.<\/p>\n
fully-qualified-server-url=http:\/\/localhost:8080\/pentaho\/<\/pre>\nSave and close the file.<\/p>\n
Restart the Pentaho Plus Server.<\/p>\n
If you recently upgraded to Pentaho+ 6.0, you may need to remove the <context-param> entry for the fully-qualified-server-url from the \/tomcat\/webapps\/pentaho\/WEB-INF\/web.xml. If so, restart the Pentaho+ Server after removing it.<\/p>\n
Change the Web Application Name or Port<\/h4>\n
The Pentaho+ Server and web application default port number is 8080. The default web application name is pentaho, which is the name of the .war file archive, the name of the directory that your application server creates, and also part of the URL structure for all content in the User Console.<\/p>\n
If you need to change the User Console application name to something else, or if your Web application server is running on a port other than 8080, follow these instructions for either JBoss or Tomcat.<\/p>\n
Change the Web Application Name on Tomcat<\/h4>\n
These instructions only work on Tomcat servers that are configured to accept context.xml overrides built into deployed .war files. Some Tomcat deployments may not have this feature turned on. You can change the Tomcat configuration on your own, or consult your Tomcat documentation to learn about other methods of changing a web application context. Use the XML snippet in these instructions in whichever configuration file you end up creating or modifying.<\/p>\n
Follow these instructions to change the web application context for a Pentaho+ .war file that you deployed to a Tomcat server. While the example below uses ‘sample’ as the context name, you can use whatever context name you choose.<\/p>\n
1. Stop the server.<\/p>\n
2. Open the pentaho\/server\/pentaho-server\/tomcat\/webapps\/pentaho\/META-INF\/context.xml file in a text editor, and change the pentaho references in the context path tag to your preferred context name. For example, to specify a context name of ‘sample’, modify context path as follows.<\/p>\n
<context path=\"\/sample\" docbase=\"webapps\/sample\/\"><\/pre>\n3. Save and close the file.<\/p>\n
4. Navigate to the pentaho\/server\/pentaho-server\/tomcat\/webapps folder, and rename the pentaho folder to your preferred context name. In this example, rename the pentaho folder to sample.<\/p>\n
5. Edit the pentaho\/server\/pentaho-server\/tomcat\/webapps\/ROOT\/index.jsp file to change the pentaho reference in the URL property to your preferred context name. In this example, use the following line of code to specify ‘sample’ as the new context name:<\/p>\n
<meta http-equiv=\u201drefresh\u201d content=\u201d0;URL=\/sample\u201d><\/pre>\n7.Edit the pentaho\/server\/pentaho-server\/pentaho-solutions\/system\/server.properties file to change pentaho in the value of the fully-qualified-server-url setting to your preferred context name. In this example, set the fully-qualified-server-url as follows.<\/p>\n
fully-qualified-server-url=http:\/\/localhost:8080\/sample\/<\/pre>\n8. Start the server.<\/p>\n
Remove sample users and credentials<\/p>\n
The sample users and the credentials in the pentaho console should be removed due to security purpose.To do that edit the file called \/pentaho-server\/pentaho-solutions\/system\/pentaho.xml and change the line as shown ln below.<\/p>\n
<login-show-sample-users-hint>false<\/login-show-sample-users-hint><\/pre>\nOnce changed, restart the server and check the pentaho user console and make sure that the default sample user credentials gets removed.<\/p>\n","protected":false},"excerpt":{"rendered":"
Increase security and performance tuning in Pentaho Plus and tomcat<\/p>\n","protected":false},"author":23,"featured_media":1871,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[424],"tags":[533,464,534],"class_list":["post-1840","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pentaho","tag-pentaho-hardening","tag-pentaho-security","tag-tomcat-hardening"],"acf":[],"_links":{"self":[{"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/posts\/1840","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/users\/23"}],"replies":[{"embeddable":true,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/comments?post=1840"}],"version-history":[{"count":0,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/posts\/1840\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/media\/1871"}],"wp:attachment":[{"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/media?parent=1840"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/categories?post=1840"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/tags?post=1840"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}