User guide

Chapter 2: Environment Setup (SSO Administrators)
2-16
4. Check the checkbox of the created SSO repository and click the Start button to start the SSO
repository.
Registering User Information and Role Configuration in the SSO
Repository
Register user information and role configuration in the SSO repository with the user program. Refer to
Preparation for a User Program, for details about the user program.
User information can be imported from the database (source data) to the SSO repository using a
command. For details on importing user information using a command, see 'Importing User Information
From the Database to the SSO Repository'.
Refer to Role Configuration Entry and User Information Entry for details of the entry attributes of role
configuration and user information in Interstage Single Sign-on.
A CSV data file or LDIF file can also be used to register user information and role configuration in the
SSO repository.
Refer to Using a CSV Data File and Using an LDIF File for details.
Importing User Information From the Database to the SSO Repository
Use the ssoimportum command to import user information from the database (source data) to the SSO
repository. For details of the database that can be used, see 'Supported Software' - 'Software Products
Required for Application Execution' in the Product Notes.
Before user information is imported from the source data to the SSO repository, the SSO repository
must be created. For details on SSO repository creation methods, see 'Creating an SSO Repository'.
In this section, the table temporarily created in the database or the table is called a 'virtual table'.
To make the source data information public, create a virtual table. Enter the table name and column
name of the connected source data in the operation information file. Using this method, registered user
information can be extracted from this source data and registered in the SSO repository. Specify the
operation information file using the parameters of the ssoimportum command.
If information that you do not want to make public is included for security purposes you should use the
public user information to create a virtual table and make a connection to that table. In this way, user
information can be extracted without having to make an actual table public.