Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v8 backport] Expose reverse tunnel address to web ui #10514

Merged

Conversation

mcbattirola
Copy link
Contributor

@mcbattirola mcbattirola commented Feb 22, 2022

Backport of #10133

webapps v8 backport: gravitational/webapps#616


The ultimate purpose is to show the reverse tunnel address on Help & Support screen on the web UI.

On cloud instances, we use a custom reverse tunnel port for each tenant. In the UI, there is no way to know your reverse tunnel address, which is necessary when adding a trusted cluster.

This PR adds the reverse tunnel address to the GRV_CONFIG object that is injected into the web UI. I added it behind a feature flag to only show on cloud only, should we expose it to everyone?

Note that this field is already publicly exposed via GET [proxy server]/webapi/ping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants