sebastiengrossetti

That's great news, thanks for this!!

It shouldn't be too complicated.

No promises but I'll try to squeeze this for 2027.1.

It cannot be in 2026.3.x as this will require backend changes and we only release those with a major version.

@Jonathan Lafontaine

very nice, Merci

And do you know: will I get any notification when available, or do I need to read through each version's release notes?

I think I've got something that would cover all bases.

We would keep the combo box with "default", "prefill and prompt" and "prefill and don't prompt". Selecting either prefill option would reveal a button.

That button would query CyberArk, show the prerequisite window and let you customize each item. We would save that state and reuse it when actually connecting.

Here's a mockup.

How does that sound?

@Jonathan Lafontaine

How does that sound?? well... AMAZING !! :D

this sounds just like it's exactly how it should be :)

Thanks for your involvement in searching for a solution!!

Is this an easy one we have chances to see in next version, or will this be a longer development, you know?

The prerequisites window is dynamic and supports custom items. Supporting all possible mandatory settings, the way we planned for the reason field, wouldn't be possible.

Back to the drawing board.

@Jonathan Lafontaine

Well, I guess then we can go for the "reason-only" proposal.

As told, it would already be already a great step ahead :)

Hi Sebastien,

Here's what we came up with. Let me know if this would solve your issue.

In an entry's advanced settings, in the CyberArk section, we would add a new combo box that controls how the reason is handled.

One of the available options would be "prefill and don't prompt." Selecting a "prefill" option would display a textbox and let you enter a reason.

Of course, if other prerequisites are mandatory, we will show the dialog.

Here's a mockup.

How does that sound?

@Jonathan Lafontaine

Hi Jonathan, that sounds like a great step forward, indeed solving our point for most connections.

nevertheless I fear the window will still appear if you don't also include the same kind of choice for the "Map local drives" checkbox.

would that be possible as well, you think?

Thanks !!

Hi @Jonathan Lafontaine and thanks for this first feedback.

Unfortunately, this is not really what I have in mind. the use we have here is to connect to a set of servers through CyberArk PSM, or simply requesting CyberArk credentials.

The policy (setup by Security team in CyberArk) is to request a reason for the password gathering from CyberArk. this is a single string, and can be anything.

Nevertheless, to be in accordance with policies in our company, we have to enter the purpose, which is most of time the role of the server we try to connect to.

Having around 15 different servers roles around, the "last used" option would most of the time not fit, and we would need to type it again.

Ideally, this string is preconfigured in each RDP connection object, so it's then sent to CyberArk's question "enter comment" that pops up at password gathering time.

attached are the current windows in two different cases: with PSM connection (checkbox about local drives - ideally possible to configure per RDP connection as well, now I think about it :)) or simply by using a CyberArk credentials object.

Thanks for your consideration :)

This would be a huge gain of time for me and my team if there was a way to fill-in a "reason" for credentials gathering from CyberArk in each RDP connection object.

This way, the double-clic would not end up into this window asking for the reason, but directly end-up in the RDP session in best times.

Thanks for considering this!