[Index]

Model: view/HcsAuditUserSyncToVIEW

Audit

Use this procedure to audit user data for SyncTo, User Type, LDAP and CUCM Audit, and Subscriber at the selected hierarchy node. The following checks and corrections are performed:

  1. Check for duplicate usernames. Warning messages are logged in User Management > Log Messages. For more information about duplicate usernames, see Managing Duplicate Usernames.
  2. Check SyncTo settings. If the SyncTo setting is incorrect and the user is not a duplicate, the SyncTo setting is updated.
  3. Check SSO User settings. If the SSO User setting is not correct based on the SyncTo setting and the user is not a duplicate, the SSO User is updated.
  4. Check User Type settings. If the User Type is incorrect, it will be updated.

Provisioning Status (CUCM, LDAP and SyncTo)

Use this procedure to identify if the right SyncTo value is set for a given user, and to identify scenarios where the user provisioning status has invalid values.

  1. Log in as a provider, reseller, or customer administrator.

  2. Choose Audit > Audit User Data.

  3. Choose a Hierarchy node.

    We recommended to run at Site hierarchy for a better performance.

  4. In the Provisioning Status (CUCM, LDAP and SyncTo) area, from the Options drop-down, choose either Off, Report Only or Report & Fix.

  5. Select the Log to Transactions Only check box to get audit data only in transaction logs not as Audit Report.

  6. Click Save.

User Type

Use this procedure to identify if the right user type is set for a given user and fix if required.

  1. Log in as a provider, reseller, or customer administrator.

  2. Choose Audit > Audit User Data.

  3. Choose a Hierarchy node.

    We recommended to run at Site hierarchy for a better performance.

  4. In the User Type area, from the Options drop-down, choose either Off, Report Only or Report & Fix.

  5. Select the Log to Transactions Only check box to get audit data only in transaction logs not as Audit Report.

  6. Click Save.

Subscriber

Use this procedure to get report to identify scenarios where the subscriber is found with no corresponding user.

  1. Log in as a provider, reseller, or customer administrator.

  2. Choose Audit > Audit User Data

  3. Choose a Hierarchy node.

    We recommended to run at Site hierarchy for a better performance.

  4. In the Subscriber area, from the Options drop-down, choose either Off, Report Only or Report & Fix.

  5. Select the Log to Transactions Only check box to get audit data only in transaction logs not as Audit Report.

  6. Click Save.

Audit Report

If you have not selected the Log to Transactions Only check box, then the Audit Report gets created per user basis if there is any discrepancy.

You can view the reports under Audit > Audit Report.

You can also export the report to .xls and .json format.

Choose Administration Tools > Transaction to view the transaction log. Click the Hcs Audit User Sync To View transaction to open it. For example, the message indicates:

Model Details: view/HcsAuditUserSyncToVIEW

Title Description Details
Tool Information Overview of Tool Default: {{ fn.localize data.HcsLocalizedStringDat.value | key: auditUser_tool_info }}
  • Field Name: info
  • Type: String
  • Default: {{ fn.localize data.HcsLocalizedStringDat.value | key: auditUser_tool_info }}
Hierarchy The name of the hierarchy node from which to start looking for users to audit.
  • Field Name: user_hn
  • Type: String
  • Choices: [" "]
Provisioning Status [CUCM, LDAP and SyncTo]
  • Field Name: provisioning_status
  • Type: Object
Options Default: Off
  • Field Name: provisioning_status.options
  • Type: String
  • Default: Off
  • Choices: ["Off", "Report Only", "Report & Fix"]
Log To Transactions Only Log to transactions only without creating report Default: false
  • Field Name: provisioning_status.log_transaction_only
  • Type: Boolean
  • Default: false
User Type
  • Field Name: user_type
  • Type: Object
Options Default: Off
  • Field Name: user_type.options
  • Type: String
  • Default: Off
  • Choices: ["Off", "Report Only", "Report & Fix"]
Log To Transactions Only Log to transactions only without creating report Default: false
  • Field Name: user_type.log_transaction_only
  • Type: Boolean
  • Default: false
Subscriber
  • Field Name: subscriber
  • Type: Object
Options Default: Off
  • Field Name: subscriber.options
  • Type: String
  • Default: Off
  • Choices: ["Off", "Report Only", "Report & Fix"]
Log To Transactions Only Log to transactions only without creating report Default: false
  • Field Name: subscriber.log_transaction_only
  • Type: Boolean
  • Default: false