RDCMan PAMPlugin - FIDO2 Support?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

RDCMan PAMPlugin - FIDO2 Support?

L1 Bithead

I was testing the RDCMan PAMPlugin and noticed that FIDO2 does not seem to be supported, seen in the image below:

Field_Content_versions_oct20__068Ht00000VfIyuIAF.pngI did notice that the login process seems very similar to the PSMConnectionManager when selecting the “Use legacy IE browser for authentication” setting and I do see the patch notes for PSMClient v2.6.6 includes “The embedded browser has been upgraded (Edge-based)”.

 

@Shay Tevet​ I believe you have been involved with the development both of these Marketplace apps (but please correct me if I’m wrong). Would it be possible to update the RDCMan PAMPlugin to also use Edge’s WebView2 embedded browser similar to the PSMClient applications?

4 REPLIES 4

L1 Bithead

Here’s a bit more detailed breakdown of the current issue since I was pretty sparse on the details above:

1.     I downloaded the Plugin.PAM.dll file and placed it in my RDCman install directory

2.     I start RDCman.exe and see the following popup

Field_Content_versions_oct20__068Ht00000VfTtiIAF.png3.     I enter in my Pcloud PVWA URL and click Auth

Field_Content_versions_oct20__068Ht00000VfTr7IAF.png4.     I enter my username in the web browser pops up to login to Pcloud

Field_Content_versions_oct20__068Ht00000VfTtnIAF.png5.     After providing my username and password, I get stuck at the FIDO2 MFA prompt

Field_Content_versions_oct20__068Ht00000VfTtxIAF.pngI also took a closer look at this problem in Process Monitor and can confirm that the Internet Explorer based mshtml.dll is being called to render the PVWA login screen. Would it be possible to update this app to use WebView2 similar to the PSMClient application?

L4 Transporter

Hi @Alexander Swinford​ 

 

As the community has not provided an answer to this question, could you kindly share if you were able to resolve the issue and how?

Your solution could help other community members who may face a similar issue.

 

If the issue is still relevant, I would advise to raise a support case for this error.

 

Thanks, Liad

Hello Liad,

 

I was not able to resolve this issue as it likely requires code changes within the Plugin.PAM.dll file provided by RDCMan PAMPlugin.

 

I will attempt to make a support case surrounding this issue, but I am unsure if I will get any answer due to the nebulous ownership of this plugin. Even though both the RDCMan PAMPlugin and the PSMClient are developed via some sort of coordination with CyberArk (ShayT seems to handle releases), they are both listed as a “Community” integrations which are “Not reviewed or supported”. Despite this, I will still open a support case and will respond back here if I am provided any workarounds/updates.

 

Thanks,

Jerry

As I suspected, I was told that the RDCMan PAMPlugin is "a community integration not supported by CyberArk R&D therefore updates aren’t added to the typical Product Management Roadmap" after opening up a support case. While not explicitly stated in my support case, I would expect the same response for any questions surrounding PSMClient as it too is technically a “Community” integration despite the subtext clearly stating that both integrations are "Developed By CyberArk".

  • 323 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!