Specify a database to store OpenID data

Follow these steps to specify a database different from the default for the Genero OpenID implementation.

The implementation of Genero OpenID Single sign-on (SSO) requires a database to store OpenID data related to the protocol. By default, the database engine is SQLite and the database file is $FGLDIR/web_utilities/services/openid/bin/openid.db. This database is fully functional after installing the Genero Application Server.

  1. Create a new or use a existing database, eventually on a dedicated machine, if several GAS servers are configured for load balancing. There must be a unique database, to centralize all OpenID authentication data.
  2. In the file server.4gl, modify the functions BDConnect() and DBDisconnect() to handle and customize the database connection. Recompile the server.4gl source. server.4gl is found in $FGLDIR/web_utilities/services/openid/src
  3. Modify the FGLPROFILE file in $FGLDIR/web_utilities/services/openid/res to include the connection information for the database.
  4. Create OpenID tables with the CreateDatabase.4gl program. Define the database permissions required to let the Genero Application Server modification the OpenID tables in the new database. CreateDatabase.4gl is found in $FGLDIR/web_utilities/services/openid/src
  5. If needed, define the PATH (Windows®) or LD_LIBRARY_PATH (Linux®/UNIX™) environment variables in $FGLDIR/web_utilities/services/OpenIDServiceProvider.xcf with ENVIRONMENT_VARIABLE elements, in order to find the database client libraries required by Genero OpenID service.
    Note: If you use SQLite (by default), you do not need to add the path to the library since it is integrated in the ODI driver on most systems.
The alternate database is now used for the Genero OpenID implementation.