Horde3 - Revision history

Saruman!: changed link

2009-08-31T18:57:21Z

changed link

← Older revision		Revision as of 18:57, 31 August 2009
Line 77:		Line 77:
	More settings can be made, but that can also be done at a later time. For now, click "Generate Horde Configuration". You will be thrown out, and must log back in with the specified admin account (LDAP account "john" in our example).		More settings can be made, but that can also be done at a later time. For now, click "Generate Horde Configuration". You will be thrown out, and must log back in with the specified admin account (LDAP account "john" in our example).

	When ''horde3'' is installed, you can start installing Horde applications. The central part of this is [[IMP - the Internet ~~Mail~~ Program]]		When ''horde3'' is installed, you can start installing Horde applications. The central part of this is [[IMP - the Internet Messaging Program]]

Saruman!: link to imp

2009-08-31T18:56:26Z

link to imp

← Older revision		Revision as of 18:56, 31 August 2009
Line 77:		Line 77:
	More settings can be made, but that can also be done at a later time. For now, click "Generate Horde Configuration". You will be thrown out, and must log back in with the specified admin account (LDAP account "john" in our example).		More settings can be made, but that can also be done at a later time. For now, click "Generate Horde Configuration". You will be thrown out, and must log back in with the specified admin account (LDAP account "john" in our example).

	~~== IMP ==~~		When ''horde3'' is installed, you can start installing Horde applications. The central part of this is [[IMP - the Internet Mail Program]]
	~~apt-get install imp4~~
	~~Now prepare file permissions for web configuration:~~

	~~chmod 777 /etc/horde/imp4/conf.php~~
	~~touch /etc/horde/imp4/conf.bak.php~~
	~~chmod 777 /etc/horde/imp4/conf.bak.php~~

	~~Choose setup from the menu~~ '~~mail(imp)~~'
	~~Generate your configuration (GPG/PGP, user constraints, enable spam/ham report, hooks...).~~

	~~And when you're done change the permissions back~~

	~~chmod 644 /etc/horde/imp4/conf.php~~
	~~chmod 700 /etc/horde/imp4/conf.bak.php~~

	~~And specify your mail server(s) in /etc/horde/imp4/servers.php file~~
	~~$servers['imap'] = array(~~
	~~'name' => 'IMAP Server',~~
	~~'server' => 'localhost',~~
	~~'hordeauth' => 'full',~~
	~~'protocol' => 'imap/notls',~~
	~~'port' => 143,~~
	~~'maildomain' => 'sample.com',~~
	~~'smtphost' => 'localhost',~~
	~~'smtpport' => 25,~~
	~~'realm' => 'sample.com~~',
	'~~preferred' => '',~~
	);

	~~When you are ready, enable IMP in /etc/horde/horde3/registry.php file and verify if all~~ is ~~right. Yes~~, you ~~read well, you MUST enable manually module in registry~~.~~php file after configuration!~~

	$this~~->applications~~[~~'imp'] = array(~~
	~~'fileroot' => '/usr/share/horde3/lib' . '/../imp',~~
	~~'webroot' => $this~~-~~>applications['horde'~~]~~['webroot'~~] ~~. '/imp',~~
	~~'name' => _("Mail"),~~
	~~'status' => 'active',~~
	~~'provides' => array('mail', 'contacts/favouriteRecipients')~~
	);

	~~Change the status from inactive to active~~

Saruman!: /* Web configuration */ adapted for ldap

2009-08-30T20:24:06Z

Web configuration: adapted for ldap

