PortalInstall - Revision history

STEPHANE GERARD stgerard@vub.ac.be: /* Switching to https */

2017-07-21T18:29:35Z

Switching to https

← Older revision		Revision as of 18:29, 21 July 2017
Line 66:		Line 66:
	clientAuth="false" sslProtocol="TLS" />		clientAuth="false" sslProtocol="TLS" />
	</pre>		</pre>
			After having restarted the portal, you can access it through an 'https://' URL.

	{{TracNotice\|{{PAGENAME}}}}		{{TracNotice\|{{PAGENAME}}}}

2017-07-21T18:27:29Z

Switching to https

← Older revision		Revision as of 18:27, 21 July 2017
Line 60:		Line 60:
	chown guse:guse /home/guse/.keystore		chown guse:guse /home/guse/.keystore
	</pre>		</pre>
	Now you can activate the https connector :		Now you can activate the https connector by uncommenting the following stenza in server.xml :
			<pre>
			<Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol"
			maxThreads="150" SSLEnabled="true" scheme="https" secure="true"
			clientAuth="false" sslProtocol="TLS" />
			</pre>

	{{TracNotice\|{{PAGENAME}}}}		{{TracNotice\|{{PAGENAME}}}}

2017-07-21T18:24:40Z

Securing the portal

@@ Line 35: / Line 35: @@
 == Securing the portal ==
 As explained in the manual, it is very important to change the default password of the test@liferay.com user right after the first login. But that's not enough ! After you've done with the Service Wizard step (<nowiki>http://<URL_install_backend>:8080/information</nowiki>), shutdown the portal, change the password of the admin user in tomcat-users.xml, and create the file /home/guse/guse/apache-tomcat-7.0.55/conf/Catalina/localhost/manager.xml with the following content :
 <pre>
@@ Line 47: / Line 49: @@
 After the restart of the portal, access to <nowiki>http://<URL_install_backend>:8080/manager</nowiki> will be restricted to the IPs allowed in manager.xml. If you don't do this, you will undergo brute force attacks (trying to guess the admin password), and this kind of attacks will put some pressure on the server.
 {{TracNotice|{{PAGENAME}}}}

2017-07-14T12:29:38Z

Securing the portal

← Older revision		Revision as of 12:29, 14 July 2017
Line 43:		Line 43:
	</pre>		</pre>

	After the restart of the portal, access to <nowiki>http://<URL_install_backend>:8080/manager</nowiki> will be restricted to the IPs allowed in manager.xml. If you don't do this, you will undergo brute force attacks (trying to guess the admin password), and this kind of ~~attack~~ will put some pressure on the server.		(Don't forget to "chown guse:guse" this file !)

			After the restart of the portal, access to <nowiki>http://<URL_install_backend>:8080/manager</nowiki> will be restricted to the IPs allowed in manager.xml. If you don't do this, you will undergo brute force attacks (trying to guess the admin password), and this kind of attacks will put some pressure on the server.


	{{TracNotice\|{{PAGENAME}}}}		{{TracNotice\|{{PAGENAME}}}}

2017-07-14T12:25:45Z

Securing the portal

← Older revision		Revision as of 12:25, 14 July 2017
Line 43:		Line 43:
	</pre>		</pre>

	After the restart of the portal, access to <nowiki>http://<URL_install_backend>:8080/manager</nowiki> will be restricted to the IPs allowed in manager.xml.		After the restart of the portal, access to <nowiki>http://<URL_install_backend>:8080/manager</nowiki> will be restricted to the IPs allowed in manager.xml. If you don't do this, you will undergo brute force attacks (trying to guess the admin password), and this kind of attack will put some pressure on the server.


	{{TracNotice\|{{PAGENAME}}}}		{{TracNotice\|{{PAGENAME}}}}

2017-07-14T12:24:03Z

← Older revision		Revision as of 12:24, 14 July 2017
Line 34:		Line 34:
	And then, follow the installation procedure from the manual.		And then, follow the installation procedure from the manual.

			== Securing the portal ==
			As explained in the manual, it is very important to change the default password of the test@liferay.com user right after the first login. But that's not enough ! After you've done with the Service Wizard step (<nowiki>http://<URL_install_backend>:8080/information</nowiki>), shutdown the portal, change the password of the admin user in tomcat-users.xml, and create the file /home/guse/guse/apache-tomcat-7.0.55/conf/Catalina/localhost/manager.xml with the following content :
			<pre>
			<Context antiResourceLocking="false" privileged="true" docBase="${catalina.home}/webapps/manager">
			<Valve className="org.apache.catalina.valves.RemoteAddrValve"
			allow="127.0.0.1\|192.168.10.\|193.190.247.\|193.58.172.*" denyStatus="404" />
			</Context>
			</pre>

			After the restart of the portal, access to <nowiki>http://<URL_install_backend>:8080/manager</nowiki> will be restricted to the IPs allowed in manager.xml.

	{{TracNotice\|{{PAGENAME}}}}		{{TracNotice\|{{PAGENAME}}}}

2017-07-14T12:14:24Z

Installation of release 3.7.x

← Older revision		Revision as of 12:14, 14 July 2017
Line 32:		Line 32:
	* copy http://central.maven.org/maven2/javax/transaction/jta/1.1/jta-1.1.jar and http://central.maven.org/maven2/javax/persistence/persistence-api/1.0.2/persistence-api-1.0.2.jar under apache-tomcat-7.0.55/lib/.		* copy http://central.maven.org/maven2/javax/transaction/jta/1.1/jta-1.1.jar and http://central.maven.org/maven2/javax/persistence/persistence-api/1.0.2/persistence-api-1.0.2.jar under apache-tomcat-7.0.55/lib/.

			And then, follow the installation procedure from the manual.



	{{TracNotice\|{{PAGENAME}}}}		{{TracNotice\|{{PAGENAME}}}}

2017-07-14T12:13:32Z

← Older revision		Revision as of 12:13, 14 July 2017
Line 24:		Line 24:
	== Installation process ==		== Installation process ==
	We followed the procedure described in the PDF "gUSE_Install_Wizard_Manual_v3.6.8" to the letter, thus using the wizard.		We followed the procedure described in the PDF "gUSE_Install_Wizard_Manual_v3.6.8" to the letter, thus using the wizard.

			== Installation of release 3.7.x ==
			It has been tested under SL6.8 with java-1.8.0-openjdk-1.8.0.111-0.b15. We have met the problem described in this thread : https://sourceforge.net/p/guse/discussion/1672628/thread/4aa465ec/

			To solve the problem :
			* remove apache-tomcat-7.0.55/lib/javaee-api-5.0-1.jar
			* copy http://central.maven.org/maven2/javax/transaction/jta/1.1/jta-1.1.jar and http://central.maven.org/maven2/javax/persistence/persistence-api/1.0.2/persistence-api-1.0.2.jar under apache-tomcat-7.0.55/lib/.





	{{TracNotice\|{{PAGENAME}}}}		{{TracNotice\|{{PAGENAME}}}}

2015-10-28T13:40:33Z

← Older revision		Revision as of 13:40, 28 October 2015
Line 1:		Line 1:
	{{DISPLAYTITLE:Portal ~~Install~~}}		{{DISPLAYTITLE:Portal installation}}
	== How the machine was prepared ==		== How the machine was prepared ==
	Create a VM in the T2B cloud with 12GB of disk size, 1 CPU, 2GB of RAM, and 2 NICs (one in the public and the other in the private network).		Create a VM in the T2B cloud with 12GB of disk size, 1 CPU, 2GB of RAM, and 2 NICs (one in the public and the other in the private network).

2015-10-28T13:40:05Z

← Older revision		Revision as of 13:40, 28 October 2015
Line 1:		Line 1:
			{{DISPLAYTITLE:Portal Install}}
	== How the machine was prepared ==		== How the machine was prepared ==
	Create a VM in the T2B cloud with 12GB of disk size, 1 CPU, 2GB of RAM, and 2 NICs (one in the public and the other in the private network).		Create a VM in the T2B cloud with 12GB of disk size, 1 CPU, 2GB of RAM, and 2 NICs (one in the public and the other in the private network).