file:/opt/ apache-karaf-3.0.0/etc/org.apache.karaf.log.cfg ... The query argument accepts a query using a LDAP syntax. For instance, you can display details on one specific configuration using the following internal.jaxp; \ CUSTOM DISTRIBUTIONS 145 com.sun.org.apache.xerces.internal.xni; \ com.sun.jndi.ldap Now, we can "assemble" our custom distribution using the Maven assembly plugin. The Maven assembly configurable using the following parameters. Name Description datasource The datasource as on OSGi ldap filter or as JDNI name query.password The SQL query that retries the password of the user query

attached bundle and properties defined in the configuration: The query argument accepts a query using a LDAP syntax. For instance, you can display details on one specific configuration using the following filter: developer guide for details): • JDBCLoginModule uses a database as backend • LDAPLoginModule uses a LDAP server as backend • SyncopeLoginModule uses Apache Syncope as backend • OsgiConfigLoginModule uses Krb5LoginModule uses a Kerberos Server as backend • GSSAPILdapLoginModule uses a LDAP server as backend but delegate LDAP server authentication to an other backend (typically Krb5LoginModule) You can

Cave backend is designed in a plugin way, you can implement your own backend (for instance, JDBC or LDAP backend). • Repository Metadata Generation: Cave creates the repository metadata for you, using the

Cave backend is designed in a plugin way, you can implement your own backend (for instance, JDBC or LDAP backend). • OBR Metadata Generation: Karaf Cave automatically creates the OBR metadata for you,