← Older revision		Revision as of 20:24, 30 August 2009
Line 57:		Line 57:
	http://server.local.lan/horde3/		http://server.local.lan/horde3/
	==Web configuration==		==Web configuration==
	Choose setup from the menu 'horde setup'		Choose setup from the menu 'horde setup'. Note: fill at LEAST all the data mentioned hereunder, and only THEN click "Generate Horde Configuration". You '''cannot''' click that button in the mean time to "save your progress", because it will then shut you out of your Horde setup.
	- edit database -> username ~~en WW -~~ connect to database = tcp/ip - localhost ~~- naam~~ database		* edit the data in tab "database"
	- edit preference system -> SQL database		** username: <nowiki>$conf[sql][username]</nowiki> = ''horde''
	- edit authentication -> ~~Administrator~~,~~user@sample~~.~~com - SQL~~ authentication		** password: put after <nowiki>$conf[sql][password]</nowiki> the strong password we put in ''create.mysql.sql.gz''
	~~Choose Users from~~ the ~~menu~~		** connect to database: select <nowiki>$conf[sql][protocol]</nowiki> = ''tcp/ip''
	~~- add users -~~> ~~user@sample~~.~~com~~		** where is that database located: <nowiki>$conf[sql][hostspec]</nowiki> = ''localhost''
			** The database name: <nowiki>$conf[sql][database]</nowiki> = ''horde''
	~~klik generate Horde Configurtion~~		* edit the data in tab "preference system
	~~Could not save~~ the ~~backup configuration file~~ /~~usr/share/horde3/config/conf~~.~~bak~~.~~php~~		** set the preferences driver <nowiki>$conf[prefs][driver]</nowiki> to ''SQL database''
	~~I had to change permissions on~~ the ~~/etc/horde/horde3 folder~~		* edit the data in tab "authentication" - this section depends heavily on how you want to authenticate. Suppose you have an OpenLDAP server on your network, perhaps even on this same server, then it could be something like this:
			** <nowiki>$conf[auth][admins]</nowiki> should have your own LDAP login, e.g. "john"
			** <nowiki>$conf[auth][driver]</nowiki> must be ''LDAP authentication''
			** <nowiki>$conf[auth][params][hostspec]</nowiki> must be the LDAP server, e.g. "localhost"
			** <nowiki>$conf[auth][params][basedn]</nowiki> will be the standard base DN, e.g. "dc=saruman,dc=biz"
			** <nowiki>$conf[auth][params][binddn]</nowiki> must be the account that is allowed to bind, so it can check users; we use "cn=authenticator,dc=saruman,dc=biz"
			** <nowiki>$conf[auth][params][password]</nowiki> contains the password of the binddn, in our case "authenticator"s password ("letmein", I believe it was :-)
			** <nowiki>$conf[auth][params][uid]</nowiki> contains the attribute that contains the login name. This will often be "uid", as it is with us
			** <nowiki>$conf[auth][params][objectclass]</nowiki> must contain an object class filter, with which horde can limit the results of its search. If all your horde users are in one single class, you can simply use that. E.g. we have all users member of "inetOrgPerson" so we can use that value.
			More settings can be made, but that can also be done at a later time. For now, click "Generate Horde Configuration". You will be thrown out, and must log back in with the specified admin account (LDAP account "john" in our example).

	== IMP ==		== IMP ==

Saruman!: /* Configure */ expounded

2009-08-30T19:50:13Z

Configure: expounded

← Older revision		Revision as of 19:50, 30 August 2009
Line 43:		Line 43:

	==Configure==		==Configure==
	To use the web configuration wizard we need to change the ~~following~~		To use the web configuration wizard we need to do a couple of things in directory ''/etc/horde/horde3''. First, we need most files to be owned by root:www-data and have permissions 750. Next, create a backup ''conf.php'' file, named ''conf.bak.php'', and change the permissions on both ''conf*.php'' files to 777:
	chgrp -R www-data /etc/horde/horde3/		chgrp -R www-data /etc/horde/horde3/
	chmod -R 750 /etc/horde/horde3		chmod -R 750 /etc/horde/horde3
	~~chmod 777 /~~etc/horde/horde3/conf.~~php~~		touch etc/horde/horde3/conf.bak.php
	~~cp /etc/horde/horde3/conf~~.php ~~/etc/horde/horde3/conf.php.bak~~		chmod 777 /etc/horde/horde3/conf*.php
	chmod 777 /etc/horde/horde3/conf.php~~.bak~~		Next, we can prepare an alternative location for the log file, in line with our [[Debian_Lenny_base_server\|Lenny base server configuration]]:
			mkdir /var/appsloghorde
	~~Prepare~~ log file:		touch /var/appsloghorde/horde3.log
	touch /var/~~log/horde~~/horde3.log
	chown root.www-data /var/log/horde/horde3.log		chown root.www-data /var/log/horde/horde3.log
	chmod 770 /var/log/horde/horde3.log		chmod 770 /var/log/horde/horde3.log
			Now edit ''/etc/horde/horde3/conf.php'' and remove line 2 and 3.
	Now ~~we can browse to the site~~		We should now be able to browse to the Horde3 admin page, something like:
	~~http:~~//~~192.168.70.9~~/horde3/		http://server.local.lan/horde3/
			==Web configuration==
	~~This will give us~~ the ~~following~~
	~~Horde3 configuration disabled by default because the administration/install wizard gives the whole world too much access to the system. Read /usr~~/~~share~~ /~~doc/horde3/README.Debian~~.~~gz on how to allow access~~.

	~~Change /var/log/horde~~/horde3/~~conf.php and comment line 2 and 3 leave the first line as is.~~

	Choose setup from the menu 'horde setup'		Choose setup from the menu 'horde setup'
	- edit database -> username en WW - connect to database = tcp/ip - localhost - naam database		- edit database -> username en WW - connect to database = tcp/ip - localhost - naam database

Saruman!: Database setup done

2009-08-30T19:34:53Z

Database setup done

