Chatta subito con l'assistenza
Chat con il supporto

Active Roles 8.1.1 - Synchronization Service Administration Guide

Synchronization Service overview Deploying Synchronization Service Getting started Connections to external data systems
External data systems supported with built-in connectors
Working with Active Directory Working with an AD LDS (ADAM) instance Working with Skype for Business Server Working with Oracle Database Working with Oracle Database user accounts Working with Exchange Server Working with Active Roles Working with One Identity Manager Working with a delimited text file Working with Microsoft SQL Server Working with Micro Focus NetIQ Directory Working with Salesforce Working with ServiceNow Working with Oracle Unified Directory Working with an LDAP directory service Working with an OpenLDAP directory service Working with IBM DB2 Working with IBM AS/400 Working with IBM RACF Working with MySQL database Working with an OLE DB-compliant relational database Working with SharePoint Working with Microsoft 365 Working with Microsoft Azure Active Directory Configuring data synchronization with the SCIM Connector Configuring data synchronization with the Generic SCIM Connector Objects and operations supported by the SCIM Connector Example of using the Generic SCIM Connector for data synchronization
Using connectors installed remotely Creating a connection Renaming a connection Deleting a connection Modifying synchronization scope for a connection Using connection handlers Specifying password synchronization settings for a connection
Synchronizing identity data Mapping objects Automated password synchronization Synchronization history Scenarios of use Developing PowerShell scripts for attribute synchronization rules Using PowerShell script to transform passwords

Povisioning datasets

To synchronize the SQL table to IBM RACF follow the steps provided here.

To synchronize the SQL table to IBM RACF

  1. Navigate to the Workflows tab.

  2. Click Add sync workflow.

  3. Enter IBM RACF Datasets and click OK.

  4. Click IBM RACF Datasets workflow.

  5. Click Add synchronization step.

  6. Click Creation and then Next.

  7. From the Source connected system section and click Specify.

  8. Select your Microsoft SQL Server Connector and click Finish.

    The SQL source object type is currently set to sql-Object. Do not change this value.

  9. Click Next.

  10. In the Target connected system field, click Specify and then locate your IBM RACF connector and click Finish.
  11. The object type in the Target object system field is populated automatically by Synchronization Service to racfUser. Change this to racfDataset.

  12. Click Next.

  13. In the Specify provisioning rules section, click Forward Sync Rule.
  14. In the Source attribute field, click Attribute locate UID and click OK.
  15. In the Target attribute field, click Attribute, locate racfDataset and click OK.

  16. Repeat these steps so that the following five items are mapped:

    SQL Attribute

    IBM RACF Attribute

    Owner

    racfOwner

    UACC

    racfUacc

    Create_Group

    racfCreateGroup

    Audit

    racfAudit

    UID

    racfDataset

  17. Click OK.

  18. Click Finish to complete the synchronization.

Updating datasets

To synchronize the SQL table to IBM RACF

  1. Navigate to the Sync Workflows tab, select IBM RACF Datasets and click OK.

  2. Click Add synchronization step.

  3. Click Update and then click Next.

  4. From the Source connected system section and click Specify.

  5. Select your Microsoft SQL Server Connector and click Finish.

    The SQL source object type is currently set to sql-Object. Do not change this value.

  6. Click Next.

  7. In the Target connected system field, click Specify and then locate your IBM RACF connector and click Finish.
  8. The object type in the Target object system field is populated automatically by Synchronization Service to racfUser. Change this to racfDataset.

  9. Click Next.

  10. In the Specify provisioning rules section, click Forward Sync Rule.
  11. In the Source attribute field, click Attribute locate UID and click OK.
  12. In the Target attribute field, click Attribute, locate racfDataset and click OK.

  13. Repeat these steps so that the following five items are mapped:

    SQL Attribute

    IBM RACF Attribute

    Owner

    racfOwner

    UACC

    racfUacc

    Create_Group

    racfCreateGroup

    Audit

    racfAudit

    UID

    racfDataset

  14. Click OK.

  15. Click Finish to complete the synchronization.

Deprovisioning datasets

To deprovision datasets

  1. Navigate to the Workflows tab and select IBM RACF Datasets.

  2. Click Add synchronization step.

  3. Click Deprovision and then click Next.

  4. From the Source connected system section and click Specify.

  5. Select your Microsoft SQL Server Connector and click Finish.

  6. Select Source object is deleted or is out of synchronization scope option in the Deprovision target objects if section.

  7. Optionally, configure the Source object meets the following criteria.

  8. Click Next.

  9. In the Target connected system field, click Specify and then locate your IBM RACF connector and click Finish.

  10. The object type in the Target object system field is populated automatically by Synchronization Service to racfDataset.

  11. Click Next.

  12. Select Delete target object.

  13. Click Finish to complete the synchronization.

Working with TSO command

The IBM RACF connector can be used to run any command in the Time Sharing Option (TSO) environment on the target IBM mainframe. The LDAPX exit must be installed and configured for this functionality to be supported.

The TSO command is run using an Active Roles Synchronization Service synchronization step to create an object of type ldapxtsocmd on the target IBM RACF system and supplying the name of the TSO command or script to be run in the attribute racfprogrammername. When the step is run, the IBM RACF connector intercepts the create command and instead sends an LDAP search command with the required parameters via the LDAP protocol.

The LDAPX exit intercepts this request, extracts the TSO command information and runs the command. The LDAP response is constructed, containing the results obtained from running the command. The IBM RACF connector receives this LDAP response, extracts the results and saves them in a text file that can be examined later.

No object is created during the synchronization step so it can be run indefinitely, each time executing the TSO command stored in the racfprogrammername attribute from the same or any other synchronization step.

The following example shows a method of issuing a TSO command using synchronisation from Active Directory (AD).

  1. Using Active Directory Users and Computers, create a container in AD that can be filtered on by the ARSS. For example, create an organisational unit container called TSO Commands.

  2. Create a dummy computer object within this container with name TSOCMD and description field set to the string STATUS. The TSO command STATUS will return the current system status.

  3. Create a workflow called Run TSO Command.

  4. Within this workflow, create a synchronization step item as follows:

    1. Synchronization step type: Create

    2. Source object: Active Directory, specified container as created above, name starts with TSOCMD.

    3. Target connector: IBM RACF

    4. Object type: ldapxtsocmd

    5. Mapping: from AD Description attribute to IBM RACF racfprogrammername attribute

  5. Save the step.

  6. Run the synchronization step. There should be one item to be created with the following properties:

    • objecttype: ldapxtsocmd

    • racfprogrammername: STATUS

  7. Perform the synchronization step.

  8. The LDAP command will be sent and interpreted by the LDAPX exit to run the TSO command.

  9. Once complete, the synchronization step will show as being successful.

  10. The output from running the command can be found in the following text file:

    <ARSS installation folder>\SyncService\TSOCommandOutput\YYDDMM.txt, where, YYMMDD represents the date when the command was run.

  11. The text file will contain the output returned from IBM RACF having run the STATUS command.

  12. Multiple commands run on the same day will have their output appended to the same daily text file.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione