• State Not Answered
  • Replies 5 replies
  • Subscribers 96 subscribers
  • Views 7706 views
  • Users 0 members are here
Options
Related

what is the best way to configure data warehouse, which is responsible for managing access information for more than one applications? Both Synchronization and (de)provisioning shall be performed on the data warehouse.

kavita.digari
over 6 years ago

I've a central repository(target system) for many of my applications which keeps user accounts, roles (along with application mapping) and user-role association. I want it to integrate within D1IM v7, so that, for all applications, data synchronization data and provisioning of roles is done using D1IM to a single target. Any suggestion what would be the best way to implement it in D1IM.

 

Parents
  • 0 over 6 years ago

    Hi,

    According to the documentation: "Base objects are are required for synchronizing all target systems that are connected to One Identity Manager by default." This suggests you usually need a unique base object for each target system. Conclusion: use UNSRootB as the base table, with the base object(s) being the custom target system(s) covered by the sync project.

    The only reason for caution is, this line in the documentation:  "You cannot normally specify a base object for synchronizing with database connectors and the CSV connector."

    Perhaps the developers mean you you can only do it if certain other objects have been created first. For example:

    1. a single Custom Target System Type for the specific SQL database in Manager (which creates the unique row in DPRNameSpace)
    2. a separate Custom Target System in Manager for each application in scope for the sync project (this creates unique rows in UNSRootB and you can link each one to the Custom Target System Type created in step 1)

Reply
  • 0 over 6 years ago

    Hi,

    According to the documentation: "Base objects are are required for synchronizing all target systems that are connected to One Identity Manager by default." This suggests you usually need a unique base object for each target system. Conclusion: use UNSRootB as the base table, with the base object(s) being the custom target system(s) covered by the sync project.

    The only reason for caution is, this line in the documentation:  "You cannot normally specify a base object for synchronizing with database connectors and the CSV connector."

    Perhaps the developers mean you you can only do it if certain other objects have been created first. For example:

    1. a single Custom Target System Type for the specific SQL database in Manager (which creates the unique row in DPRNameSpace)
    2. a separate Custom Target System in Manager for each application in scope for the sync project (this creates unique rows in UNSRootB and you can link each one to the Custom Target System Type created in step 1)

Children
No Data