Novel edirectory OIDs for Livelink Directory Service LDAP RO synchronisation

Hi all I'm now in the process of setting up eDirectory for LDAP synchronisation and authentication with Livelink 9.2 I was wondering if you could advise on that. Our Novel eDirectory manager is worried about extending the eDirectory schema with unregistered OIDs. Can I reassure him we won't make any damage? Or could we even register these OIDs ourselves? As far as you know, is there any suggested naming convention change to ot-livelink-schema.conf for eDirectory?

Find more posts tagged with

Comments

Chris_Wagg

Message from Chris Wagg via eLinkActually Bettina, If you are using LDAP read only synch, you don't need to add Livelinkschema. The added schema is only required if you are doing an LDAPsynch (we usually call it a write back synch to differentiate it from aread only LDAP synch. Please have a look at this KB article whichdescribes some of the advantages and disadvantages of different forms ofsynch:https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=4028432&objAction=ArticleView&viewType=1I hope this helps.---------------------------------------Chris WaggSenior Product SpecialistLivelink Escalations Support TeamOpen Text CorporationPh: 800-540-7292--------------------------------------------Original Message-----From: eLink Discussion: Livelink Directory Services Discussion[mailto:directoryservices@elinkkc.opentext.com] Sent: Thursday, September 20, 2007 7:49 AMTo: eLink RecipientSubject: Novel edirectory OIDs for Livelink Directory Service LDAP ROsynchronisationNovel edirectory OIDs for Livelink Directory Service LDAP ROsynchronisation Posted by Mastroianni, Bettina on 09/20/2007 07:48 AMHi all I'm now in the process of setting up eDirectory for LDAP synchronisationand authentication with Livelink 9.2 I was wondering if you could adviseon that. Our Novel eDirectory manager is worried about extending the eDirectoryschema with unregistered OIDs. Can I reassure him we won't make anydamage? Or could we even register these OIDs ourselves? As far as youknow, is there any suggested naming convention change toot-livelink-schema.conf for eDirectory?[To reply to this thread, use your normal E-mail reply function.]============================================================Discussion: Livelink Directory Services Discussionhttps://knowledge.opentext.com/knowledge/llisapi.dll/open/3062146Livelink Server:https://knowledge.opentext.com/knowledge/llisapi.dllTo Unsubscribe from this Discussion, send an e-mail tounsubscribe.directoryservices@elinkkc.opentext.com.

Bettina_Mastroianni

Sorry, I'm not clear; are you saying on eDirectory we don't need to create: attribute llserverinfo 1.3.6.71.140.100.1.1.2.1 cisattribute llquery 1.3.6.71.140.100.1.1.2.2 cisobjectclass LivelinkUser oid 1.3.6.71.140.100.1.1.1.1 requires objectclass allows llserverinfoobjectclass LivelinkGroup oid 1.3.6.71.140.100.1.1.1.2Apparentely there must be a permission problem as I can't access the link.Many thanksBettina

Chris_Wagg

Message from Chris Wagg via eLinkThe purpose of creating this schema is to allow you to identify toLivelink which users are to be synchronized. The LDAP write back synchactually writes to the llserverinfo attribute, so for that type ofsynch, you need to have the additional schema. With an LDAP read-onlysynch, we are not looking for this attribute to write to, so you can useany attribute you want to identify which users are to be synchronized.With LDAP read only, you use a search filter to choose whichusers/groups to synch rather than looking specifically for llserverinfo.Can you send a screen shot of the error that you get when accessing thelink that I sent? ---------------------------------------Chris WaggSenior Product SpecialistLivelink Escalations Support TeamOpen Text CorporationPh: 800-540-7292--------------------------------------------Original Message-----From: eLink Discussion: Livelink Directory Services Discussion[mailto:directoryservices@elinkkc.opentext.com] Sent: Thursday, September 20, 2007 8:34 AMTo: eLink RecipientSubject: Can't access the linkCan't access the linkPosted by Mastroianni, Bettina on 09/20/2007 08:31 AMSorry, I'm not clear; are you saying on eDirectory we don't need tocreate: attribute llserverinfo 1.3.6.71.140.100.1.1.2.1cisattribute llquery 1.3.6.71.140.100.1.1.2.2cisobjectclass LivelinkUser oid 1.3.6.71.140.100.1.1.1.1 requires objectclass allows llserverinfoobjectclass LivelinkGroup oid 1.3.6.71.140.100.1.1.1.2Apparentely there must be a permission problem as I can't access thelink.Many thanksBettina [To reply to this thread, use your normal E-mail reply function.]============================================================Topic: Novel edirectory OIDs for Livelink Directory Service LDAP ROsynchronisationhttps://knowledge.opentext.com/knowledge/llisapi.dll/open/12826404Discussion: Livelink Directory Services Discussionhttps://knowledge.opentext.com/knowledge/llisapi.dll/open/3062146Livelink Server:https://knowledge.opentext.com/knowledge/llisapi.dllTo Unsubscribe from this Discussion, send an e-mail tounsubscribe.directoryservices@elinkkc.opentext.com.

Bettina_Mastroianni

I've realised in your reply the discussion formatting had split up the url on two different lines, so the url was incorrect.I've just emailed myself the article.Many thanksBettina