Follow these steps to specify a database different from the default database for the
Genero SAML implementation.
The implementation of Genero SAML Single sign-on (SSO) requires a database, to store SAML data
related to the protocol. By default, the database engine is SQLite and the database file is
$FGLDIR/web_utilities/services/saml/bin/saml.db.
-
Create a new or use an existing database, essentially on a dedicated machine. If several JGAS servers are configured for load balancing. There must be a unique database, to centralize
all SAML authentication data.
-
In the file DBase.4gl, modify the functions
BDConnect()
and DBDisconnect()
to handle and customize the database connection. Recompile the
DBase.4gl source.
DBase.4gl is found in
$FGLDIR/web_utilities/services/saml/src.
-
Modify the fglprofile file in $FGLDIR/web_utilities/services/saml/res to
include the connection information for the database.
-
Create SAML tables with the CreateDatabase.4gl program. Define the
database permissions required to allow the JGAS modification of SAML tables in the new
database.
CreateDatabase.4gl is found in
$FGLDIR/web_utilities/services/saml/src.
-
If needed, define the PATH (Windows®) or LD_LIBRARY_PATH (Linux®/UNIX™) environment variables in
$FGLDIR/web_utilities/services/SAMLServiceProvider.xcf with
ENVIRONMENT_VARIABLE
elements, in order to find the database client libraries
required by Genero SAML 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 SAML implementation.