Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note that reprovisioning has no way of knowing how to clear entries from the provisioning target that are not known to COmanage Registry. A typical pattern for reprovisioning all records would be to first clear out the target entirely (eg: delete all records from the LDAP server) and then executing execute Reprovision All.

Automatic Provisioning

...

  • Address (attached to CO Person Role)
  • CO Group Membership
  • CO Person Record
  • CO Person Role Record
  • Email Address (attached to CO Person)
  • Identifier (attached to CO Person)
  • Name (attached to CO Person)
  • TelephoneNumber (attached to CO Person Role)

(warning) Only Active or (where appropriate) Grace Period Which records are provisioned are determined by CO Person and Person Role Status.

Monitoring Push Provisioning

(warning) When provisioning is triggered automatically by an update, there is not currently a way to pass to the end user the results of the provisioning operation (other than manually clicking on the Provisioned Services link for the CO Person) (CO-582). If a provisioning plugin fails in such a situation, an error message will be syslog()d (at LOG_ERR). It is recommended that syslog be suitably configured and monitored to catch any errors with automatic provisioning.

Additionally, a Notification will be generated and sent to the CO Administrators.

...