Skip to end of metadata
Go to start of metadata

Imports module can help to create automated imports from Active Directory/File source which will be executed periodically based on Quartz CRON expression.

Active Directory

  1. Navigate to "Automation → Imports".
  2. Click "ADD" button.
  3. Make sure that "Active directory" form is selected (after save this cannot be changed).
  4. Enter task name (must be unique).
  5. Select CRON expression from available list or enter custom expression. Read more at Quartz CRON documentation.

    SecondsMinutesHoursDay Of MonthMonthDay Of WeekYear
    *****?*
  6. Select "Start time", from which periodic import will be executed.
  7. Select primary key (First and Last name or Employee number). Primary keys must have unique values.
  8. Select Mode:

    ModeDescription
    OverwriteAdd new users and Overwrite existing user data at CredoID.  If user already exists, all user data is updated according to import source.
    AppendAdd new users and add data to existing user if existing user data fields was empty before import.
    SynchronizeSame as "Overwrite". User from CredoID are deleted if  doesn't exists at import source.
  9. Type "LDAP Path: - full path of Active directory (example: ldap://1.2.3.4:389/OU=users,DC=midpoint)

  10. Type LDAP group path -  full path of Active directory group. Users existing in this group will be assigned with access level, after binding groups to access level (example: ldap://1.2.3.4:389/OU=groups,DC=midpoint).
  11. Type Username - user name for LDAP login.
  12. Type Password - password for LDAP login.
  13. After entering all required data, click "BINDINGS" button.
  14. If connection to LDAP server is successful, "Import bindings" window will appear:
    • CredoID column - represents user field in CredoID.
    • Attribute - select binding field form Active Directory available user fields.*

      Requirements for Active Directory fields

      • All fields must be single valued except locations and identifications.
      • Activation/Expiration fields require to follow ISO 8601 date and time format.
      • Identifications fields must follow one of formats:
        1. as card/pin string: cardbits_facilitycode_cardnumber_pin (example: 26_10_12345_1234)
        2. as JSON string:
          {

              "CardNumber": "12345",

              "FacilityCode": "10",

              "VisibleNumber": "12345",

              "CardFormatBits": 26,

              "PinCode": "1234",

              "LicensePlate": "MDP23"

          }

  15. Click "Group binding".
  16. Select access level on the right column, which will be applied to available Active directory group from left column.
  • No labels
Write a comment...