Feature Proposal: Support alternative tunneling backends (Google Identity, institutional tunnels)
Summary
CS-Bridge currently relies on Microsoft Dev Tunnels for remote port forwarding and authentication. This works well, but restricts identity provider options and creates vendor lock-in.
Expanding tunneling backend support could enable:
- Google / EDU authentication
- Institution-hosted tunnel servers
- Alternative secure port-forwarding layers
Why This Matters
Some institutions may prefer non-Microsoft identity providers. Supporting alternatives opens usage to a broader academic audience.
Possible Approaches
- Google Identity + Cloud IAP tunnel
- Institution-hosted reverse-tunnel backend
- Pluggable tunnel provider abstraction in linkspan
- Fallback SSH-only tunneling for sites without devtunnels.ms
Challenges
- Requires abstraction layer in linkspan
- Needs new VS Code connect protocol
- Must ensure performance & reliability
Long-Term Impact
This becomes a research-grade enhancement, increasing adoption beyond Microsoft ecosystems and allowing greater flexibility.
Status
Exploratory: would require design discussion with maintainers.
Feature Proposal: Support alternative tunneling backends (Google Identity, institutional tunnels)
Summary
CS-Bridge currently relies on Microsoft Dev Tunnels for remote port forwarding and authentication. This works well, but restricts identity provider options and creates vendor lock-in.
Expanding tunneling backend support could enable:
Why This Matters
Some institutions may prefer non-Microsoft identity providers. Supporting alternatives opens usage to a broader academic audience.
Possible Approaches
Challenges
Long-Term Impact
This becomes a research-grade enhancement, increasing adoption beyond Microsoft ecosystems and allowing greater flexibility.
Status
Exploratory: would require design discussion with maintainers.