|
|
Show your full config. |
|
bofhus
2018-01-12 20:14
reporter
|
|
|
|
|
I uploaded it as attachement |
|
|
|
Well, probably the bug, which disables posibility of log in to SOGo is minor for you, but it would be nice to confirm the problem at least - is it reproduceable in your enviroment, when it will be corected (if ever?), maybe a little patch? I reported the problem over a month ago... |
|
|
|
You choose to define UIDFieldName = uid
So your primary login method is by uid. Witch is what the "remember username" will retain.
Your config worked "by chance" with 2.2.
How is constructed you directory and especially the rdn of your users ?
With 2.3 there was a change in the multidomain handling which could choke with the existing content of your profiles.
Anyway, in your case you shoud have used UIDFieldName = mail and bindFields = (uid) if your RDNs are uid based.
But if you change it now, all your profiles will be lost or your database need to be script post-processed.
We have the exact opposite:
UIDFieldName = uid and bindFields = (uid) because all our users are using their uid anywhere.
email login still work because it is hardcoded in SOGo, but "remember username" correctly use the uid.
SOGoForceExternalLoginWithEmail = YES is only used for connexions between SOGo and your SMTP server and change nothing to the web login process.
If you have a test platform, do some tests with a clean database and your existing ldap server. |
|
bofhus
2018-01-25 17:46
reporter
~0012537
Last edited: 2018-01-25 17:51
|
This is an example of my user record in LDAP:
dn: cn=u00051,o=bingo,dc=mydomain,dc=local
objectClass: top
objectClass: person
objectClass: knkPerson
cn: u00051
o: bingo
mail: bogdan@bingo.mydomain.pl
uid: u00051-bingo
knkMailQuota: 8192
displayName: <edited>
givenName: <edited>
sn: <edited>
telephoneNumber: <edited>
The UID field is just a number plus an group name (based on domain).
UID is unique forever, mail could be reused.
I set the UIDFieldName = UID because it is the best ID for database, but users always login using the e-mail address.
The bindFields config means the fields, which user can use to login. And "remember username" should remember the username entered by user, not replaced by the another one.
Is it any method, how to destroy the "remember username" feature? I could remove it from the forms (probably?), but what happens if the user already selected this checkbox? |
|
bofhus
2018-02-18 13:00
reporter
|
remember_username.patch (1,095 bytes)
diff -Naur SOGo-2.3.23.orig/UI/MainUI/SOGoRootPage.m SOGo-2.3.23.new/UI/MainUI/SOGoRootPage.m
--- SOGo-2.3.23.orig/UI/MainUI/SOGoRootPage.m 2017-10-18 17:22:39.000000000 +0200
+++ SOGo-2.3.23.new/UI/MainUI/SOGoRootPage.m 2018-02-18 13:22:24.000000000 +0100
@@ -185,6 +185,7 @@
SOGoUserDefaults *ud;
SOGoUser *loggedInUser;
NSString *username, *password, *language, *domain, *remoteHost;
+ NSString *ousername;
NSArray *supportedLanguages;
SOGoPasswordPolicyError err;
@@ -198,6 +199,7 @@
authenticatorInContext: context];
request = [context request];
username = [request formValueForKey: @"userName"];
+ ousername = username;
password = [request formValueForKey: @"password"];
language = [request formValueForKey: @"language"];
rememberLogin = [[request formValueForKey: @"rememberLogin"] boolValue];
@@ -263,7 +265,7 @@
}
if (rememberLogin)
- [response addCookie: [self _cookieWithUsername: username]];
+ [response addCookie: [self _cookieWithUsername: ousername]];
else
[response addCookie: [self _cookieWithUsername: nil]];
|
|
|
|
Near two month passed. No any help from developers. So I decided to make a workaround myself (God, why I have waited so long?). I attached a simple patch. |
|
|
|
Thanks! |
|
