Issue #18 has been updated by Rémy-Christophe Schermesser.
We (Jonathan, Sebastien and me) decided for this new configuration format in
the FOSDEM, what do you think of it ?
<pre class="xml">
<connections>
<connection type="ldap">
<name>myAdServer</name>
<url>ldap://localhost:1390/dc=AD,dc=net</url>
<username>cn=manager,dc=AD,dc=net</username>
<password>secret</password>
<referral>ignore</referral>
<derefAliases>never</derefAliases>
<factory>com.sun.jndi.ldap.LdapCtxFactory</factory>
<version>3</version>
<authentification>simple</authentification>
<pageSize>10</pageSize>
<tls>true</tls>
</connection>
<connection type="database">
<name>myHSQLDBServer</name>
<url>jdbc:hsqldb:file:hsqldb/lsc</url>
<username>elilly</username>
<password></password>
<driver>org.hsqldb.blabla</driver>
</connection>
</connections>
<audits>
<audit type="csv">
<name>csv</name>
<operations>create, delete</operations>
<attributes>cn, dn</attributes>
<separator>;</separator>
<append>true</append>
<file>/tmp/log.csv</file>
</audit>
<audit type="ldif">
<name>ldif</name>
<operations>create, delete</operations>
<append>false</append>
<file>/tmp/log.ldif</file>
</audit>
</audits>
<services>
<service type="SimpleJndiSrcService">
<name>myADAccount</name>
<connection>myAdServer</connection>
<baseDn>ou=people</baseDn>
<pivotAttributes>dn, cn</pivotAttributes>
<fetchAttributes>uid, mail, cn</fetchAttributes>
<dn>'cn=' + srcBean.getAttributeValueById('uid')</dn>
<getAllFilter>(&(objectClass=inetOrgPerson)(uid=*))</getAllFilter>
<getOneFilter>(&(objectClass=inetOrgPerson)(uid={uid}))</getOneFilter>
</service>
<service type="SimpleJndiDstService">
<name>myDestination</name>
<connection>myAdServer</connection>
</service>
</services>
<tasks>
<task>
<name>myTask</name>
<source>myADAccount</source>
<destination>myDestination</destination>
<auditLogs>
<audit>csv</audit>
<audit>ldif</audit>
</auditLogs>
<conditions>
<create>1 > 0</create>
<update>src.getAttr('updateTimeStamp') >
dst.getAttr('updateTimeStamp')</update>
<delete>false</delete>
<modrdn>false</modrdn>
</conditions>
<syncoptions class="XmlBasedSyncOptions">
<attribute>
<name>cn</name>
<createValue>toto</createValue>
<defaultValue>toto</defaultValue>
<forceValue>toto</forceValue>
<policy>(force|keep|merge)</policy>
</atttibute>
</syncoptions>
</task>
</tasks></pre>
----------------------------------------
Feature #18: Change the configuration format to something more adaptable
http://tools.lsc-project.org/issues/show/18
Author: Jonathan Clarke
Status: Feedback
Priority: Normal
Assigned to:
Category: Core
Target version: Sometime in the future
XML?
YAML?
Think about it being parsed/written by a web interface.
WIP :
h2. XML :
+ Very easy to read/write for a computer
+ With CDATA we can write multiple lines JS
- Very hard to read/write for a human
h2. YAML :
+ Easy to read/write for a human/computer
+ Can write multiple lines JS
h2. Properties :
+ Easy to read/write for a human/computer
+ Can reference other properties
- Can not write multiple lines JS
h2. NeXt/ Open Step configuration files
See :
http://commons.apache.org/configuration/apidocs/org/apache/commons/configuration/plist/PropertyListConfiguration.html
+ Easy to read/write for a human/computer
- Can not write multiple lines JS
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://tools.lsc-project.org/my/account
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-dev mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-dev
