Chapter 3. Securing a sample application

Procedure

1. Download JBoss EAP 7.4 from the Red Hat customer portal.

2. Unzip the downloaded JBoss EAP.

   $ unzip <filename>.zip

   Copy to Clipboard Toggle word wrap
3. Change to the Red Hat Single Sign-On root directory.

4. Start the Red Hat Single Sign-On server by supplying a value for the jboss.socket.binding.port-offset system property. This value is added to the base value of every port opened by the Red Hat Single Sign-On server. In this example, 100 is the value.

   Linux/Unix

   $ cd bin
   $ ./standalone.sh -Djboss.socket.binding.port-offset=100

   Copy to Clipboard Toggle word wrap

   Windows

   > ...\bin\standalone.bat -Djboss.socket.binding.port-offset=100

   Copy to Clipboard Toggle word wrap

   Windows Powershell

   > ...\bin\standalone.bat -D"jboss.socket.binding.port-offset=100"

   Copy to Clipboard Toggle word wrap

5. Confirm that the Red Hat Single Sign-On server is running. Go to http://localhost:8180/auth/admin/ .

   If the admin console opens, you are ready to install a client adapter that enables JBoss EAP to work with Red Hat Single Sign-On.

Procedure

1. Download the Client Adapter for EAP 7 from the Red Hat customer portal.
2. Change to the root directory of JBoss EAP.

3. Unzip the downloaded client adapter in this directory. For example:

   $ unzip <filename>.zip

   Copy to Clipboard Toggle word wrap

4. Change to the bin directory.

   $ cd bin

   Copy to Clipboard Toggle word wrap

5. Run the appropriate script for your platform.

   Note

   If you receive a file not found, make sure that you used unzip in the previous step. This method of extraction installs the files in the right place.

   Linux/Unix

   $ ./jboss-cli.sh --file=adapter-elytron-install-offline.cli

   Copy to Clipboard Toggle word wrap

   Windows

   > jboss-cli.bat --file=adapter-elytron-install-offline.cli

   Copy to Clipboard Toggle word wrap

   Note

   This script makes the necessary edits to the …​/standalone/configuration/standalone.xml file.

6. Start the application server.

   Linux/Unix

   $ ./standalone.sh

   Copy to Clipboard Toggle word wrap

   Windows

   > ...\standalone.bat

   Copy to Clipboard Toggle word wrap

Procedure

1. Log in to the admin console with your admin account: http://localhost:8180/auth/admin/
2. In the top left drop-down list, select the Demo realm.

3. Click Clients in the left side menu to open the Clients page.

   Clients

   

4. On the right side, click Create.

5. On the Add Client dialog, create a client called vanilla by completing the fields as shown below:

   Add Client

   

6. Click Save.
7. On the Vanilla client page that appears, click the Installation tab.

8. Select Keycloak OIDC JSON to generate a file that you need in a later procedure.

   Keycloak.json file

   

9. Click Download to save Keycloak.json in a location that you can find later.

10. Select Keycloak OIDC JBoss Subsystem XML to generate an XML template.

    Template XML

    

11. Click Download to save a copy for use in the next procedure, which involves JBoss EAP configuration.

Procedure

1. Go to the standalone/configuration directory in your JBoss EAP root directory.

2. Open the standalone.xml file and search for the following text:

   <subsystem xmlns="urn:jboss:domain:keycloak:1.1"/>

   Copy to Clipboard Toggle word wrap

3. Change the XML entry from self-closing to using a pair of opening and closing tags as shown here:

   <subsystem xmlns="urn:jboss:domain:keycloak:1.1">
   </subsystem>

   Copy to Clipboard Toggle word wrap

4. Paste the contents of the XML template within the <subsystem> element, as shown in this example:

   <subsystem xmlns="urn:jboss:domain:keycloak:1.1">
     <secure-deployment name="WAR MODULE NAME.war">
       <realm>demo</realm>
       <auth-server-url>http://localhost:8180/auth</auth-server-url>
       <public-client>true</public-client>
       <ssl-required>EXTERNAL</ssl-required>
       <resource>vanilla</resource>
     </secure-deployment>
   </subsystem>

   Copy to Clipboard Toggle word wrap

5. Change WAR MODULE NAME.war to vanilla.war:

   <subsystem xmlns="urn:jboss:domain:keycloak:1.1">
     <secure-deployment name="vanilla.war">
     ...
   </subsystem>

   Copy to Clipboard Toggle word wrap
6. Reboot the application server.

Procedure

1. Make sure your JBoss EAP application server is started.

2. Download the code and change directories using the following commands.

   $ git clone https://github.com/redhat-developer/redhat-sso-quickstarts
   $ cd redhat-sso-quickstarts/app-profile-jee-vanilla/config

   Copy to Clipboard Toggle word wrap
3. Copy the keycloak.json file to the current directory.
4. Move one level up to the app-profile-jee-vanilla directory.

5. Install the code using the following command.

   $ mvn clean wildfly:deploy

   Copy to Clipboard Toggle word wrap

6. Confirm that the application installation succeeded. Go to http://localhost:8080/vanilla where a login page is displayed.

   Login page confirming success

   

7. Log in using the account that you created in the demo realm.

   Login page to demo realm

   

   A message appears indicating you have completed a successful use of Red Hat Single Sign-On to protect a sample JBoss EAP application. Congratulations!

   Complete success