Set up model security - Connect_CDC - aws_mainframe_modernization_service - connect_cdc_mimix_share - Latest

You may define one or more model user IDs, passwords, and roles to be stored with a particular model. If a model is secured, then only an Admin user can add, delete, or modify user ids, passwords and roles.

Additional roles may be defined if more security is necessary.

To set up the user IDs, passwords, and roles, select Properties from the context menu of the Data Movement Model. If the Enable model security check box is not checked, the grid is disabled.

If the Enable model security check box is checked, then at least one Admin ID is required.

Note: Ensure that you remember the assigned password as it will require a call to Precisely Support to recover it

The Enable XML hashcode check box is used to request that message digests (short representations of streams of bytes) be used to secure both the XML files (network and dataflow) in their entirety. This is optional.

If Secure Logging is selected (enabled) then messages in the Listener logs, Kernel logs, the Console logs and MonCon logs sensitive data. To enable this option you must select Enable model security. For detailed information refer to Secure logging.

If Secure Logging is disabled in the model then all users connected to that kernel could potentially view any source or target table customer data contained in messages sent to the log or the clients. The default value for Secure Logging is disabled. Refer to

Connect CDC MonCon and Connece CDC Console can implement the use of any model user IDs provided.

 Director actions by user type details the Director model security role actions by user type:

• Admin    

• User    

• Modeler

• Monitor