For the remainder of this document, $HOME refers to
the location where you unzipped your sample configuration files.
Download and unzip the sample configuration files. If you installed through quick start you already have the configuration files downloaded and installed.
Copy WordPressProxyOnly.json to
$HOME/.ForgeRock/OpenIG/config.json. By default, OpenIG
looks for $HOME/.ForgeRock/OpenIG/config.json for its
configuration. You must restart the OpenIG container when making any change
to the configuration file.
$ cp $HOME/forgerock-sample-configs/WordPressProxyOnly.json $HOME/.ForgeRock/OpenIG/config.json $ jetty.sh restart
To try out the first sample browse to http://demo.forgerock.com:8080/wordpress. You should see the WordPress
Portal home page. If you click on the login link you should be prompted to
login to the application as if you were accessing it directly. To verify you
are actually going through OpenIG, stop the OpenIG container, refresh your
browser and try to access the application again. If you still see the
application, make sure your DNS or host files are configured to point to
OpenIG instead of the Portal. You can login to the Portal with user name
george and password costanza. The next
section shows how to configure OpenIG to intercept the login page and
automatically log you in when it sees that you have clicked the login
link.
To see what is happening behind the scenes, take a look at
$HOME/.ForgeRock/OpenIG/config.json. Look for the
HandlerServlet. This is the servlet entry point to OpenIG. The HandlerServlet
passes the request off to another handler which may be a chain of filters
and handlers. In the pure proxy case there is no special logic to execute so
it hands off to the ClientHandler. The job of the ClientHandler is to send
the request on to the target. Since there are no chains called before the
ClientHandler, the request passes through to the target untouched.
