Skip to content
Permalink
Browse files
more description on security model
  • Loading branch information
shawnmckinney committed Apr 25, 2019
1 parent c230743 commit 19ff1838a9a5034f44a8cac716660f5342830718
Showing 2 changed files with 2 additions and 2 deletions.
@@ -45,7 +45,7 @@ ________________________________________________________________________________

The system architecture of a typical Apache Fortress Rest deployment:

(*REST/JSON Client*)<--HTTP-->(*FortressREST*)<--in-process API call-->(*FortressCore*)<--LDAPv3-->(*DirectoryServer*)
(*REST/JSON Client*)<--https-->(*FortressREST*)<--in-process-->(*FortressCore*)<--ldaps-->(*DirectoryServer*)

* REST/JSON Client is any HTTP interface that supports the message formats.
* Fortress Rest is this project's main artifact, a web application archive (.war) file that deploys into servlet containers like Apache Tomcat.
@@ -255,7 +255,7 @@ ________________________________________________________________________________
These tests will use the Apache Fortress Core test programs to drive the Apache Fortress Rest services.
It works via fortress core's inherent ability to call itself over REST, useful for testing and hopping over firewalls.

(*FortressCore*)<--HTTP-->(*FortressREST*)<--in-process API call-->(*FortressCore*)<--LDAPv3-->(*DirectoryServer*)
(*FortressCore*)<--https-->(*FortressREST*)<--in-process-->(*FortressCore*)<--ldaps-->(*DirectoryServer*)

See *SECTION 1. Prerequisites* of this document for more info on how to prepare a test env.

0 comments on commit 19ff183

Please sign in to comment.