https://bugs.contribs.org/show_bug.cgi?id=10224

--- Comment #8 from Jean-Philippe Pialasse <[email protected]> ---
we could simplify to this:


       public function authusername($userId, $toHorde)
      {
       // strip the domain off
        $userId = substr($userId, 0, strpos($userId, '@'));
        return $userId;
             }
this way:
1/ all users will auth to the imap using their login as username helping in 
bug :
2/ configuration will always be stored under username, no lost configuration in
case primary domain or connecting domain is changed
3/ no more issue to display domain name as *.co.uk


after few tests:
- if we log with different domains name with horde 5 contraryto horde 3, you
will lose your calendar, addressbook and so on because they are encoded using a
specifi string, so we must keep the same username now.
calendar_id was username without@domain, so you were able to connect to the
same one.
now this is a string defined in horde preference against username | kronolith|
default_share

this way few things will display bad :
- servername will be used as domain for the emails; not ideal for a domain used
on a secondary ibay.
- calendar name are truncated and display as "Calendar of " in place of
"Calendar of Admin"
- address book will display as "Address book of " in place of "Address book of
"
- same issue for tasks...

also I can see default calendar is set to
https://sme10.com/horde/rpc.php/kronolith//qeEGij67CcgMBWCPTQTehT4.ics instead
of  https://sme10.com/horde/rpc.php/kronolith//admin.ics as seen on SME9 and
horde 3

I believe that all those issues could be templated  and fixed as an example I
can see /home/httpd/html/horde/kronolith/config/prefs.php on SME9 horde 3
define the default share..., we could make a prefs.local.php or a pref.d/


an alternative could be 

      public function authusername($userId, $toHorde)
      {
          $vdomain = getenv('HTTP_HOST');
        if ($toHorde) {
            return ltrim(rtrim(Horde_String::lower($userId))) . '@' . $vdomain;
        } else {
$userId = substr($userId, 0, strpos($userId, '@'));
                 return $userId;
}
}

this will still store as username@domain. 
this is not affected by primary domain change as long as the domain is still
accessible and we keep using it .


alternativelly
$vdomain = getenv('HTTP_HOST')
could be
$vdomain = $DomainName (with this value obtained from the db)

and a script would be needed to migrate username when changing Primary domain
name.....

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/

Reply via email to