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
http://www.apache.org/licenses/LICENSE-2.0
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 Realm
Version 3.0.1
Table of Contents
Document Overview
About Apache Fortress Realm
Tips for first-time users
SECTION 1. Prerequisites
SECTION 2. Download & Install
SECTION 3. Instructions for Application Usage
Document Overview
This document contains instructions to download and install the Apache Fortress Realm. SECTION 3 contains steps to get it working with Apache Tomcat.
About Apache Fortress Realm
Role-Based Access Control security provider to Apache Tomcat.
Uses Apache Tomcat Realm Interface
Declarative controls for authentication & coarse-grained authorization (role check)
Tips for first-time users
To use with ApacheDS: README-QUICKSTART-APACHEDS.md in FORTRESS_CORE_HOME package
To use OpenLDAP: README-QUICKSTART-SLAPD.md in FORTRESS_CORE_HOME package.
There are two options for web app usage of the fortress realm:
Option 1 requires web apps to be dependent on the fortress realm libs but enables usage of the fortress RBAC programmatic authZ apis.
It allows multiple realms, each of a different type and version, to be enabled within a single Tomcat instance.
Option 2 frees the web app from entanglement with fortress libs, which is easier to manage, but doesn’t allow fortress api usage. It limits to a single realm instance,
enabled globally, which might not agree with multitenant requirements.
Table of Options
Realm Type
Is Global Security?
Is Declarative?
Is RBAC APIs?
Multiple Realms Supported?
Fortress Dependencies?
Option 1
No
Yes
Yes
Yes
Yes
Option 2
Yes
Yes
No
No
No
Option 1. For Single Web Context
enable Java EE security for a single web app running under Tomcat
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 Realm
Table of Contents
Document Overview
This document contains instructions to download and install the Apache Fortress Realm. SECTION 3 contains steps to get it working with Apache Tomcat.
About Apache Fortress Realm
Role-Based Access Control security provider to Apache Tomcat.
Uses Apache Tomcat Realm Interface
Declarative controls for authentication & coarse-grained authorization (role check)
Tips for first-time users
SECTION 1. Prerequisites
Minimum software requirements (to build):
SECTION 2. Download & Install
a. from git:
b. or download package:
SECTION 3. Instructions for Application Usage
There are two options for web app usage of the fortress realm:
Option 1 requires web apps to be dependent on the fortress realm libs but enables usage of the fortress RBAC programmatic authZ apis. It allows multiple realms, each of a different type and version, to be enabled within a single Tomcat instance.
Option 2 frees the web app from entanglement with fortress libs, which is easier to manage, but doesn’t allow fortress api usage. It limits to a single realm instance, enabled globally, which might not agree with multitenant requirements.
Table of Options
Option 1. For Single Web Context
enable Java EE security for a single web app running under Tomcat
Option 2. For Global Security
enable Java EE security for all web apps running under Tomcat
END OF README