Configure Defaults (MDM)

Overview

This page describes the application Defaults that can be configured via MDM. The Defaults are distributed through a .mobileconfig profile as a Preferences Payload and reflect the central application settings.

All keys described here are set within the domain ibi.aws.client.

Technical context

The Defaults are provided via a forced Preferences Payload. This ensures that the values apply system-wide and cannot be changed locally by users.

Example structure in the .mobileconfig:

<key>ibi.aws.client</key>
<dict>
  <key>Forced</key>
    <array>
    <dict>
    <key>mcx_preference_settings</key>
      <dict>
      <!-- Defaults -->
      </dict>
    </dict>
  </array>
</dict>

Available Defaults

Remarks (Required)

Defines the data source of the notification file. This must be accessible on all target devices.

Example:

<key>Remarks</key>
<string>https://server.example.internal/remarks.ibi</string>

Without a valid value, the IBI-aws Client for macOS cannot start.

Logo (optional)

Specifies the path to an image file that is displayed as a logo in the notifications. The path must be accessible on the target device.

Example:

<key>Logo</key>
<string>/Path/To/Logo.png</string>

If no logo is defined, the default logo is used.

Permission flags (Optional)

The following Defaults are used exclusively to control the application behaviour during the initial setup. They indicate whether specific permissions have already been distributed via MDM.

If these flags are set, the corresponding permissions are not requested during the first launch of the IBI-aws Client for macOS in the setup.

SkipAccessibilityPermissionCheckAtStartup

Indicates that the accessibility permission check can be skipped (because it was granted via MDM).

<key>SkipAccessibilityPermissionCheckAtStartup</key>
<true/>

SkipAutomationPermissionCheckAtStartup

Indicates that the automation permission check can be skipped (because it was granted via MDM).

<key>SkipAutomationPermissionCheckAtStartup</key>
<true/>