Windows
Britive integrates with Windows servers through the Britive Access Broker, enabling just-in-time RDP access without maintaining standing credentials. The broker connects to target servers via WinRM and executes PowerShell scripts to grant and revoke access at checkout and checkin.
Access Patterns
Three patterns are available:
- Temporary local user — creates a local account with a randomly generated password at checkout; deletes it at checkin. Suited for scenarios where users need a dedicated local identity.
- Local group membership — adds the user’s existing domain account to a local group (e.g.
Remote Desktop Users) at checkout; removes it at checkin. No local account creation required. - Browser-based via Bridge — creates the temporary local user but hands the password to Britive Bridge instead of the user; the RDP session opens in the browser through a recorded proxy, and no credential reaches the user.
The broker communicates outbound to Britive over HTTPS only — no inbound ports are required on the broker host. WinRM (port 5985) is required only between the broker and target servers.
In This Section
- Getting Started
Deploy the Britive Access Broker on a Windows host and register Windows servers as Resource Manager resources for JIT RDP and local account access.
- Temporary Local User Access
Create and delete temporary Windows local user accounts at checkout and checkin for JIT RDP access — no standing credentials remain between sessions.
- EC2 Instance Access (SSM)
Grant just-in-time access to EC2 Windows instances via AWS Systems Manager — create a local admin or AD user at checkout and remove it at checkin, across one or many instances.
- Local Group Access
Add and remove users from local Windows groups on remote servers via WinRM for JIT RDP access — no local account creation required.
- Browser-Based RDP via Bridge
Open clientless, recorded RDP sessions to Windows servers through Britive Bridge — temporary local users created at checkout, deleted at checkin, passwords never shown to the user.