boundary dev -api-listen-address=0.0.0.0 -cluster-listen-address=0.0.0.0 -proxy-listen-address=0.0.0.0 -worker-public-address=192.168.1.80Using token none (make sure to unset the BOUNDARY_TOKEN env variable if set):
# boundary authenticate password -auth-method-id ampw_1234567890 -login-name admin -password "password" -token-name=noneUsing BOUNDARY_TOKEN env variable:
export BOUNDARY_ADDR=http://192.168.1.80:9200
boundary authenticate password -auth-method-id=ampw_1234567890 -login-name=admin -password=password -token-name=none -format=json | jq -r ".token" > boundary_token.txt
export BOUNDARY_TOKEN=$(cat boundary_token.txt)This works well with WSL
boundary connect ssh -target-id ttcp_tP3Uoe7X2d -host-id hst_uFcRGR4FCFwireshark filter: ip.addr == 192.168.1.80
This works well with WSL, just make sure you increase the connection count to at least 2 for rdp to work.. Terraform already takes care of this.
boundary connect rdp -target-id ttcp_nqhPabGuma -host-id hst_WB9GVkJe8Lwireshark filter: ip.addr == 192.168.1.80
- Introduction
- Slides to Explain Boundary
- Getting Started and Installation
- Start Boundary in Dev Mode
- Run Terraform to Configure it
- Authenticate to Boundary
- SSH Connect to Linux Server
- Wireshark the SSH Connection
- RDP Connect to Windows Server
- Wireshark the RDP Connection
- Conclusion
Blog Announcement Armon's Whiteboard Terraform Boundary Provider Getting Started Learn Guide Production AWS Reference Architecture Production High Availability Architecture
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent