Simon,

it would be nice if users of other OC_User* classes would be manageable under 
the "normal" Users functions automatically. Each class needs to implement this 
manually, however. LDAP does this rather nicely [1]. For one installation, I 
did locally modify the DAV auth app to add the users to the local DB on login, 
which could be done as well. It would be nice if more of the attribute handling 
would be done by generic code in ownCloud.

I haven't had problems with settings being overridden, but maybe this is due to 
the fact that I have installed *.deb packages and am upgrading using apt.

Maybe you could modify the IMAP auth app to offer an option to have 
novalidate-cert added (or switch to an "official" certificate…)

Beste Grüsse,
-Marcel Waldvogel

[1] However, while both local and LDAP users are sorted alphabetically, they 
are joined in groups of 10 each, which results in a weird sorting order in the 
end.

Am 23.01.2013 um 17:27 schrieb Simon Brereton <[email protected]>:

> Hi Marcel
> 
> No, adding the curly brace didn't help.
> 
> I managed to get it to work - I think correctly* - but adding the
> following variables - user_id and password such:
>  'user_backends'=>array(
>            array(
>                        'class'=>'OC_User_IMAP',
> 
> 'arguments'=>array('{mail.redacted.net:143/imap/tls/novalidate-cert}INBOX',"user_id","password")
>              )
>      )
> 
> *correctly here means that valid user accounts log in (and preferences
> are saved across sessions.  Invalid users are not able to log in.
> 
> There are two small hitches that I've found thus far.
> 1)  Authenticating users are not added to the users tab in the
> administration account
> 2)  I would like to disable/remove the adminstration account I created
> on install and assign the administration rights to one of the
> authenticating users (mine).
> 
> One other concern occurred to me yesterday - this needs to be moved to
> a config.local.php file to avoid being overwritten by an upgrade.
> Does Owncloud have such a facility?
> 
> If you can help me fix either of those two issues (the first is the
> most critical), that would be great.  I'm in the process of moving,
> but I will try to write more comprehensive documentation on the
> imap_open snippet (I'm not a php programmer, but I know what options
> apply to my imap server - others may not.
> 
> Cheers
> 
> Simon
> 
> 
> 
> 
> On 23 January 2013 06:50, Marcel Waldvogel
> <[email protected]> wrote:
>> Does adding an open curly brace before mail.example.com fix the problem?
>> 
>> But maybe the error message should be more meaningful…
>> 
>> Viele Grüsse,
>> -Marcel Waldvogel
>> (kurz&bündig da mobil)
>> 
>> Am 22.01.2013 um 22:52 schrieb Simon Brereton <[email protected]>:
>> 
>>> This is where it gets interesting.  The example in the link you sent
>>> seems straightforward:
>>> 
>>> 'user_backends'=>array(
>>> array(
>>>   'class'=>'OC_User_IMAP',
>>>   'arguments'=>array('{imap.gmail.com:993/imap/ssl}INBOX')
>>> )
>>> )
>>> 
>>> After adding it to my config/config.php it looks like:
>>> <?php
>>> $CONFIG = array (
>>> 'passwordsalt' => 'redacted',
>>> 'datadirectory' => '/var/www/domains/redacted.net/owncloud/data',
>>> 'dbtype' => 'mysql',
>>> 'version' => '4.90.0',
>>> 'dbname' => 'cloud',
>>> 'dbhost' => 'localhost',
>>> 'dbtableprefix' => 'oc_',
>>> 'dbuser' => 'oc_redacted',
>>> 'dbpassword' => 'redacted',
>>> 'installed' => true,
>>> 'instanceid' => 'redacted',
>>> 'user_backends'=>array(
>>> array(
>>>   'class'=>'OC_User_IMAP',
>>>   'arguments'=>array('mail.example.com:143/imap/tls}INBOX')
>>> )
>>> )
>>> );
>>> 
>>> 
>>> If I add in the imap snippet I get this error in my owncloud logs:
>>> Error core User backend OC_User_IMAP not found. January 22, 2013, 16:47
>>> 
>>> Any advice?
>>> 
>>> Cheers
>>> 
>>> Simon
>>> 
>>> 
>>> On 21 January 2013 12:44, Daniel Molkentin <[email protected]> wrote:
>>>> It's documented in
>>>> http://doc.owncloud.org/server/4.5/admin_manual/custom_user_backend.html. 
>>>> On
>>>> GitHub, this is
>>>> https://github.com/owncloud/documentation/blob/stable45/admin_manual/custom_user_backend.rst.
>>>> It should probably be renamed and moved so that it fits with the LDAP
>>>> chapter:
>>>> https://github.com/owncloud/documentation/blob/stable45/admin_manual/auth_ldap.rst
>>>> 
>>>> 
>>>> 
>>>> On 21.01.2013, at 13:40, Simon Brereton wrote:
>>>> 
>>>> I would still appreciate documentation on how to authenticate against an
>>>> IMAP server if anyone has written this.  If you only have rough notes, I'll
>>>> expand them and polish them.
>>>> 
>>>> Simon
>>>> 
>>>> On Jan 21, 2013 7:26 AM, "Bernhard Posselt" <[email protected]> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> On the 19th of february is the documentation freeze. It would be nice if
>>>>> we finished the documentation one week before the deadline to be able to
>>>>> make corrections.
>>>>> 
>>>>> To do that, we need to have a list containing stuff that is not done yet.
>>>>> 
>>>>> Please create issues on https://github.com/owncloud/documentation/issues
>>>>> 
>>>>> _______________________________________________
>>>>> Owncloud mailing list
>>>>> [email protected]
>>>>> https://mail.kde.org/mailman/listinfo/owncloud
>>>> 
>>>> _______________________________________________
>>>> Owncloud mailing list
>>>> [email protected]
>>>> https://mail.kde.org/mailman/listinfo/owncloud
>>>> 
>>>> 
>>>> --
>>>> www.owncloud.com - Your Data, Your Cloud, Your Way!
>>>> 
>>>> ownCloud GmbH, GF: Markus Rex, Holger Dyroff
>>>> Schloßäckerstrasse 26a, 90443 Nürnberg, HRB 28050 (AG Nürnberg)
>>> _______________________________________________
>>> Owncloud mailing list
>>> [email protected]
>>> https://mail.kde.org/mailman/listinfo/owncloud

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud

Reply via email to