# Credential release activity does not auto login when connecting using Mac

**URL:** <https://community.netwrix.com/t/credential-release-activity-does-not-auto-login-when-connecting-using-mac/120505>\
**Category:** Privilege Secure Ideas\
**Tags:** privilege-secure, under-review\
**Created:** [January 7, 2026, 12:28am UTC](https://community.netwrix.com/t/credential-release-activity-does-not-auto-login-when-connecting-using-mac/120505 "2026-01-07T00:28:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pasanillege](https://avatars.discourse-cdn.com/v4/letter/p/3ec8ea/32.png) [@Pasanillege](https://community.netwrix.com/u/Pasanillege)\
**Post date:** [January 7, 2026, 12:28am UTC](https://community.netwrix.com/t/credential-release-activity-does-not-auto-login-when-connecting-using-mac/120505/1 "2026-01-07T00:28:43Z")

</div>

### What is a one sentence summary of your feature request?

Credential release activity does not auto login when connecting using Mac

### Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

The exact same activity works as expected when using a windows device to connect. So, it is better if we can have the same user experience when they are using a Mac.

Changing the RDP file “prompt for credentials on client:i:1” to “prompt for credentials on client:i:0” might fix the issue.

### How do you currently solve the challenges you have by not having this feature?

Users have to click continue on the pop-up screen to connect to the destination host.

---

<div class="post-metadata">

**Author:** ![dpiazza](https://yyz1.discourse-cdn.com/netwrix/user_avatar/community.netwrix.com/dpiazza/32/1531_2.png) [@dpiazza](https://community.netwrix.com/u/dpiazza)\
**Post date:** [January 30, 2026, 8:06pm UTC](https://community.netwrix.com/t/credential-release-activity-does-not-auto-login-when-connecting-using-mac/120505/2 "2026-01-30T20:06:49Z")

</div>

Hi Pasan,

Thanks for the suggestion!

Making that change to the RDP file does seem to be the answer, although we have to research if that impacts existing workflows for users of non-Mac operating systems.

I’ll add this to the backlog for tracking.

- Dan