← Older revision		Revision as of 19:34, 30 August 2009
Line 21:		Line 21:
	SSLCipherSuite HIGH:MEDIUM		SSLCipherSuite HIGH:MEDIUM
	</Location>		</Location>
	Restart your Apache webserver, and horde3 is operational. However, if you surf to ''<nowiki>http://your.web.server/horde3'' you read this:		Restart your Apache webserver, and horde3 is operational. However, if you surf to ''<nowiki>http://your.web.server/horde3</nowiki>'' you read this:
	Horde3 configuration disabled by default because the administration/install wizard gives the whole world too much access to the system. Read /usr/share/doc/horde3/README.Debian.gz on how to allow access.		{\| border="1"
			\|Horde3 configuration disabled by default because the administration/install wizard gives the whole world too much access to the system. Read /usr/share/doc/horde3/README.Debian.gz on how to allow access.
			\|}
			No worries, we'll get horde operational with the following steps.

	==Database==		==Database==
	Horde needs its own database to keep information. To create that database there are several scripts in ''/usr/share/doc/horde3/examples/scripts/''. We use MySQL:		Horde needs its own database to keep information. To create that database there are several scripts in ''/usr/share/doc/horde3/examples/scripts/''. We use MySQL, so we unpack the MySQL setup script:
	~~gunzip~~ /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql.gz		cd /usr/share/doc/horde3/examples/scripts/sql
	~~and~~ change the password ~~in the script~~ for the user ''horde''. We can run the script		gunzip create.mysql.sql.gz
	localhost:$ '''mysql -u root -p'''		This unpacks ''create.mysql.sql'', in which we need to change the password for the user ''horde'', in line 27-29. They reads
			-- IMPORTANT: Change this password.
			PASSWORD('horde')
			);
			We change the default password ''horde'' to something stronger.
			We can now run the script by feeding it into the MySQL client:
			localhost:# '''mysql -u root -p < /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql.gz'''
	Enter password:		Enter password:
	~~Welcome to~~ the ~~MySQL monitor~~. ~~Commands end with ; or \g~~.		localhost:# _
	~~Your MySQL connection id is 4200~~		Now remove the ''create.mysql.sql.gz'' file, or change the password back to 'horde', or secure access to the file! We don't want anyone to read the horde database password.
	~~Server version: 5~~.~~0.51a-24+lenny1 (Debian)~~

	~~Type~~ '~~help;~~' or '\h' ~~for help. Type '\c~~' to ~~clear~~ the ~~buffer.~~

	~~mysql> '''source /usr/share/doc/horde3/examples/scripts/sql/create~~.~~mysql.sql'''~~

	==Configure==		==Configure==

Saruman!: installation procedure finished

2009-08-30T19:21:47Z

installation procedure finished

← Older revision		Revision as of 19:21, 30 August 2009
Line 2:		Line 2:

	==Installation==		==Installation==
	First install the base package plus dependencies:		First make sure you have a nice little [[LAMP]] server running, with [[Database_101\|MySQL]], [[Apache2_and_PHP5\|Apache2, PHP5]] et cetera.
			Now install the base package plus dependencies:
	apt-get install horde3		apt-get install horde3

	Now make the site available		Now make the site available: in ''/etc/apache2/sites-available'', find the site(s) that will get horde3 enabled. In the site definition files, include the following snippet:
	In ''/etc/apache2/sites-available'' the ~~installation script has already placed a file~~ horde3; the ~~content will closely resemble~~
	Alias /horde3 /usr/share/horde3		Alias /horde3 /usr/share/horde3
	<Directory /usr/share/horde3>		<Directory /usr/share/horde3>
Line 14:		Line 14:
	allow from all 192.168 127.0.0		allow from all 192.168 127.0.0
	</Directory>		</Directory>
			<Files ~ "\.(inc\|bak)$">
			deny from all
			</Files>
			If you include the code in an SSL protected site, you can also add
	<Location /horde3>		<Location /horde3>
	SSLCipherSuite HIGH:MEDIUM		SSLCipherSuite HIGH:MEDIUM
	</Location>		</Location>
	~~You could simply enable~~ this ~~site~~		Restart your Apache webserver, and horde3 is operational. However, if you surf to ''<nowiki>http://your.web.server/horde3'' you read this:
	~~ln -s~~ /~~etc~~/~~apache2~~/~~sites-available~~/horde3 ~~00X-horde3~~		Horde3 configuration disabled by default because the administration/install wizard gives the whole world too much access to the system. Read /usr/share/doc/horde3/README.Debian.gz on how to allow access.
	~~(or use ''a2ensite horde3'')~~. ~~Note that this makes the horde3 package available in every virtual host that you have~~.

	== Database ==		==Database==
	Horde needs its own database to keep information. To create that database there are several scripts in ''/usr/share/doc/horde3/examples/scripts/''. We use MySQL:		Horde needs its own database to keep information. To create that database there are several scripts in ''/usr/share/doc/horde3/examples/scripts/''. We use MySQL:
	gunzip /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql.gz		gunzip /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql.gz
