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.

Sign up for GitHub

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

Jump to bottom

Redirect HTTP to HTTPS when connecting to RDS webclient #361

Closed
5 tasks done
martintoreilly opened this issue Jun 19, 2019 · 3 comments
Closed
5 tasks done

Redirect HTTP to HTTPS when connecting to RDS webclient #361

martintoreilly opened this issue Jun 19, 2019 · 3 comments

Comments

@martintoreilly
Copy link
Member

martintoreilly commented Jun 19, 2019 •
edited by jemrobinson
Loading

✅ Checklist

  • I have searched open and closed issues for duplicates.
  • This is a problem observed when using a Data Safe Haven.
  • I can reproduce this with the latest version.
  • I have read through the documentation.
  • This isn't an open-ended question (open a discussion if it is).

💻 System information

  • Data Safe Haven version: 0.3.0-beta
  • Browser details: All
  • Operating system details: All

🚫 Describe the problem

The Microsoft Remote Desktop gateway can only be accessed over https but we do not currently run an HTTP->HTTPS upgrade route. This means that users must explicitly type https rather than http.

🚂 Workarounds or solutions

  • Add an nginx instance in front of the RDS server
  • Use an application gateway
@martintoreilly martintoreilly added this to the DSG Network @ Bristol milestone Jun 19, 2019
@jemrobinson
Copy link
Member

We currently don't have anything exposed over HTTP but we allow don't do a redirect.

@jemrobinson
Copy link
Member

Guacamole does this via nginx.

@jemrobinson jemrobinson mentioned this issue Aug 19, 2022
Closed
@jemrobinson jemrobinson removed this from the DSG Network @ Bristol milestone Aug 31, 2022
@craddm
Copy link
Contributor

craddm commented Sep 12, 2023

Closed as MS RDS is now removed, as of merging of #1535 into develop (see also #1159)

@craddm craddm closed this as completed Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jemrobinson @craddm @martintoreilly