op5-ldap-helper.conf

---
authyml_connection_name: ldapserver
contactgroup_prefix: LDAP
ldap:
  # in case you want to set these differently from what your LDAP config within op5
  # monitor is, you can set the group base DN, the group filter and the group search
  # scope here. This might be useful in cases where your LDAP directory contains
  # a huge amount of groups that makes the script crash when trying to iterate over
  # all of them
  custom_group_base_dn: false
  custom_group_filter: false
  custom_group_search_scope: false

  # if you want to synchronize the "pager" field for newly generated contact objects
  # with an LDAP value of the user, you have to configure the corresponding LDAP property
  # here. In case of an AD, this is "telephoneNumber"
  user_key_phone: false

  # In some cases you might want to not only synchronize USER objects from LDAP into
  # your op5 Monitor, but also CONTACTs. These may contain only an email address and/or
  # a telephone number, but they are no real users. If you are also adding LDAP contact
  # objects to your LDAP groups, you have to set both the contact_base_dn and the
  # contact_filter options to anything else than "false". You can start by setting
  # contact_base_dn: <the same as the USER dn in auth.yml>
  # contact_filter: (objectType=contact)
  contact_base_dn: false
  contact_filter: (objectType=contact)

  # For contact synchronization and in case you have memberkey_is_dn set to OFF, you
  # need to provide an LDAP field that can be used to filter for the short name of
  # the LDAP contact object. Could be "cn"
  contact_key: false

  # The contact_key_name should be a unique name of the contact object in the LDAP
  # directory. This is used to generate the name of the op5 Monitor contact object.
  # For AD this should be fine with "cn"
  contact_key_name: cn

  # this is the field where to find the email address in the LDAP contact object
  contact_key_email: mail

  # this is the fiels where to find the telephoneNumber in the LDAP contact object
  contact_key_phone: telephoneNumber

op5api:
  user: monitor$Default
  password: monitor
  authentication_realm: op5 Monitor API Access
  server: localhost
  ssl_verify_hostname: false

notify_service_check:
  notify_service_check: false
  host_object_name: monitor
  service_check_description: LDAP users sync

contact_notifications_settings:
  host_notifications_enabled: false
  service_notifications_enabled: false
  host_notification_commands: host-notify
  service_notification_commands: service-notify
  host_notification_options: d,r
  service_notification_options: c,w,r
  host_notification_period: 24x7
  service_notification_period: 24x7

contact_settings_per_group:
  # here you can add settings that will be used to create the newly generated
  # contact objects in op5 Monitor based on the LDAP group name. This way, you can
  # define settings that should be different per LDAP group, such as notification
  # time periods and such. Just add one "section" per LDAP group that you want
  # custom settings for. LDAP group names which does not exist in LDAP will be
  # ignored. Settings set here override general settings under the contact_notification_settings
  # section.
  Test Group (Name in LDAP):
    host_notifications_enabled: false
    service_notifications_enabled: true
    host_notification_commands: host-notify
    service_notification_commands: service-notify
    host_notification_options: d,r
    service_notification_options: c,w,r
    host_notification_period: 24x7
    service_notification_period: 24x7