Přeskočit na hlavní obsah

Speed-up ApacheDS LDAP server for testing

Using the ApacheDS for unit testing can be painful if you need to restart/reconfigure the server several times. IT'S SOOO SLOOOOW.

The reason is simple. The default configuration creates a nice directory structure and unpacks all the schema files from JAR file to one of the created directories. Then it creates a file based JDBM partition for you. And it loads your LDIF data to it.

It means many, money, many I/O operations even before the LDAP starts.

Nevertheless, ApacheDS has a nice API to resolve this issue. You will need to make your hands dirty little bit, but it's worth it.

Follow these 3 simple steps and it's all:

  1. Create schema partition class, which stores LDAP schema data in-memory only: sample InMemorySchemaPartition.java
  2. Create DirectoryServiceFactory implementation, which will use in-memory AvlPartitions instead of JDBM and as a schema partition it will use class from the first step: sample InMemoryDirectoryServiceFactory.java
  3. use the new DirectoryServiceFactory to create embedded LDAP

Embedded LDAP

There are 2 simple ways, how to create LDAP server in your unit tests. One uses ApacheDS annotations and the second uses API directly. Here are sample code snippets, which show how to enable the custom InMemoryDirectoryServiceFactory for both of the ways.

Annotations
@CreateDS(
 name = "JBossOrgDS",
 factory=InMemoryDirectoryServiceFactory.class,
 partitions = {
  @CreatePartition(
   name = "jbossorg",
   suffix = "dc=jboss,dc=org",
   contextEntry = @ContextEntry(
    entryLdif =
     "dn: dc=jboss,dc=org\n" +
     "dc: jboss\n" +
     "objectClass: top\n" +
     "objectClass: domain\n\n" )
  )
 })
@CreateLdapServer (
 transports = { @CreateTransport( protocol = "LDAP",  port = 10389, address = "0.0.0.0" ) })
public static void createLdapServer() throws Exception {
 DirectoryService directoryService = DSAnnotationProcessor.getDirectoryService();
 final SchemaManager schemaManager = directoryService.getSchemaManager();
 //import your LDIF here
 ServerAnnotationProcessor.instantiateLdapServer((CreateLdapServer) AnnotationUtils.getInstance(CreateLdapServer.class), directoryService).start();
}

API
DirectoryServiceFactory dsf = new InMemoryDirectoryServiceFactory();
dsf.init("JBossOrgDS");
DirectoryService directoryService = dsf.getDirectoryService();
SchemaManager schemaManager = masterDirectoryService.getSchemaManager();

PartitionFactory pf = dsf.getPartitionFactory();
Partition p = pf.createPartition(schemaManager, "jbossorg", "dc=jboss,dc=org", 1000, workingDir);
p.initialize();
directoryService.addPartition(p);

//import LDIF here

LdapServer ldapServer = new LdapServer();
ldapServer.setServiceName("DefaultLDAP");
Transport ldap = new TcpTransport( "0.0.0.0", 10389, 3, 5 );
ldapServer.addTransports(ldap);
ldapServer.setDirectoryService(directoryService);
ldapServer.start();

I bet your ApacheDS startup time falls down at least by 50% with these in-memory settings.

Komentáře

Populární příspěvky z tohoto blogu

Three ways to redirect HTTP requests to HTTPs in WildFly and JBoss EAP

WildFly application server (and JBoss EAP) supports several simple ways how to redirect the communication from plain HTTP to TLS protected HTTPs. This article presents 3 ways. Two are on the application level and the last one is on the server level valid for requests to all deployments. 1. Request confidentiality in the deployment descriptor The first way is based on the Servlet specification. You need to specify which URLs should be protected in the web.xml deployment descriptor. It's the same approach as the one used for specifying which URLs require authentication/authorization. Just instead of requesting an assigned role, you request a transport-guarantee . Sample content of the WEB-INF/web.xml <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" version="3.1

Ignore the boring SSH error message - Host identification has changed!

The problem If you work with virtual machines in clouds, or you run an SSH server in Docker containers, then you've probably met the following error message during making ssh connection: (I'm connecting through SSH to a docker container) ~$ ssh -p 8822 root@localhost @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is SHA256:smYv5yA0n9/YrBgJMUCk5dYPWGj7bTpU40M9aFBQ72Y. Please contact your system administrator. Add correct host key in /home/jcacek/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /home/jcacek/.ssh/known_hosts:107 remove with: ssh-keygen -f "/home/jcacek/.ssh/know

Enable Elytron in WildFly

Steps to enable Elytron in WildFly nightly builds. There is an ongoing effort to bring a new security subsystem Elytron to WildFly and JBoss EAP. For some time a custom server profile named standalone-elytron.xml  existed beside other profiles in standalone/configuration directory. It was possible to use it for playing with Elytron. The custom Elytron profile was removed now.  The Elytron subsystem is newly introduced to all standard server profiles. The thing is, the Elytron is not used by default and users have to enable it in the subsystems themselves. Let's look into how you can enable it. Get WildFly nightly build # Download WildFly nightly build wget --user=guest --password=guest https://ci.wildfly.org/httpAuth/repository/downloadAll/WF_Nightly/.lastSuccessful/artifacts.zip # unzip build artifacts zip. It contains WildFly distribution ZIP unzip artifacts.zip # get the WildFly distribution ZIP name as property WILDFLY_DIST_ZIP=$(ls wildfly-*-SNAPSHOT.zip) # un