Feature Request - Extend Key Agent Manager to external tools
Feature Request - Extend Key Agent Manager to external tools
0 vote
Key Agent Manager appears to be the main solution in RDM to make up for Pagent from PuTTY. This solution works great for connections made with RDM, but I currently still need Pagent installed and running with the same keys to make other tools work in our work environment. This is because there is no exposure of the Agent to external tools unless you use an DPS store. Pagent, on the other hand, extends it's capability to any tool on the local machine.
The request here is to make the Key Agent Manager a tool that can intercept local calls (similar to Pagent) and inject the agent key into the process so external tools could be used, even with basic local data store options. Perhaps using the registry or something to create a path passthrough to test or something. Not sure how the implimentation would work, but I know Pagent has already solved that issue so a similar mechanism would be ideal.
Fettuccine Alfredo is Macaroni and Cheese for Adults
All Comments (3)
Hello,
This should already be functional if you keep RDM open with the Key Agent Manager running with the needed keys loaded. It shouldn't require using DPS specifically, any datasource should work this way. Are you sure the agent is running with the keys loaded?
Also, what version of RDM are you using?
Regards,
Hubert Mireault
Hello Hubert,
I was asking support how to do this when I first had issues with it which is why I opened the request. As I worked through some other issues I found they inadvertently pointing to this being an issue but it wasn't - it was a false lead. We resolved the actual issue late yesterday and I was able to do just as you said. I just didn't get a chance to update this post before you responded. Thank you for the quick turn around though.
Fettuccine Alfredo is Macaroni and Cheese for Adults
Thanks for the update, I'm glad to hear the issue is resolved. 🙂
Hubert Mireault