Using gosa-encrypt-passwords on a working GOsa install breaks it

Bug #319685 reported by stephen mulcahy
2
Affects Status Importance Assigned to Milestone
gosa (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gosa

Description: Ubuntu 8.10
Release: 8.10

If I follow this procedure (modified from /usr/share/doc/gosa/README.Debian to include the php5 library required for encryption) on a GOsa installation that is working and allows me to login - it ceases to work afterwards. It looks like the LDAP admin password is corrupted or invalid afterwards.

1. sudo a2enmod headers

2. sudo aptitude install php5-mcrypt

3. sudo gosa-encrypt-passwords

4. Edit the file /etc/gosa/apache.conf and uncomment the following line
#include /etc/gosa/gosa.secrets

5.Restart apache
sudo /etc/init.d/apache2 restart

Is there a bug in the procedure I used or gosa-encrypt-passwords?

Error message from GOsa after following the above procedure

FATAL: Error when connecting the LDAP. Server said 'Could not bind to cn=admin,dc=example,dc=net (while operating on LDAP server ldaps://ldap.example.net)'.

gosa:
  Installed: 2.5.16.1-3ubuntu1
  Candidate: 2.5.16.1-3ubuntu1
  Version table:
 *** 2.5.16.1-3ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/universe Packages
        100 /var/lib/dpkg/status

slapd:
  Installed: 2.4.11-0ubuntu6
  Candidate: 2.4.11-0ubuntu6
  Version table:
 *** 2.4.11-0ubuntu6 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

apache2-mpm-prefork:
  Installed: 2.2.9-7ubuntu3
  Candidate: 2.2.9-7ubuntu3
  Version table:
 *** 2.2.9-7ubuntu3 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
stephen mulcahy (stephen-mulcahy) wrote :

If I change step 4. above to

sudo vi /etc/apache2/conf.d/gosa.conf

and make the change there, the procedure seems to work.

However, at least in my case, logins to GOsa now seem to take forever. This may be a quirk of my setup though (in which case this bug should still be resolved by updating the README as per this comment). It would be good if someone else could test this to see if they also get very slow logins to GOsa.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.