Line 35:		Line 38:
	mysql> '''source /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql'''		mysql> '''source /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql'''

			==Configure==

	== Configure ==

	To use the web configuration wizard we need to change the following		To use the web configuration wizard we need to change the following
	chgrp -R www-data /etc/horde/horde3/		chgrp -R www-data /etc/horde/horde3/

Saruman!: started updating

2009-08-30T18:58:17Z

started updating

← Older revision		Revision as of 18:58, 30 August 2009
Line 1:		Line 1:
	A standard howto can be found at [http://wiki.debian.org/Horde]. Our notes on Horde3 installation are the following:		A standard howto for the Horde3 installation can be found at [http://wiki.debian.org/Horde wiki.debian.org]. Our notes on Horde3 installation are the following:

			==Installation==
			First install the base package plus dependencies:
	apt-get install horde3		apt-get install horde3

	Now make the site available		Now make the site available
	In etc/apache2-sites-available ~~there is~~ already a file horde3		In ''/etc/apache2/sites-available'' the installation script has already placed a file horde3; the content will closely resemble
	Alias /horde3 /usr/share/horde3		Alias /horde3 /usr/share/horde3
	<Directory /usr/share/horde3>		<Directory /usr/share/horde3>
Line 15:		Line 17:
	SSLCipherSuite HIGH:MEDIUM		SSLCipherSuite HIGH:MEDIUM
	</Location>		</Location>
			You could simply enable this site
	~~And make the~~ site ~~enabled~~
	ln -s /etc/apache2/sites-available/horde3 00X-horde3		ln -s /etc/apache2/sites-available/horde3 00X-horde3
			(or use ''a2ensite horde3''). Note that this makes the horde3 package available in every virtual host that you have.

	== Database ==		== Database ==
			Horde needs its own database to keep information. To create that database there are several scripts in ''/usr/share/doc/horde3/examples/scripts/''. We use MySQL:
	To ~~make the~~ database there are several scripts in /usr/share/doc/horde3/examples/scripts/. We use ~~MYsql~~:
	gunzip /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql.gz		gunzip /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql.gz
			and change the password in the script for the user ''horde''. We can run the script
			localhost:$ '''mysql -u root -p'''
			Enter password:
			Welcome to the MySQL monitor. Commands end with ; or \g.
			Your MySQL connection id is 4200
			Server version: 5.0.51a-24+lenny1 (Debian)

			Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

			mysql> '''source /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql'''

	~~and change the password in the script for the user horde~~
	~~Run the script~~
	~~mysql -u root -p~~
	~~source /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql~~

Insomnia: /* Configure */

2009-08-30T09:24:21Z

Configure

@@ Line 52: / Line 52: @@
 Change /var/log/horde/horde3/conf.php and comment line 2 and 3 leave the first line as is.
-Klik op setup en klik 'horde setup'
+Choose setup from the menu 'horde setup'
 - edit database			-> username en WW - connect to database = tcp/ip - localhost - naam database
 - edit preference system	-> SQL database
 - edit authentication           -> Administrator,user@sample.com - SQL authentication
 klik generate Horde Configurtion
   Could not save the backup configuration file /usr/share/horde3/config/conf.bak.php
-Not solved yet
+I had to change permissions on the /etc/horde/horde3 folder
-- edit users			-> root
+== IMP ==

Saruman!: added link to debian wiki

2009-08-30T08:08:05Z

added link to debian wiki

← Older revision		Revision as of 08:08, 30 August 2009
Line 1:		Line 1:
			A standard howto can be found at [http://wiki.debian.org/Horde]. Our notes on Horde3 installation are the following:

	apt-get install horde3		apt-get install horde3

82.161.20.132: /* Database */

2009-08-29T20:23:02Z

Database

@@ Line 19: / Line 19: @@
 == Database ==
-To make the database there are several scripts. We use MYsql:
+To make the database there are several scripts in /usr/share/doc/horde3/examples/scripts/. We use MYsql:
   gunzip /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql.gz
@@ Line 26: / Line 26: @@
   mysql -u root -p
   source  /usr/share/doc/horde3/examples/scripts/sql/create.mysql.sql
 Now we can browse to the site
@@ Line 31: / Line 46: @@
 This will give us the following
-  Horde3 configuration disabled by default because the administration/install wizard gives the whole world too much access to the system. Read /usr/share   /doc/horde3/README.Debian.gz on how to allow access.
+  Horde3 configuration disabled by default because the administration/install wizard gives the whole world too much access to the system. Read /usr/share /doc/horde3/README.Debian.gz on how to allow access.
-To use the web configuration wizard we need to change the following
+- edit users			-> root