Another EGroupware install problem

[riess82]

Installing EGroupware brought 3 new problems for me.

For some reason I had to add a firewall exception to port 3306 mysql. I did not take the time so far to limit the access to the docker ips.

Second problem: the random password for the egroupware-user was too short for my domain policy and was rejected. I put a new password in /etc/egroupware.secret. Removed the EGroupware app again and installed new.

The third problem leaves me guessing for now:
After logging in as Administrator I open any account and try to change the folder layout, for example from “INBOX/Sent” to “Sent”. When I try to save, i get “Authentication failed”.

I have taken the password from /etc/dovecot/master-users and inserted it for the dovecotadmin, still authentication failed. I have tested the password from the file using telnet, login works from telnet.

Any help would be great.

[StefanU]

Hi riess82.

@riess82

For some reason I had to add a firewall exception to port 3306 mysql.

I can’t reproduce that.
I have EGroupware running on a current UCS and there are no problems with new installations.

@riess82

the random password for the egroupware-user

Which EGroupware user?

For the first login, use the UCS admin…
See also:
https://help.egroupware.org/t/where-do-i-find-the-admin-credentials-after-installation/74246#UCS

@riess82

After logging in as Administrator I open any account and try to change the folder layout, for example from “INBOX/Sent” to “Sent”.

That comes from your Mail-Server!
The standard folders or the schema cannot be changed via EGroupware.

Stefan

[riess82]

I fear I have to disagree:

I am not the only one with the firewall problem, see Kein Zugriff auf die Datenbank durch eGroupware und Wordpress - UCS - Univention Corporate Server - Univention Help

Egroupware user gets created in the postinst under LDAP /egroupeware/egroupware-[mailservername] with a random password in above mentioned file. If that password does not fulfill the password policy requirements, things get messy.

Standard folder schema for the EGroupware install is mentioned in /var/lib/univention-appcenter/apps/egroupware/compose/docker-compose.yml, so even if it comes from the mailserver, EGW uses those. And I was able to change those folders in my test installation successfully, so I am absolutely sure it could and should work. Please also have a look at Struktur der Mailbox ändern - EGroupware Mail - EGroupware Help Forum for details.

[StefanU]

@riess82

I fear I have to disagree:

I cannot reproduce this.
We have not received any reports from customers either.

What is there to disagree with?

---

@riess82

Egroupware user gets created

@StefanU

Which EGroupware user?

EGroupware only creates the anonymous user.

---

@riess82

After logging in as Administrator I open any account and try to change the folder layout,

Please show me how you do it.

Stefan

[riess82]

that user: from /usr/lib/univention-install/50egroupware.inst:

udm users/user create “$@” --ignore_exists
–position “cn=egroupware,$ldap_base”
–set username=“$username”
–set password=“$password”
–set firstname=“$SERVICE Service”
–set lastname=“LDAP Account”
–set description=“Account used by $SERVICE to authenticate against LDAP directory”
–set objectFlag=“hidden”
–set primaryGroup=“cn=$groups_default_domainadmins,cn=groups,$ldap_base”
–option ldap_pwd || die

Here is a screenshot from my test install, where changing the folders worked. As Administrator I click on any user and select “E-Mail-Konto”

Here are the screenshots from my future production system:

[riess82]

Thank you so much Ralf!

change checking admin-credentials to be no longer fatal, just display a info-message with the error

As per instructions I received from RalfEGroupware, the patch can be manually added to docker or you can wait for the next maintainance release.