OTP Prompt String not working on macOS (RDM Free) - still prompting for OTP

Hi eroi00,

Thanks for the report, sorry for the trouble.

To help track this down, could you share:

1. The session type for this host (SSH Shell, SFTP, Telnet, etc.)
2. Your Connection – One-time password settings (Source and Usage) for this entry, a screenshot would help
3. Your Windows RDM version, for comparison
4. Whether a brand-new test entry created directly on macOS shows the same issue
5. Debug logs from a macOS session where the prompt appears: Send logs from Remote Desktop Manager macOS

Once we have these, we'll be able to dig into whether it's a config or platform issue.

Thanks!

Hi,

Thanks for getting back to me. Here is the information you requested:

1. Session type: SSH

2. OTP Settings: Source is set to Inherited (Linked vault), Usage is set to Inherited (Specific to session), OTP prompt string: "TOTP - Enter Token".

Edit: screenshots from macOS, not windows :-)


We tried to set "Linked (vault)" and "Specific to session" withouth inheritance, outcome was the same.

3. Windows RDM version: 2026.2.17.0 Arm 64-bit (tested as well on intel cpu newest version, works fine)

4. Brand-new test entry: I created a fresh test entry directly on macOS, and the issue still occurs.

5. Help -> Session logs from macOS:

[8/7/2026 2:28:52 PM] Devolutions.ProtocolsSharp: 2026.6.2.1 OS: macOS
[8/7/2026 2:28:52 PM] Terminal font: Menlo [Menlo, fixed=True]

[8/7/2026 2:28:52 PM] Starting SSH, verbose level: 4
[8/7/2026 2:28:52 PM] Setting up connection
[8/7/2026 2:28:52 PM] Connecting to: xxx.xxx.xx:xxxx (IPV_ANY)
[8/7/2026 2:28:52 PM] SSH version banner: SSH-2.0-PBPS-SM-1.0.0

[8/7/2026 2:28:52 PM] Sending kex init
[8/7/2026 2:28:52 PM] Received kex init
[8/7/2026 2:28:52 PM] Selected algorithms: curve25519-sha256, ssh-ed25519, aes256-ctr, aes256-ctr, hmac-sha2-256-etm@openssh.com, hmac-sha2-256-etm@openssh.com, none, none
[8/7/2026 2:28:52 PM] Sending Ed25519 kex init
[8/7/2026 2:28:52 PM] Received Ed25519 kex reply
[8/7/2026 2:28:52 PM] Successfully authentified server
[8/7/2026 2:28:52 PM] Sending new keys message
[8/7/2026 2:28:52 PM] Received new keys message
[8/7/2026 2:28:52 PM] Sending userauth service request
[8/7/2026 2:28:52 PM] Received service accepted message
[8/7/2026 2:28:52 PM] Sending userauth init request
[8/7/2026 2:28:52 PM] Received userauth failure: publickey,password,keyboard-interactive
[8/7/2026 2:28:52 PM] Starting interactive authentication
[8/7/2026 2:28:52 PM] Sending userauth interactive request
[8/7/2026 2:28:52 PM] Received userauth info request:
[Name->Password Safe SSH Direct Connect]
[Prompt->Password: ]
[8/7/2026 2:28:52 PM] Sending userauth interactive response: *
[8/7/2026 2:28:52 PM] Received userauth info request:
[Instruction->Your session is loading. Please wait...]
[8/7/2026 2:28:52 PM] Sending userauth interactive response: 
[8/7/2026 2:28:53 PM] Received userauth info request:
[Prompt->TOTP - Enter Token: ]

And it waits like that for OTP input.

Thanks!

Hi again...

While gathering the screenshots, I think I managed to pinpoint the exact cause of the issue. It appears to be a bug in how RDM for macOS handles OTP Usage overrides between a parent folder and a host entry.
Configuration setup:

• Parent Folder:
  • OTP Source: Linked (Vault)
  • OTP Usage: Append to the password
• Host Entry (inside the folder):
  • OTP Source: Inherited (Linked (Vault))
  • OTP Usage: Specific to session

The issue: Even though the Host entry explicitly had its Usage set to Specific to session, the macOS client was not applying this setting.
Workaround: As soon as I changed the OTP Usage on the Parent Folder level from Append to the password to Specific to session, the OTP Prompt String started working as expected on macOS.

It seems the macOS client lets the Parent Folder's OTP Usage override the Host's explicit Usage setting, rather than respecting the Host's local configuration.

Host:

Folder:


Thanks for your time!