| commit | 033a4c8c9d706b6ac5145abee3781fa7dd277e3e | [log] [tgz] |
|---|---|---|
| author | Shawn McKinney <smckinney@apache.org> | Mon Nov 05 04:28:13 2018 -0600 |
| committer | Shawn McKinney <smckinney@apache.org> | Mon Nov 05 04:28:13 2018 -0600 |
| tree | 7ea04058c77384266ad544748daf2ec8c20f6c48 | |
| parent | b6f423e8c79227a7a0f7d68eb42917cdd0c7909d [diff] |
+ note on loading delegated admin policy
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.
This document contains instructions to download, build, and test operations using Apache Fortress Web component.
Minimum hardware requirements:
Minimum software requirements:
Everything else covered in steps that follow. Tested on Debian, Centos & Windows systems.
Build the source.
a. from git:
git clone --branch 2.0.2 https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git cd directory-fortress-commander mvn clean install
b. or download package:
wget http://www.apache.org/dist/directory/fortress/dist/2.0.2/fortress-web-2.0.2-source-release.zip unzip fortress-web-2.0.2-source-release.zip cd fortress-web-2.0.2 mvn clean install
These contain the coordinates to the target LDAP server.
cp $FORTRESS_CORE_HOME/config/fortress.properties $FORTRESS_WEB_HOME/src/main/resources
# This param tells fortress what type of ldap server in use: ldap.server.type=apacheds # ldap host name host=localhost # if ApacheDS is listening on port=10389 # If ApacheDS, these credentials are used for read/write to fortress DIT admin.user=uid=admin,ou=system admin.pw=secret # This is min/max settings for admin pool connections: min.admin.conn=1 max.admin.conn=10 # This node contains more fortress properties stored on behalf of connecting LDAP clients: config.realm=DEFAULT config.root=ou=Config,dc=example,dc=com # Used by application security components: perms.cached=true # Fortress uses a cache: ehcache.config.file=ehcache.xml # Default for pool reconnect flag is false: enable.pool.reconnect=true
Run maven install with load file:
mvn install -Dload.file=./src/main/resources/FortressWebDemoUsers.xml
Notes:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>tomcat-maven-plugin</artifactId>
<version>${version.tomcat.maven.plugin}</version>
<configuration>
...
<!-- Warning the tomcat manager creds here are for deploying into a demo environment only. -->
<username>tcmanager</username>
<password>m@nager123</password>
</configuration>
</plugin>
cp $FORTRESS_REALM_HOME/proxy/target/fortress-realm-proxy-[version].jar $TOMCAT_HOME/lib
Restart Tomcat server.
Enter maven command to deploy to Tomcat:
mvn tomcat:deploy
mvn tomcat:redeploy
http://hostname:8080/fortress-web
where hostname is host or ip for your machine
There version of Webdriver being used for Selenium now requires downloading and installing the gecko (firefox) and/or chrome drivers as separate binary packages. For more info: https://github.com/bonigarcia/webdrivermanager
Once that download has been completed, you will need to set the location of the driver as a system.property. For example, these lines may need to be added to the FortressWebSeleniumITCase test class, or set via other means:
@BeforeClass
public static void setupClass()
{
System.setProperty("webdriver.gecko.driver", "/home/user/drivers/geckodriver");
System.setProperty( "webdriver.chrome.driver", "/home/user/drivers/chromedriver");
...
}
mvn test -Dtest=FortressWebSeleniumITCase
mvn test -Dtest=FortressWebSeleniumITCase -Dweb.driver=chrome
Note: These automated tests require that:
This section describes the properties needed to control fortress web.
# Host name and port of LDAP DIT: host=localhost port=10389
# If ApacheDS server: ldap.server.type=apacheds
# Else if OpenLDAP server: ldap.server.type=slapd
# Else leave blank: #ldap.server.type=other
# If ApacheDS it will look something like this: admin.user=uid=admin,ou=system admin.pw=secret
# Else If OpenLDAP it will look something like this: admin.user=cn=Manager,dc=example,dc=com
# This is min/max settings for LDAP connections. For testing and low-volume instances this will work: min.admin.conn=1 max.admin.conn=10
# This node contains fortress properties stored on behalf of connecting LDAP clients: config.realm=DEFAULT config.root=ou=Config,dc=example,dc=com
# Used for SSL Connection to LDAP Server: enable.ldap.ssl=true enable.ldap.ssl.debug=true trust.store=/fully/qualified/path/and/file/name/to/java/truststore trust.store.password=changeit trust.store.set.prop=true
# This will override default LDAP manager implementations for the RESTful ones: enable.mgr.impl.rest=true
# Optional parameters needed when Fortress client is connecting with the En Masse (rather than LDAP) server: http.user=demouser4 http.pw=gX9JbCTxJW5RiH+otQEX0Ja0RIAoPBQf http.host=localhost http.port=8080
# The default is 'false': enable.nav.panel=true
# ApacheDS stores its password policies objects here by default: apacheds.pwpolicy.root=ou=passwordPolicies,ads-interceptorId=authenticationInterceptor,ou=interceptors,ads-directoryServiceId=default,ou=config
# Used by application security components: perms.cached=true
# This is the default tenant or home context contextId=HOME
# If you need to scope to a different tenant, supply its ID here: contextId=mytenantid