Hi Clement, 1. I suggest to add it always 2. binaryAttributes = attributes to be returned as binary, not string. Mandatory for jpegPhoto, userCertificate, ... sortedBy = LDAP attribute name to sort on so that entries will be returned and paged by the server accordingly saslMutualAuthentication = Reserved For Futur Use : will be activated for Kerberos authentication when functional 3. I agree 4. Hooks: http://tools.lsc-project.org/issues/59 5. Plugins mechanism is provided to cover both license issues (i.e. NIS jar) and to provide extensibility for closed source services. That's why NIS configuration is described in the standard XML even if it is a plugin. Extending XML is possible but quite time consuming so I'd like to avoid doing it if it is not strictly required.
No problem with your questions: if it is not clear for you, it should be explained. Regards, -- Sebastien BAHLOUL IAM / Security specialist Ldap Synchronization Connector : http://lsc-project.org Blog : http://sbahloul.wordpress.com/ Le 17 avril 2012 10:56, Clément OUDOT <[email protected]> a écrit : > Hi, > > I am trying to update the wiki to document some new parameters. I am > using the XSD file to discover them, so some questions: > > > * LDAP Versions: > > <xsd:simpleType name="ldapVersionType"> > <xsd:restriction base="xsd:string"> > <xsd:enumeration value="VERSION2" /> > <xsd:enumeration value="VERSION_3" /> > </xsd:restriction> > </xsd:simpleType> > > -> we should decide if we have an underscore or not. > > * LDAP connection > > These parameters are not documented : > > <xsd:element > name="saslMutualAuthentication" type="xsd:boolean" > default="false" > minOccurs="0" /> > <xsd:element name="sortedBy" > type="xsd:string" > minOccurs="0" /> > <xsd:element > name="binaryAttributes" type="valuesType" > minOccurs="0" /> > > What is the saslMutualAuthentication? > I suppose sortedBy will use server side sorting, and binaryAttributes > will list binary attributes, is it right? > > > * Audit type > > Why do we have taskNames for CSV audit and not LDIF audit? I think > this parameter is generic and should be declared in auditType > > > * LDAP service > > the getCleanFilter is declared in the generic LDAP service, but it > seems to be effective only for LDAP source service, so it should be > moved. > > * LDAP source service > > These parameters are not documented: > > <xsd:element > name="filterAsync" type="xsd:string" > minOccurs="0" /> > <xsd:element name="dateFormat" > type="xsd:string" > minOccurs="0" /> > <xsd:element name="interval" > type="xsd:int" > default="5" minOccurs="0" /> > > Could you give some examples? Why do we have an "async" filter here? > > * LDAP async source service > > This parameter is not documented: > > <xsd:element > name="synchronizingAllWhenStarting" type="xsd:boolean" > minOccurs="0" > default="true" /> > > What does it mean? Do it prevent to set -a all when launching LSC in async > mode? > > > * Hooks > > A task can have a syncHook and a cleanHook, how does it work? Any examples? > > * Executable plugin / NIS plugin > > The only thing in XSD is jndiExecDstService, so I suppose we have to > use the pluginSourceService and pluginDestinationService to use it? > Does it means that the executable service is no available in LSC core > and need to install the plugin? But NIS seems also to be a plugin, but > is declared in the XSD file (nisSourceService). S what the difference > between a plugin and a built-in service? > > > > Sorry to ask so many questions, but a lot of things are not clear for me. > > > Clément. > _______________________________________________________________ > Ldap Synchronization Connector (LSC) - http://lsc-project.org > > lsc-dev mailing list > [email protected] > http://lists.lsc-project.org/listinfo/lsc-dev >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
