Hello Boundary Community!
We’re excited to share that we’re working on adding RDP credential injection to Boundary. This will allow Boundary to securely inject credentials into RDP sessions without exposing them to end-users or their devices - similar to our current SSH credential injection enterprise functionality.
What is RDP credential injection?
When implemented, this feature will enhance security by eliminating the need for users to directly handle RDP credentials. Boundary will securely provide these credentials to the RDP session, reducing credential exposure and improving the user experience.
Why we need your input
For secure RDP credential injection, Boundary requires trusted certificates to establish encrypted channels between components. We’re evaluating several approaches to certificate management:
- Integration with existing enterprise CA infrastructure (e.g., Microsoft ADCS)
- Delegated intermediate CA functionality
- Various certificate distribution mechanisms
- Self-signed certificates with manual distribution
How you can help
If your organization uses RDP for accessing Windows environments, we’d love your input on certificate management preferences. We’ve created a quick survey to help us understand your needs:
→ RDP Certificate Management Survey
Your responses will directly influence our implementation priorities as we build this feature. The survey takes about a minute to complete, and your feedback is invaluable to our product development process.
Have additional thoughts about RDP support in Boundary? Please share them in the comments below!
Thank you for contributing to Boundary’s development!
Dan Rohan & the rest of the Boundary team