Mirror of Apache Directory Fortress Commander

Clone this repo:
  1. ee5fbc7 ->wicketstuff v10.0.0 by Shawn McKinney · 3 months ago master
  2. 348ed36 ->spring security v6.2.2 by Shawn McKinney · 3 months ago
  3. d2f4b0a ->wicket v10.0.0 by Shawn McKinney · 3 months ago
  4. 2894cff [maven-release-plugin] prepare for next development iteration by Shawn McKinney · 10 months ago
  5. 68ba080 [maven-release-plugin] prepare release 3.0.0 by Shawn McKinney · 10 months ago 3.0.0

Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at


Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

README for Apache Fortress Web

  • Version 3.0.0
  • Apache Fortress Web System Architecture Diagram Apache Fortress Web System Architecture

Table of Contents

  • Document Overview
  • About Apache Fortress Web
  • Tips for first-time users.
  • SECTION 1. Prerequisites
  • SECTION 2. Download & Install
  • SECTION 3. Configure the Apache Fortress Web deployment
  • SECTION 4. Load Sample Security Policy
  • SECTION 5. Deploy to Tomcat Server
  • SECTION 6. Test with Selenium
  • SECTION 7. Fortress Web properties

Document Overview

This document contains instructions to download, build, and test operations using Apache Fortress Web component.

About Apache Fortress Web

  • A web interface to drive administrative and review functions of Apache Fortress.

  • Uses Apache Wicket as the web framework.

  • Layered security using ...

    • declarative controls:
      • Form-based authentication and coarse-grained role check (Tomcat Realm)
      • Page-level security (Spring Security)
    • programmatic controls:
      • Buttons and link visibility controlled by Apache Fortress
  • Each Page maps to a different Fortress entity (Users, Roles, Perms, Groups, ...) and has four panels:

    1. Nav (optional): links to the pages.
    2. List: search criteria entered and results are shown.
    3. Info: errors or other program messages displayed here.
    4. Detail: where the work gets done, entering data, completing operations.

Tips for first-time users

SECTION 1. Prerequisites

Minimum software requirements:

  • git
  • Java SDK >= 17
  • Apache Maven >= 3
  • Apache Tomcat >= 10
  • LDAP server on the network, configured for Apache Fortress usage.

Everything else covered in the steps that follow. Tested on Debian & Redhat systems.

SECTION 2. Download & Install Apache Fortress Web

  1. Download the source.

a. from git:

git clone --branch 3.0.0 https://gitbox.apache.org/repos/asf/directory-fortress-commander.git/
cd directory-fortress-commander

b. or apache fortress downloads

  1. Build the source.
mvn clean install

SECTION 3. Configure the Apache Fortress Web deployment

1. Copy the fortress.properties example:

cp src/main/resources/fortress.properties.example src/main/resources/fortress.properties

2. Edit the file:

vi src/main/resources/fortress.properties

3. Choose Apache Directory or OpenLDAP server:

a. Prepare fortress for ApacheDS usage:

# This param tells fortress what type of ldap server in use:

# Use value from [Set Hostname Entry]:

# ApacheDS defaults to this:

# These credentials are used for read/write access to all nodes under suffix:

-- Or --

b. Prepare fortress for OpenLDAP usage:

# This param tells fortress what type of ldap server in use:

# Use value from [Set Hostname Entry]:

# OpenLDAP defaults to this:

# These credentials are used for read/write access to all nodes under suffix:

# Optional, If using audit view pages, enable this service account to the slapd access log database:
# For corresponding log user:

3. Enable other options as needed.

a. Look out fortress.properties.example for a list of typical options.

b. Learn more about what properties there are: README-PROPERTIES.

SECTION 4. Load Sample Security Policy

Run maven install with load file:

mvn install -Dload.file=./src/main/resources/FortressWebDemoUsers.xml


  • This step must be completed before tests can be successfully run.
  • The DelegatedAdminManagerLoad must also be loaded into LDAP, for base policy req's.

SECTION 5. Deploy to Tomcat Server

  1. If Tomcat has global security enabled you must add credentials to pom.xml:
      <!-- Warning the tomcat manager creds here are for deploying into a demo environment only. -->
  1. Load the Apache Fortress Realm Proxy jar to TOMCAT_HOME/lib/
wget http://repo.maven.apache.org/maven2/org/apache/directory/fortress/fortress-realm-proxy/[version]/fortress-realm-proxy-[version].jar -P $TOMCAT_HOME/lib

where TOMCAT_HOME matches your target env. where [version] matches a particular release of fortress, e.g. 3.0.0.

  1. Allow javax.swing in TOMCAT_home/bin/setenv.sh

Required for Tomcat 10

JAVA_OPTS="$JAVA_OPTS --add-opens=java.desktop/javax.swing.tree=ALL-UNNAMED"
  1. Restart Tomcat server.

  2. Enter maven command to deploy to Tomcat:

mvn tomcat:deploy
  1. To redeploy:
mvn tomcat:redeploy
  1. Open browser and test (creds: test/password):

where hostname is host or ip for your machine

SECTION 6. Test with Selenium

  1. Fortress Web uses WebDriverManager to manage the Selenium drivers.

  2. Run the Selenium Web driver integration tests with Firefox (default):

mvn test -Dtest=FortressWebSeleniumITCase
  1. Run the tests using Chrome:
mvn test -Dtest=FortressWebSeleniumITCase -Dweb.driver=chrome

Note: These automated tests require that:

  • Either Firefox or Chrome installed to target machine.
  • FORTRESS_CORE_HOME/FortressJUnitTest successfully run. This will load some test data to grind on.
  • FortressWebDemoUsers policy loaded into target LDAP server.

SECTION 7. Fortress Web properties

This section describes the properties needed to control fortress web.

  1. LDAP Hostname coordinates. The host name can be specified as a fully qualified domain name or IP address.
# Host name and port of LDAP DIT:
  1. LDAP Server type. Each LDAP server impl has different behavior on operations like password policies and audit. If using a 3rd type of server that isn't formally supported, leave blank or type is other.
# If ApacheDS server:
# Else if OpenLDAP server:
# Else leave blank:
  1. Set the credentials of service account. Must have read/write privileges over the Fortress LDAP DIT:
# If ApacheDS it will look something like this:
# Else If OpenLDAP it will look something like this:
  1. Define the number of LDAP connections to use in the pool This setting will be proportional to the number of concurrent users but won't be one-to-one. The number of required ldap connections will be much lower than concurrent users:
# This is min/max settings for LDAP connections.  For testing and low-volume instances this will work:
  1. Give coordinates to the Config node that contains all of the other Fortress properties. This will match your LDAP‘s server’s config node per Fortress Core setup.
# This node contains fortress properties stored on behalf of connecting LDAP clients:
  1. If using LDAPS.
# Used for SSL Connection to LDAP Server:
  1. To use REST instead of LDAP. Points to fortress-rest instance.
# This will override default LDAP manager implementations for the RESTful ones:
  1. If using REST, provide the credentials of user that has access to fortress-rest.
# Optional parameters needed when Fortress client is connecting with the En Masse (rather than LDAP) server:
  1. To reenable the nav panel on startup.
# The default is 'false':
  1. If using ApacheDS and setting password policies, point to the correction location.
# ApacheDS stores its password policies objects here by default:
  1. The fortress web runtime will cache user's permissions in their session if set to true.
# Used by application security components:
  1. Each instance of a fortress web can be scoped to one and only one tenant. The default tenant is called HOME.
# This is the default tenant or home context
# If you need to scope to a different tenant, supply its ID here: