Skip to content

Settle the window.__MINT_CONFIG__ values for the TACC deployment #75

Closed

Description

@mosoriob

Question

The deployed app reads one nested window.__MINT_CONFIG__ object, written by the container entrypoint at startup from a single generator function. Decide the actual values for TACC's cluster and record them as chart values:

  • Hasura GraphQL endpoint — TACC's, not ISI's. Confirm which one their cluster serves and whether it is the same instance the Lit app uses today.
  • CKAN — DATA_CATALOG_API and DATA_CATALOG_BROWSE_URL as two distinct values (T6 may repoint the first at a proxy path).
  • OAuth2 — issuer, client id, redirect URI, matching what T5 confirmed.

The Lit app used flat window.REACT_APP_* globals; the two contracts are incompatible, so nothing can be copied across verbatim from the existing deployment.

Deriving these from the other components' ingress declarations is what the chart already does for service endpoints — reuse that rather than hardcoding hostnames where you can.


Sharpened by Commit .env.example and local-setup notes so ui-react runs for someone who is not Max:
the key list is complete, and one key is gone.

That ticket deleted MODEL_CATALOG_API. No code used it. Decide these 12 keys:

HASURA_ENDPOINT · AUTH_SERVER · AUTH_CLIENT_ID · AUTH_PROVIDER · AUTH_REALM ·
GOOGLE_MAPS_KEY · DATA_CATALOG_API · DATA_CATALOG_BROWSE_URL · ENSEMBLE_MANAGER_API ·
AUTH_CALLBACK_ORIGIN · AUTH_PREVIEW_ORIGIN_ALLOWLIST · WELCOME_MESSAGE

Three keys need a decision, not a hostname lookup:

  1. Set ENSEMBLE_MANAGER_API. MintThread.tsx reads it. The generator omits the key
    when it is unset, so the page can find the absence. If you leave it unset, thread
    execution stops without an error. The smoke test in
    #76 would show a missing feature, not
    a fault.
  2. AUTH_PREVIEW_ORIGIN_ALLOWLIST is for Vercel. It corrects a browser origin that
    differs from the registered origin. At mint.tacc.utexas.edu the two origins are the
    same. Leave the key empty. Do not copy it from the Vercel project. See the Check whether the OAuth2 redirect URI for mint.tacc.utexas.edu is already registered #73 block below
    for AUTH_CALLBACK_ORIGIN.
  3. AUTH_REALM is for Keycloak only. Tapis ignores it.

Read ui-react/.env.example before you decide. It gives each key, its default, and its
behaviour when unset.


Sharpened by Check whether the OAuth2 redirect URI for mint.tacc.utexas.edu is already registered:
the OAuth2 bullet is now settled — these are the values, not a question:

auth:
  provider: tapis                        # chart default already correct
  server: https://portals.tapis.io       # chart default already correct
components:
  ui_react:
    config:
      client_id: "mint"                  # the SAME client the Lit app uses
      auth_callback_origin: ""           # empty = use the deployment's own origin

mint is the client registered in the Tapis portals tenant with callback_url
exactly https://mint.tacc.utexas.edu/oauth2/callback — which is the string ui-react
sends from that origin, verified live against the IdP. No new client, no IdP change.

⚠️ Ignore the chart's own advice here. charts/mint/values.yaml and the fail in
templates/ui-react-config.yaml insist the React client "must be a client distinct from the
legacy UI's". That reasoning assumes the two apps serve different origins; in this rollout
they share one origin sequentially (Lit is unrouted, per #77), and they want the identical
redirect URI. The template only hard-fails on an empty client_id, so "mint" renders fine.

The host is part of the OAuth contract: Tapis matches redirect_uri on scheme, host and path,
so the ingress must serve exactly https://mint.tacc.utexas.edu — plain http:// is rejected.

Activity

  1. added
    wayfinder:taskWayfinder ticket: manual work that unblocks a decision
    on Aug 8, 2026
  2. self-assigned this
    on Aug 8, 2026
  3. mosoriob commented on Aug 8, 2026

    @mosoriob
    ContributorAuthor

    Answer: set two values. The other ten are already correct.

    The deployed Lit app publishes its runtime config at https://mint.tacc.utexas.edu/config.js.
    That file is TACC's own truth, not ISI's. Every endpoint below comes from it.

    The 12 keys at TACC

    Key Value at mint.tacc.utexas.edu Action
    HASURA_ENDPOINT https://graphql.mint.tacc.utexas.edu/v1/graphql none — derived
    AUTH_SERVER https://portals.tapis.io none — chart default
    AUTH_CLIENT_ID mint set client_id
    AUTH_PROVIDER tapis none — chart default
    AUTH_REALM not emitted none — correct, Tapis ignores it
    GOOGLE_MAPS_KEY TACC's own key none — inherited
    DATA_CATALOG_API https://ckan.tacc.utexas.edu set data_catalog_api
    DATA_CATALOG_BROWSE_URL https://ckan.tacc.utexas.edu none — falls back to the API
    ENSEMBLE_MANAGER_API https://ensemble-manager.mint.tacc.utexas.edu/v1 none — derived
    AUTH_CALLBACK_ORIGIN empty none
    AUTH_PREVIEW_ORIGIN_ALLOWLIST not emitted none — correct
    WELCOME_MESSAGE Welcome to MINT none — chart default matches

    GOOGLE_MAPS_KEY and WELCOME_MESSAGE are top-level chart values shared with the Lit app.
    The ui_react template reads the same two values. TACC's overrides apply automatically.

    The values to add

    components:
      ui_react:
        enabled: true
        config:
          client_id: "mint"
          data_catalog_api: "https://ckan.tacc.utexas.edu"

    Why derivation is safe for Hasura and Ensemble Manager

    I did not have to guess whether TACC declares ingress.tls. The Lit template and the
    mint.component_url helper use the same {{ if .ingress.tls }} idiom. Lit's live output shows
    REACT_APP_GRAPHQL_ENABLE_SSL = true and an https:// ensemble manager URL. So both ingresses
    declare TLS, and derivation gives https:// for both. A missing TLS block would have given
    http:// and mixed-content failures. The /v1 suffix comes from api_version, which Lit's
    live URL also confirms.

    Why CKAN must be explicit

    The ui_react template derives DATA_CATALOG_API from components.data_catalog. TACC does not
    use that component; it is disabled by default. TACC uses external_services.ckan.url, which
    ui-config.yaml reads and ui-react-config.yaml does not. So the key is omitted from the
    ConfigMap and the app falls back to its compiled default. That default is
    https://ckan.tacc.utexas.edu — the right value by coincidence. Set it explicitly.

    Chart debt: ui-react-config.yaml should read external_services.ckan.url, as
    ui-config.yaml does. The override makes the fix optional, not urgent.

    Verified live from the https://mint.tacc.utexas.edu origin

    • Hasura preflight returns Access-Control-Allow-Origin: *. An anonymous query returned a row
      from modelcatalog_standard_variable.
    • Ensemble Manager preflight returns 204 with the same wildcard. GET /v1/executions/<id>/logs
      returns 404 for an unknown id, so the route exists and the service is live.
    • CKAN sends no X-Frame-Options and no CSP. The datasets browse iframe will render.

    CORS is therefore not a risk for Hasura or the Ensemble Manager. Both send a wildcard to every
    origin. Only CKAN uses an allowlist, and #71 settled that.

    No CKAN API key is needed → #76

    Lit sets DATA_CATALOG_KEY from a chart secret. ui-react has no such key and needs none. It
    calls only package_search and package_show, with GET. Every read is anonymous.

    Two notes for the flip → #77

    1. The template still emits MODEL_CATALOG_API. Commit .env.example and local-setup notes so ui-react runs for someone who is not Max #72 deleted that key from the app. The
      generator ignores unknown variables, so the extra key is harmless. Remove it when convenient.
    2. values.yaml and the fail in ui-react-config.yaml say the React client must differ from
      Lit's. Check whether the OAuth2 redirect URI for mint.tacc.utexas.edu is already registered #73 settled that this is wrong for this rollout. The fail triggers only on an
      empty client_id, so "mint" renders.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

wayfinder:taskWayfinder ticket: manual work that unblocks a decision

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions