LDAP Sync

Select the subsystem the profile belongs to

Type the name of the profile

Type the external key of the profile. This can be used as the id when you start the synchronization

Select the LDAP-profile which manages access to the LDAP-server to use. To the right, the connection status will be shown. It the profile is a valid one, the message "The ldap-profile is valid"

Select this check box to map synchronize all groups automatically.

Enter the number of days you want to keep log entries for. Use 0 if you not want an automatic purge of old log entries.

Specify the language that will be set on the user when its created.

This is the last known change number from the LDAP server. All updates will start after this change number.
The LDAP sync engine will automatically update this number after each run, to avoid
having to redo many updates. It will also update the last successful run time.

If required, you can type a change number yourself, to redo changes or to skip corrupt entries.

Mandatory values for creation of person or organization card

Select the top dimension for user dimensions. Dimensions with an external key are available in the drop down box.
By default, the objects that are retrieved from the remote directory are organized in a dimension structure in iKnowBase.
Dimensions representing the synchronized user objects will be placed under this top dimension.

Select the top dimension for organization dimensions. Dimensions with an external key are available in the drop down box.

You can configure the user synchronization to create organization information based on information in user objects.
Dimensions for the synchronized organization information will be placed under this top dimension.

Click the appropriate dimension type.

In iKnowBase, a dimension can be associated with a dimension type. This type segments the dimensions in iKnowBase.
Dimensions representing users will be associated with the dimension type given in this field.

Click the appropriate dimension type.

In iKnowBase, a dimension can be associated with a dimension type. This type segments the dimensions in iKnowBase.
Dimensions representing organizations will be associated with the dimension type given in this field.

Select the access control list to be used for the person and organization cards that are created when synchronizing user objects.

Select the group to be used as the default group for synchronized users.

When a user is created in iKnowBase, it is provided with a default group.
The value of this property is the name of the default group.

The default value is IKB_XNET_USERS.

Select the information type to be used for person cards.

When a user is synchronized, iKnowBase creates a person card for this user that has some standard attributes. This person card is a placeholder for the attributes and dimensions that a developer chooses to transfer from the external user directory to iKnowBase. The value of this property is the information type that will be used for these is the external key of this document type.

Click the appropriate information type.

You can create an organization card that is a placeholder for the information that the developer chooses to synchronize from the remote user directory as organizational information.
This field provides an external key that represents an information type given to this document.

By running a bootstrap, all users in the LDAP that correspond to the profile will be synchronized to iKnowBase.The job will be runned as a background job. Be aware it will take some time and it should only be used when you want all users synchronized to iKnowBase. Normally, the changelog synchronization is a preferred way of getting data into iKnowBase. This function is only available if the LDAP profile is valid.

By running a changelog synchronize, all changes since last time the synchronization was runned will be synchronized to iKnowBase. In production, this will normally be runned as a scheduled job.
The command you can use to add it as a schedule is :
begin oid_sync.synchronize_users (p_sync_id => ‘id’,p_execution_user => ‘adminuser’);end;. This function is only available if the LDAP profile is valid.

By running a single instance, only the entered user will be synchronized, You need to enter a valid DN-string. This function is only available if the LDAP profile is valid.

The name of the LDAP-attribute that identifies the username (login name).

The name of the LDAP-attribute that identifies the user�s e-mail address.

The name of the LDAP-attribute that identifies the user�s display name.

Check this flag if you want the LDAP Sync engine to create Oracle Portal groups corresponding to the synchronized organizations.

Check this flag if you want the LDAP Sync engine to create organization cards and dimensions corresponding to the organization information on the user object in LDAP.

The name of the LDAP-attribute that will be the external key of the organization card. Required when creating organization cards.

The name of the LDAP-attribute that identifies the name of the organization.

The name of the LDAP-attribute that identifies the code of the organization.

Type the name of the function that should be called before the synchronization takes place in iKnowBase.

Type the name of the function that should be called after the synchronization has taken place in iKnowBase, ie after the users, dimensions, organization and person cards has been created.

Type the name of the LDAP attribute of the LDAP object (user or group) to be synchronized from the LDAP to iKnowBase.

Select the iKnowBase attribute for the target information object.

The select list will only be populated by iKnowBase attributes tagged with an external key. The iKnowBase attribute selected will be the attribute that the LDAP value is synchronized to.

Select the type of the target attribute to create during synchronization.

There are four available choices:

• Text
• Dimension
• Digit
• Date

For all these types, except dimension, the LDAP Sync engine will assign the value from the LDAP attribute to the iKnowBase attribute. If you select the dimension type, the value of the LDAP attribute will be treated as an external key for a dimension, and the corresponding dimension will be assigned to the iKnowBase attribute.

Select the appropriate object type of this entry.

Select Person if the attribute should be synchronized to the person card. Select Organization if the attribute should be synchronized to the organization card.

Select the LDAP group to be synchronized from the LDAP to iKnowBase.

Existing groups in the LDAP specified by the Select LDAP-profile property on the Configuration tab are available in the dropdown boxes.

Select the iKnowBase group which the given LDAP group will be synchronized to.

Displays when the log info was created

Displays the id in the log table

Displays the severity of the message. INFO, DEBUG and ERROR are the valid values.

Displays normally the key (DN) handled in the operation

Displays a status/error message for each line

Displays trace info (only available when running i debug mode)