ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Siebel Connector: Which are the Siebel fields that can be fully administered by CA Identity Manager Provisioning?

book

Article ID: 53527

calendar_today

Updated On:

Products

DIRECTORY CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On SINGLE SIGN ON - LEGACY CA Data Protection (DataMinder) CA User Activity Reporting

Issue/Introduction

Description:

This document describes which Siebel fields can be administered by CA Identity Manager Provisioning.

Solution:

All single-valued fields that belong to user accounts, positions, divisions and responsibilities can be administered by the Siebel connector. The desired fields to be administered would first need to be mapped to an ETA attribute, and this is done through one of the 'Mapping Table' tabs for the Object type that the field belongs to.Multi-valued fields are not supported.

An administrator can choose to map:

  • up to 20 fields in Siebel user account to user account's attributes.

  • up to 10 fields in Siebel position, responsibility, organization, view and internal division to corresponding Siebel object's attributes. These attributes will, of course, be read-only for organizations and views.

An administrator can explore, create, modify, rename and delete Siebel user accounts, positions, divisions and responsibilities.

An administrator can only explore organizations, views and lists of values.

Note: Only user accounts which have "User ID" field are supported in SBL Connector. Thus it will not be possible to manage Siebel user accounts of "Person" type and other customized accounts without a "User ID". This is not a major problem because these accounts cannot be used to login into Siebel, thus it does not make sense to provision them.

Environment

Release:
Component: ETRADM