Is the Icon Series able to connect to an OpenLDAP 2.4 server running on a linux server?
The Icon has an LDAP menu indeed, where you can connect to an LDAP server.
The LDAP server needs to provide a scheme compatible with H.350.
Here is a document that describes how to make your OpenLDAP compatible with H.350.
I hope this helps!
Where can I download the LifeSizeIdentity.schema mentioned in the document?
I'm attaching the schema file for Icons, named lifesizeIdentity.schema, and one named LifeSizeIdentity.schema.older for the 220 systems. I'm also attaching the doc, as dropbox links might or might not stay whole forever.
Thanks and hope this helps,
I did some steps in Tutorial install OpenLDAP for lifesize 20130427.pdf, however I gave up to installation.
Could you advise me?
1. I could not find "openldap-2.2.29-db-4.3.29-openssl-0.9.8a-win32_Setup.exe". I think it may be old. So I need to install with v2.4. I think that the guide was made with v2.2. Is there any different steps between v2.2 and v2.4?
2. I am using Windows 2008R2(64bit) server, so I am using openldap for 64bit windows. Am I correct?
3. If question 2 is correct, the directory which is installed OpenLDAP different from guide, correct? (I think it is C:\OpenLDAP.)
4. If I use v2.4, how do I get schema files. Except LifeSizeIdentity.schema? Do I need other schema files?
First, a full disclosure that I am not an LDAP expert so just speaking generally here. Secondly Lifesize Manager will provide an address book to Icons for free (along with other functionality). This is not an official Lifesize document and was created a few years ago so I will assume it references the Open LDAP version that was current at the time it was written and in theory should work with the current version of Open LDAP and use the same schema files (questions 1 and 4). For question 2 that does appear to be the correct version fro a 64 bit machine. For question 3 I believe the default installation path will be C:\Program Files\OpenLDAP.
Thank you for your advice.
I will try anywhere.
Setting up OpenLDAP is very much a professional Linux or Windows system administrator's job, and if you don't have access to those staff resources then there are better alternatives (and even if you can manage to get it working, you may well leave yourself a huge security hole if you don't know how to properly secure it).
As Kevin says, UVC Manager will do it too, but in truth you don't even need UVC Manager. Any UVC installation, even one without any applications enabled or any licences, comes with an LDAP server that will do this out of the box with an easy to use GUI and can be operated much more securely when you don't have access to a system administrator's time. I would strongly recommend people go down this route unless they really know what they're doing.
Just wondering if you have any more information on this method. I do have a UVC installation for ClearSea and Multipoint but not Manager. I would love to see how I can utilize UVC's LDAP server to push phonebooks to my Icon units.
Thomas, Icons do not need a license to be used with Manager. Since you already have a UVC deployment you can enable a trial of Manager and it will not expire (normally 30 days) once you start managing an Icon. Manager will automatically provide an address book to the Icon once it is managed.
This here was very helpful. Finally got it working: Manually Editing the Address Book in your UVC Platform
I read the manual, in step 2, need to add below schema, but i didn't know where i can get these shcema files, could you please tell me the location?
Save the following .SCHEMA files in the in the folder C:\Program Files\OpenLDAP\schema
Gary, there is a zip file in the middle of this thread but I am attaching another just incase you are not able to download them.
In the option b of step 4, it mentioned that "b) Start the slapd service using the command « slapd –d 1 (option 1 for debug mode) "
May i know where i should input the command?
Btw, i use JXplorer ou LDAP Browser as LDAP client, when i input all information to the client as picture 1 in step 5, but pop-up as below
"Error opening connection
[LDAP: error code 49 - Invalid Credentials]"
I input the password as the manual "1234" why pou- up such wrong message?
Did you figure this out?
may i know if we can grant different access right for user?
such as normal user only with read access right, can't modify the setting in server
Still I am getting the same error
Error opening connection
[LDAP: error code 49 - Invalid Credentials]
Retrieving data ...