Feature/152 (#162)

* Synching develop branch with master. (#161)

* Feature/157 (#158)

* Initial creation of terraform setup for AWS static-content site hosting.

* Website deployment run locally works. Terraform AWS resource build run locally works.

* Creating test self-hosted environment. Alwways run terraform in docker containers.

* Removing all run on PR creation / modification.

* Making redirect_uri and logout URL field defaults parameterized.

* OIDC Authorization Code Flow with local keycoak is now working for test and prod hosted static-content site.

* Updating Token History grouping.

* Test suite works against test and prod sites with a local keycloak instance. The introspection endpoint in keycloak  cannot be invoked from the browser. So, the static content site cannot call the keycloak instrospection site. The test suite looks for hte expected CORS error. Test suite must be run against a local build for full validation.

* Feature/158 (#160)

* Initial creation of terraform setup for AWS static-content site hosting.

* Website deployment run locally works. Terraform AWS resource build run locally works.

* Creating test self-hosted environment. Alwways run terraform in docker containers.

* Removing all run on PR creation / modification.

* Making redirect_uri and logout URL field defaults parameterized.

* OIDC Authorization Code Flow with local keycoak is now working for test and prod hosted static-content site.

* Updating Token History grouping.

* Test suite works against test and prod sites with a local keycloak instance. The introspection endpoint in keycloak  cannot be invoked from the browser. So, the static content site cannot call the keycloak instrospection site. The test suite looks for hte expected CORS error. Test suite must be run against a local build for full validation.

* Minimize javascript for static content sites. Google analytics for static content sites.

* Updated docker build instructions.

Author: rcbjBlueMars

README.md

@@ -82,7 +82,7 @@ Note, that all configuration values except for the user password is written to l
 The debugger has been tested with recent versions of Chrome.
 
 ## Getting Started
-If you have docker installed already:
+If you have docker / docker-compose installed already:
 ```
 git clone https://github.com/rcbj/oauth2-oidc-debugger.git
 cd oauth2-oidc-debugger
@@ -93,7 +93,7 @@ Note, you will need at least 950MB of disk space ree in order to build this Dock
 
 From a bash command prompt on Fedora or RHEL 7.x, run the following::
 ```
-yum install git
+dnf install git # Or, yum install git
 git clone https://github.com/rcbj/oauth2-oidc-debugger.git
 dnf install docker
 systemctl start docker
@@ -172,8 +172,10 @@ To run this project you will need to install docker.
  yum install docker
  system start docker
  cd oauth2-oidc-debugger/client
- docker build -t oauth2-oidc-debugger .
- docker run -p 3000:3000 oauth2-oidc-debugger 
+ sudo docker build -t rcbj/debugger-client --build-arg CONFIG_FILE=./env/local.js -f client/Dockerfile .
+ sudo docker run -p 3000:3000 -e CONFIG_FILE=./env/local.js -d rcbj/debugger-client
+ sudo docker build -t rcbj/debugger-api --build-arg CONFIG_FILE=./env/local.js -f api/Dockerfile .
+ sudo docker run -p 4000:4000 -e CONFIG_FILE=./env/local.js -d rcbj/debugger-api
 ```
 On other systems, the commands needed to start the debugger in a local docker container will be similar. The docker Sinatra/Ruby runtime will have to be able to establish connections to remote IdP endpoint (whether locally in other docker containers, on the host VM, or over the network/internet).  On the test system, it was necessary to add "--net=host" to the "docker run" args. The network connectivity details for docker may vary from platform-to-platform.