Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

bug(sdk/go): browser login callback binds 127.0.0.1 but redirect_uri uses localhost

Open Beginner friendly
#4,518 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go

Research direction

The listener is in oidc/authcode.go (startCallbackServer, which calls net.Listen on 127.0.0.1) and the redirect URI is built in oidc/oidc.go (loginBrowser, which uses localhost). Read both, then decide whether to change the redirect host to 127.0.0.1 or make the listener cover both loopback families. Done means the host in the redirect URI matches what the server accepts, and the Login flow still completes on a normal IPv4 host. The issue has not been reproduced, so confirm the IPv6 case before treating it as fixed.

Written by the indexing model from the issue text.

Description

state:triage-needed
User Story

I use OpenShell and build automation against its SDKs. I found this while reviewing sdk/ on main; it is identified from the code paths cited below and has not yet been reproduced against a live gateway.

Problem Statement

startCallbackServer listens on 127.0.0.1:<port>, but loginBrowser sends redirect_uri=http://localhost:<port>/callback. The CLI uses 127.0.0.1 for both.

Impact / Why This Matters

On hosts or browsers where localhost resolves to ::1 first without IPv4 fallback, the IdP redirect fails to reach the callback and Login times out.

Acceptance Criteria
  • The redirect URI host matches the address the callback server listens on (or the server listens on both loopback families).
Reproduction Steps

Code reference: oidc/authcode.go net.Listen("tcp", "127.0.0.1:%d") vs oidc/oidc.go fmt.Sprintf("http://localhost:%d/callback", port). On a host where localhost maps only to ::1, run oidc.Login.

Suggested UX (if applicable)

No response

Environment
  • OpenShell: main @ 82977e2 (2026-10-13)
  • SDK: Go (sdk/go/openshell/v1/oidc)
  • Toolchain: Go 1.25.4 linux/amd64, Node 22
Logs

Dominant language
Rust
Stars
15.4k
Forks
1.7k
Avg merge
2d 3h
Merged PRs (30d)
374

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/OpenShell

All issues in NVIDIA/OpenShell

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.