Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Installation and Upgrades / Re: Webadmin unable to start after upgrading from 6,2 to 7.0
« on: April 05, 2021, 09:01:46 pm »
Only to let others know, I've just upgraded today from 6.2.9 to 7.0 and I'm facing just the same issue.
2
Installation and Upgrades / Re: SOGo not working after update to Zentyal 5.0.1
« on: August 18, 2018, 09:31:07 am »
No. My "solution" was to avoid SOGo webmail altogether. 
3
Installation and Upgrades / SOGo not working after update to Zentyal 5.0.1
« on: February 02, 2018, 10:51:28 am »
I've updated from Zentyal 4.1 to 5.0.1.
After the update, when I try to log into SOGo, I'm redirected to:
https://localhost/(null):/SOGo/so/direzione/Mail
which obviously yelds a 404. Where does that "(null)" in the URL come from? What should be in its place?
After the update, when I try to log into SOGo, I'm redirected to:
https://localhost/(null):/SOGo/so/direzione/Mail
which obviously yelds a 404. Where does that "(null)" in the URL come from? What should be in its place?
4
Installation and Upgrades / Re: SOGo refuses valid credentials after upgrade to Zentyal 5.0.1 [SOLVED]
« on: February 02, 2018, 10:14:57 am »
I don't know if it was bad luck or the Zentyal upgrade, but the problem boiled down to expired passwords... maybe all the password were due to expire just the same day I upgraded to Zentyal 5, or maybe the upgrade to Zentyal enabled password expiration that was previously disabled. Unfortunately I don't know if password expiration was set or not before the upgrade.
Something remains unexplained though: domain logos were working also before removing password expiration.
Something remains unexplained though: domain logos were working also before removing password expiration.
5
Installation and Upgrades / [SOLVED] SOGo refuses valid credentials after upgrade to Zentyal 5.0.1
« on: January 31, 2018, 09:26:55 am »
I've just upgraded a Zentyal instance from 4.1 to 5.0.1.
After upgrade, SOGo doesn't let users log in anymore.
Users can access other Zentyal services like shares and domain logon, so I assume the LDAP & Kerberos parts are working, but SOGo refuses the same credentials.
I've tried copying over the /etc/sogo/sogo.conf from the old installation to the new one, and. I've also tried to follow the suggestion here, to no avail.
In the /var/log/sogo/sogo.log file I get:
Here is what I believe is the relevant part of my current sogo.conf (the one that worked in the old version):
Can you help me spot the problem?
After upgrade, SOGo doesn't let users log in anymore.
Users can access other Zentyal services like shares and domain logon, so I assume the LDAP & Kerberos parts are working, but SOGo refuses the same credentials.
I've tried copying over the /etc/sogo/sogo.conf from the old installation to the new one, and. I've also tried to follow the suggestion here, to no avail.
In the /var/log/sogo/sogo.log file I get:
Code: [Select]
Jan 31 09:40:41 sogod [13184]: <0x0x561c14f67ce0[LDAPSource]> <NSException: 0x561c155e19b0> NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{"error_code" = 49; login = "cn=direzione di agape,cn=users,dc=ufficio,dc=lan"; }
Jan 31 09:40:41 sogod [13184]: SOGoRootPage Login from '192.168.1.253' for user 'direzione' might not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0
Jan 31 09:40:41 sogod [13184]: 192.168.1.253 "POST /SOGo/connect HTTP/1.1" 403 34/64 0.028 - - 0
Here is what I believe is the relevant part of my current sogo.conf (the one that worked in the old version):
Code: [Select]
/* LDAP authentication */
SOGoUserSources = (
{
type = ldap;
id = sambaLogin;
displayName = "SambaLogin";
canAuthenticate = YES;
CNFieldName = cn;
IDFieldName = cn;
UIDFieldName = sAMAccountName;
hostname = "ldap://127.0.0.1";
baseDN = "DC=ufficio,DC=lan";
bindDN = "CN=zentyal-mail-barth,CN=Users,DC=ufficio,DC=lan";
bindPassword = "mWaByi97SfgLAWZQ49GS";
bindFields = (sAMAccountName, mail);
filter = "(mail='*')";
MailFieldNames = (mail, otherMailbox);
},
{
type = ldap;
id = sambaShared;
displayName = "Shared Addressbook";
canAuthenticate = NO;
isAddressBook = YES;
CNFieldName = cn;
IDFieldName = mail;
UIDFieldName = mail;
hostname = "ldap://127.0.0.1";
baseDN = "DC=ufficio,DC=lan";
bindDN = "CN=zentyal-mail-barth,CN=Users,DC=ufficio,DC=lan";
bindPassword = "mWaByi97SfgLAWZQ49GS";
filter = "((NOT isCriticalSystemObject='TRUE') AND (mail=\'*\') AND (NOT objectClass=contact))";
MailFieldNames = (mail, otherMailbox);
},
{
type = ldap;
id = sambaContacts;
displayName = "Shared Contacts";
canAuthenticate = NO;
isAddressBook = YES;
CNFieldName = cn;
IDFieldName = mail;
UIDFieldName = mail;
hostname = "ldap://127.0.0.1";
baseDN = "DC=ufficio,DC=lan";
bindDN = "CN=zentyal-mail-barth,CN=Users,DC=ufficio,DC=lan";
bindPassword = "mWaByi09SfgLAWZQ49GS";
filter = "((((objectClass=person) AND (objectClass=contact) AND ((uidNumber>=2000) OR (mail=\'*\'))) AND (NOT isCriticalSystemObject='TRUE') AND (NOT showInAdvancedViewOnly='TRUE') AND (NOT uid=Guest)) OR (((objectClass=group) AND (gidNumber>=2000)) AND (NOT isCriticalSystemObject='TRUE') AND (NOT showInAdvancedViewOnly='TRUE')))";
mapping = {
displayname = ("cn");
};
MailFieldNames = (mail, otherMailbox);
}
);
/* Web Interface */
SOGoPageTitle = "Zentyal Webmail";
SOGoVacationEnabled = NO;
SOGoForwardEnabled = YES;
SOGoSieveScriptsEnabled = YES;
Can you help me spot the problem?
6
Installation and Upgrades / Re: SOGo fails after an upgrade to Zentyal 5 - SOLVED!
« on: January 25, 2018, 06:14:35 pm »
Sorry for resuming this old thread, but I'm about to do the same things suggested by bragrabb and I'm not sure if I can safely purge the packages without loosing my planner data.
7
Installation and Upgrades / Re: kerberos linux client PAM configuration
« on: February 28, 2014, 11:03:48 am »
And what flavour is the one that comes bundled in Samba? But, more importantly, how do I add arbitrary service principals in Zentyal? (Maybe you have the answer to the latter question even without knowing the answer to the former one).
And, what are the steps needed to configure a Linux client to authenticate with kerberos provided by Zentyal? These https://help.ubuntu.com/community/Kerberos are not enough, because the server side, in the Zentyal case, does not work that way (kadmin error reported above).
And, what are the steps needed to configure a Linux client to authenticate with kerberos provided by Zentyal? These https://help.ubuntu.com/community/Kerberos are not enough, because the server side, in the Zentyal case, does not work that way (kadmin error reported above).
8
Installation and Upgrades / kerberos linux client PAM configuration
« on: February 28, 2014, 10:36:45 am »
Hello everybody,
I know that cross posting is Bad Practice (TM), but someone told me I likely posted my request in the wrong group, so I bring it to your attention instead:
https://lists.ubuntu.com/archives/xubuntu-users/2014-February/006563.html
After I posted that question, someone else in a IRC channel told me that I should add service principals to my Zentyal server issuing the kadmin command, but:
# kadmin -p admin/admin
kadmin: kadm5_init_with_password: No KDC found for realm LUCIODOM.MY.ORG
And the question now is also: "how do I add arbitrary service principals to Zentyal?" And: "Is Zentyal using MIT or HEIMDAL kerberos"?
In other words, is there a step-by-step howto for linux kerberos client configuration when the domain controller is Zentyal 3.3?
I know that cross posting is Bad Practice (TM), but someone told me I likely posted my request in the wrong group, so I bring it to your attention instead:
https://lists.ubuntu.com/archives/xubuntu-users/2014-February/006563.html
After I posted that question, someone else in a IRC channel told me that I should add service principals to my Zentyal server issuing the kadmin command, but:
# kadmin -p admin/admin
kadmin: kadm5_init_with_password: No KDC found for realm LUCIODOM.MY.ORG
And the question now is also: "how do I add arbitrary service principals to Zentyal?" And: "Is Zentyal using MIT or HEIMDAL kerberos"?
In other words, is there a step-by-step howto for linux kerberos client configuration when the domain controller is Zentyal 3.3?
Pages: [1]