---
title: PingID integration for Mac login 1.3.0 (August 2, 2023)
description: Release notes in the Legacy PingID admin portal for PingID integration for Mac login 1.3.0 (August 2, 2023).
component: pingid
page_id: pingid:release_notes:pid_integration_mac_login_august_2_2023
canonical_url: https://docs.pingidentity.com/pingid/release_notes/pid_integration_mac_login_august_2_2023.html
llms_txt: https://docs.pingidentity.com/pingid/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2026-09-17T09:07:18Z
section_ids:
  new-installation-options-attribute-mapping-exclude-local-users: New installation options - attribute mapping, exclude local users
  no-authentication-prompt-after-cli-installation: No authentication prompt after CLI installation
  login-failure-after-providing-organization-domain-in-ui-installation: Login failure after providing organization domain in UI installation
---

# PingID integration for Mac login 1.3.0 (August 2, 2023)

## New installation options - attribute mapping, exclude local users

New PingID

When installing the integration with Mac login, you can now specify that an Active Directory attribute should be used for identifying users. You can also specify that PingID authentication should not be used for local user logins. For details, see [Installing PingID integration for Mac login using UI wizard](../pingid_integrations/pid_installing_pid_integration_mac_login_using_ui_wizard.html) and [Mac login command line reference](../pingid_integrations/pid_mac_login_command_line_reference.html).

## No authentication prompt after CLI installation

Fixed STAGING-19298 PingID

There were cases where users weren't getting an authentication prompt when logging back in to their Mac after carrying out a command-line installation of the integration that included use of the `--domainPostfix` parameter. This issue has been fixed.

## Login failure after providing organization domain in UI installation

Fixed STAGING-19762 PingID

There were cases where users couldn't log in after carrying out a UI installation of the integration that included specification of an organization domain. This issue has been fixed.