Logging In With Credentials From a Database

Before you start, prepare IG and the sample application as described in Getting Started Guide.

1. On your system, add the following data in a comma-separated value file called /tmp/userfile (on Windows, C:\Temp\userfile):

   username,password,fullname,email
   george,C0stanza,George Costanza,george@example.com
   kramer,N3wman12,Kramer,kramer@example.com
   bjensen,H1falutin,Babs Jensen,bjensen@example.com
   demo,Ch4ng31t,Demo User,demo@example.com
   kvaughan,B5ibery12,Kirsten Vaughan,kvaughan@example.com
   scarter,S9rain12,Sam Carter,scarter@example.com

2. Download and unpack the H2 database, and then start H2:

   $ sh /path/to/h2/bin/h2.sh

   H2 starts, listening on port 8082, and opens the H2 Console in a browser.

3. In the H2 Console, select the following options, and then select Connect to access the console:

   • Saved Settings: Generic H2 (Server)

     This option sets the Driver Class, org.h2.Driver, the JDBC URL, jdbc:h2:tcp://localhost/~/test, and the User Name, sa.

   • Password: password

4. In the console, add the following text, and then run it to create the user table:

   DROP TABLE IF EXISTS USERS;
   CREATE TABLE USERS AS SELECT * FROM CSVREAD('/tmp/userfile');

5. In the console, add the following text, and then run it to verify that the table contains the same users as the file:

   SELECT * FROM users;

6. Add the .jar file /path/to/h2/bin/h2-*.jar to the IG configuration:

   • For IG in standalone mode, create the directory $HOME/.openig/extra, where $HOME/.openig is the instance directory: and add .jar files to the directory.

   • For IG in web container mode, add .jar files to the web container classpath. For example, in Jetty use /path/to/jetty/webapps/ROOT/WEB-INF/lib.

1. Set an environment variable for the database password, and then restart IG:

   $ export DATABASE_PASSWORD='cGFzc3dvcmQ='

   The password is retrieved by a SystemAndEnvSecretStore, and must be base64-encoded.

2. Add the following route to IG, to serve .css and other static resources for the sample application:

   $HOME/.openig/config/routes/static-resources.json

   %appdata%\OpenIG\config\routes\static-resources.json

   {
     "name" : "sampleapp_resources",
     "baseURI" : "http://app.example.com:8081",
     "condition": "${matches(request.uri.path,'^/css')}",
     "handler": "ReverseProxyHandler"
   }

3. In IG, add the following route as $HOME/.openig/config/routes/03-sql.json (on Windows, $HOME/.openig/config/routes/03-sql.json):

   {
     "heap": [
       {
         "name": "SystemAndEnvSecretStore-1",
         "type": "SystemAndEnvSecretStore"
       },
       {
         "name": "JdbcDataSource-1",
         "type": "JdbcDataSource",
         "config": {
           "driverClassName": "org.h2.Driver",
           "jdbcUrl": "jdbc:h2:tcp://localhost/~/test",
           "username": "sa",
           "passwordSecretId": "database.password",
           "secretsProvider": "SystemAndEnvSecretStore-1"
         }
       }
     ],
     "name": "sql",
     "condition": "${matches(request.uri.path, '^/profile')}",
     "handler": {
       "type": "Chain",
       "baseURI": "http://app.example.com:8081",
       "config": {
         "filters": [
           {
             "type": "PasswordReplayFilter",
             "config": {
               "loginPage": "${matches(request.uri.path, '^/profile/george') and (request.method == 'GET')}",
               "credentials": {
                 "type": "SqlAttributesFilter",
                 "config": {
                   "dataSource": "JdbcDataSource-1",
                   "preparedStatement":
                   "SELECT username, password FROM users WHERE email = ?;",
                   "parameters": [
                     "george@example.com"
                   ],
                   "target": "${attributes.sql}"
                 }
               },
               "request": {
                 "method": "POST",
                 "uri": "http://app.example.com:8081/login",
                 "form": {
                   "username": [
                     "${attributes.sql.USERNAME}"
                   ],
                   "password": [
                     "${attributes.sql.PASSWORD}"
                   ]
                 }
               }
             }
           }
         ],
         "handler": "ReverseProxyHandler"
       }
     }
   }
   

   Notice the following features of the route:

   • The route matches requests to /profile.

   • The PasswordReplayFilter specifies a loginPage page property:

     • When a request is an HTTP GET, and the request URI path is /profile/george, the expression resolves to true. The request is directed to a login page.

       The SqlAttributesFilter specifies the data source to access, a prepared statement to look up the user's record, a parameter to pass into the statement, and where to store the search results in the request context attributes map.

       The request object retrieves the username and password from the context, and replaces the browser's original HTTP GET request with an HTTP POST login request, containing the credentials to authenticate.

       The request is for username, password, but H2 returns the fields as USERNAME and PASSWORD. The configuration reflects this difference.

     • For other requests, the expression resolves to false. The request passes to the ReverseProxyHandler, which directs it to the profile page of the sample app.

1. Go to http://openig.example.com:8080/profile.

   Because the property loginPage resolves to false, the PasswordReplayFilter passes the request directly to the ReverseProxyHandler. The sample app returns the login page.

2. Go to http://openig.example.com:8080/profile/george.

   Because the property loginPage resolves to true, the PasswordReplayFilter processes the request to obtain the login credentials. The sample app returns the profile page for George.