Creating the data repository

Create two database tables, TP_MASTER and TP_MAPPING, to hold user mappings. Any schema can be used to create the tables.

About this task

The following example SQL scripts are provided in the scripts directory in the idp-server.war file.

  • DatabaseScript_DB2.sql
  • DatabaseScript_Oracle.sql
  • DatabaseScript_SQL.sql

The following tables describe the fields in the database tables that the scripts create.

Table 1. Fields in the TP_MASTER table
Field Description
TP_ID Primary key. The unique ID for a registered Service Provider.
TP_NAME The Service Provider name.
TP_INFO A description of the Service Provider.
KEY_ALIAS Unique key. The alias name of the Service Provider keystore.

Enforces a unique alias name. You can drop the UNIQUE constraint if you want to use the same keystore alias for multiple Service Providers.
Table 2. Fields in the TP_MAPPING table
Field Description
TP_CLIENT_ID Foreign key. The TP_ID of the requesting Service Provider.

Part of a composite primary key comprised of four columns to ensure that there is no duplicate mapping in this table.
TP_FOR_USER_ID The ID of the user making the request from the requesting Service Provider.

Part of a composite primary key comprised of four columns to ensure that there is no duplicate mapping in this table.

Must be a minimum of 4 characters and up to 24 characters long, and contain only alphanumerics, hyphen and underscore: [a-zA-Z0-9_-]
TP_SP_ID Foreign key. The TP_ID of the serving Service Provider.

Part of a composite primary key comprised of four columns to ensure that there is no duplicate mapping in this table.

Must be a minimum of 4 characters and up to 24 characters long, and contain only alphanumerics, hyphen and underscore: [a-zA-Z0-9_-]
TP_MAPPED_USER_ID The ID of the user in the serving Service Provider.

Part of a composite primary key comprised of four columns to ensure that there is no duplicate mapping in this table.
SAML_TOKEN Unique key. ID of the SAML token.

Enforces unique token generation. You can drop the UNIQUE constraint if you want to use the same token for multiple Service Providers.
LAST_REQUEST Timestamp of the last successful request.