Kolab + Active Directory

Shaw, Brian bshaw at vsvinc.com
Sat Aug 1 03:38:31 CEST 2015


I believe the reason Kolab uses a dedicated LDAP server is because it 
has a custom schema and using private resources makes life easier when 
you are distributing systems.

That said, you should be able to convert the custom schema file from the 
389-ds format to the AD format.  (You should be able to find a pre-made 
script to do the conversion).  Then you just load the schema file into 
AD and update your Kolab LDAP settings to point to your AD server.

I've not tried this with AD so your mileage may vary but, I have done it 
with other systems and it works reasonably well.

Brian

On 2015-07-30 9:24 am, signaldeveloper at gmail.com wrote:
> I am wondering this too. I have a client who wishes for us to hook
> into their AD and not sure if it's smart or not.
> 
> 
> 
>> On Jul 30, 2015, at 8:02 AM, Dr. Hirn <drhirn at gmail.com> wrote:
>> 
>> Hi,
>> 
>> does it makes sense to try to integrate Kolab into Active Directory?
>> I searched a lot the last days but couldn't find any answers or 
>> documentation on how to. Just old posts to this list regarding the 
>> same question.
>> But maybe something has changed in the meantime?
>> 
>> Regards
>> Stefan
>> _______________________________________________
>> users mailing list
>> users at lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users


More information about the users mailing list