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

idpbuilder in codespaces needs https not http #452

Closed
agardnerIT opened this issue Nov 19, 2024 · 1 comment · Fixed by #456
Closed

idpbuilder in codespaces needs https not http #452

agardnerIT opened this issue Nov 19, 2024 · 1 comment · Fixed by #456
Labels
bug Something isn't working

Comments

@agardnerIT
Copy link

Spinning up idpbuilder following hte codespaces instructinos, I see:

Can Access ArgoCD at http://literate-space-halibut-96wwg755xv7hxp7g-8080.app.github.dev:8080/argocd

I believe the URL is build on this line and indeed the docs instructions do specify --protocol http

However, GitHub really does want an https:// URL.

So...

  1. Should the docs be updated to read --protocol https
  2. Does the code need a special condition if Github codespaces then protocol is https?
@nabuskey
Copy link
Collaborator

Hey @agardnerIT,

Thanks for reporting this issue. In Codespaces or other environments where a proxy is involved in front of idpbuilder, the ArgoCD URL given at the end is inaccurate. See this issue: #269

The --protocol http is needed for Codespaces to proxy requests correctly. Otherwise, you have two TLS certs involved when making requests from your laptop.

This isn't just an issue with protocol either btw. The port number printed is incorrect as well. e.g. 443 vs 8080. The expectation we have from users is to access it using the port forward popup you get in Codespaces, not the URL given by idpbuilder.

Having said that, we do need to fix this.

@nabuskey nabuskey added the bug Something isn't working label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants