Serve a landing page at the base domain that links to every user-facing service

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
authentication, frontend, infrastructure

Research direction

Start with ADR 0013 and the #176 perimeter, then inspect the shared.access.routes contract and the platform phase’s static serving setup. Define shared/portal, derive its page from enabled user-facing routes, and clarify the remaining checklist items: exclude the portal link, specify the identity link, add shared services, and update #182 step 2. Done when the open acceptance criteria are met, including bare-domain certificate coverage and the login and return flows.

Written by the indexing model from the issue text.

Description

priority: P1 roadmap track: identity track: portal

Milestone: v0.5-alpha — Identity and Authorization
Roadmap sequence: #183 (revised 2026-10-05)

Context

ADR 0013 gives every user-facing service its own host (https://<service>.<stage>.<base_domain>), but nothing answers at https://<base_domain> itself. A user has to know every host, and step 2 of the #182 walkthrough ("opens the platform's HTTPS URL") has no destination.

This is portal phase 1. Phase 2 (web admin console) and phase 3 (integrated workspace UI) are post-v1; role assignment is done with olf users (#331).

Scope

  • A static page at https://<base_domain> listing the enabled, user-facing routes of shared.access.routes, grouped by stage. The list is derived from the contract, never hardcoded.
  • Served by a minimal static server in the platform phase (the route set is static infrastructure, ADR 0002); its route is added to shared.access and ADR 0013.
  • Behind the #176 perimeter like every other route. Links are not filtered by role in this phase; the perimeter denies what a role cannot open.

Out of scope

  • Role-aware filtering, admin actions, embedded service UIs.

Acceptance criteria

  • https://<base_domain> serves the page with a trusted certificate.
  • It lists exactly the enabled user-facing routes; internal and disabled routes are absent.
  • An unauthenticated request is sent to login.
  • Completing invitation setup or company SSO returns the member to this page without another credential prompt when opening an authorized service.
  • Denied service access has a clear response and a return-to-portal link.
  • Define shared/portal, explicitly support the bare-domain route, and issue a certificate covering the bare domain (a subdomain wildcard alone does not cover it).
  • Exclude the portal's own link; specify whether the identity route is an account-management link, and provide a shared-services section alongside stages.
  • #182 step 2 lands on this page.
Dominant language
Python
Stars
26
Forks
6
Avg merge
6h 44m
Merged PRs (30d)
314

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.