How to configure CardDAV settings on macOS devices

CardDAV (vCard Extensions to WebDAV) is a protocol that allows the users to access and share contacts on a server. Admins can configure CardDAV settings for macOS devices from the Hexnode console. With this functionality, admins can remotely add a contact account to the user’s device thus enabling them to synchronize contact data with any server that supports CardDAV.

Configure CardDAV settings via policy

To configure CardDAV settings on your Mac devices via policy,

1. Login to your Hexnode portal.
2. Navigate to Policies > New Policy. Assign a suitable name and description (optional) for the policy. You can also choose to continue with an existing policy.
3. Go to macOS > Accounts > CardDAV. Click Configure.

Associate policy with devices/ groups

If the policy has not been saved,

1. Navigate to Policy Targets > +Add Devices.
2. Choose the target entities and click Ok. Click Save.
3. You can also choose to associate the policy with device groups, users, user groups or domains from the left pane of the Policy Targets tab.

If the policy has been saved,

1. Choose the desired policy from the Policies tab.
2. Click on Manage drop-down and select Associate Targets. Choose the target entities and click Associate.

What happens at the device end?

On associating the policy with the macOS device, the configured CardDAV account will get added and the contacts will sync with the device. The synchronized contacts can be accessed from the Contacts app on the Mac.

FAQs

1. What is the default port for CardDAV connections?

   The default port is 8443, but admins can specify a different port if required by their CardDAV server configuration.

2. Is SSL mandatory for CardDAV connections?

   SSL is enabled by default and strongly recommended to secure communication between macOS devices and the CardDAV server. Disabling SSL may expose sensitive contact data.

3. Can multiple CardDAV accounts be configured on the same Mac?

   Yes. Admins can configure multiple CardDAV accounts by creating separate policies or adding multiple accounts under the same policy, each with its own description and server details.

Troubleshooting Guides:

1. Authentication Failure

Symptom: User cannot log in; contacts fail to sync.

Cause: Incorrect username/password or misconfigured wildcards.

Solution:

1. Verify credentials in the policy.
2. Ensure wildcards (%email%, %alternateemail%) are mapped correctly to user data.
3. Update and redeploy the policy with corrected values.

2. The contacts are not syncing

Symptom: Account appears on device, but contacts do not sync.

Cause: Incorrect host name, port, or server path.

Solution:

1. Double-check the Host Name (IP/FQDN) and Port (default: 8443).
2. Confirm the CardDAV server is reachable and supports syncing.
3. Redeploy the policy with corrected server details.

Best Practices

1. Use SSL: Keep SSL enabled to secure communication between macOS devices and the CardDAV server.
2. Verify Server Details: Double-check host name (IP/FQDN) and port (default: 8443) before deployment.
3. Leverage Wildcards: Use %email% and %alternateemail% to auto-populate usernames dynamically.
4. Test Before Rollout: Apply the policy to a small group of Macs first to confirm correct syncing.
5. Keep Credentials Updated: Update policies promptly if server usernames or passwords change.
6. Audit Sync Status: Regularly check that contacts are syncing correctly in the Contacts app.
7. Document Configurations: Maintain internal records of server paths, ports, and authentication methods for consistency.