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

Dex: readable page when a GitHub sign-in is refused

Closed
  • Is something wrong?
#438 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
66/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github, python
Domain
authentication, frontend

Research direction

Read docs/setup/github-oauth-app.md and check the Dex v2.46.0 frontend template configuration, especially frontend.dir and the stock templates. Determine the smallest supported way to override error.html while keeping the rest of the frontend stock. Done when the stated GitHub refusal and both likely causes appear with the setup guide link, and the uninstalled-app sign-in shows the custom page instead of a generic 500.

Written by the indexing model from the issue text.

Description

track: identity

Follow-up to #433/#436. When the GitHub connector refuses a login (app not installed on the org, or the user in no mapped team), Dex renders its own error page:

Internal Server Error — Authentication failed. Please contact your administrator or try again later.

The browser never returns to oauth2-proxy, so #436's perimeter error page does not appear. The cause is only in the Dex log: user not in org or application not authorized to read org data.

Fix: give Dex a custom error.html, either through frontend.dir with the default templates plus an override, or the smallest supported mechanism in v2.46.0. Show:

  • that sign-in was refused by the GitHub check;
  • the two likely causes (GitHub App not installed on <org>, not in a mapped team);
  • a link to docs/setup/github-oauth-app.md.

Keep everything else the stock Dex frontend.

Acceptance: signing in with the app not installed shows that page, not the generic 500.

🤖 Generated with Claude Code

Dominant language
Python
Stars
26
Forks
6
Avg merge
12h 26m
Merged PRs (30d)
162

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 OpenLakeForge/openlakeforge

All issues in OpenLakeForge/openlakeforge

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.