2b3704761a
Customers no longer authenticate with passwords. A POST to the hub's
/portal/request-link mints a 24h customer-scoped JWT and sends it via
email + SMS; the /#/login Vue page sits on top of this and a navigation
guard hydrates the Pinia store from the token on arrival.
Why now: legacy customer passwords are unsalted MD5 from the old PHP
system. Migrating hashes to PBKDF2 would still require a forced reset
for every customer, so it's simpler to drop passwords entirely. The
earlier Authentik forwardAuth attempt was already disabled on
client.gigafibre.ca; this removes the last vestige of ERPNext's
password form from the customer-facing path.
Hub changes:
- services/targo-hub/lib/portal-auth.js (new) — POST /portal/request-link
• 3-requests / 15-min per identifier rate limit (in-memory Map + timer)
• Lookup by email (email_id + email_billing), customer id (legacy +
direct name), or phone (cell + tel_home)
• Anti-enumeration: always 200 OK with redacted contact hint
• Email template with CTA button + raw URL fallback; SMS short form
- services/targo-hub/server.js — mount the new /portal/* router
Client changes:
- apps/client/src/pages/LoginPage.vue (new) — standalone full-page,
single identifier input, success chips, rate-limit banner
- apps/client/src/api/auth-portal.js (new) — thin fetch wrapper
- apps/client/src/stores/customer.js — hydrateFromToken() sync decoder,
stripTokenFromUrl (history.replaceState), init() silent Authentik
fallback preserved for staff impersonation
- apps/client/src/router/index.js — PUBLIC_ROUTES allowlist + guard
that hydrates from URL token before redirecting
- apps/client/src/api/auth.js — logout() clears store + bounces to
/#/login (no more Authentik redirect); 401 in authFetch is warn-only
- apps/client/src/composables/useMagicToken.js — thin read-through to
the store (no more independent decoding)
- PaymentSuccess/Cancel/CardAdded pages — goToLogin() uses router,
not window.location to id.gigafibre.ca
Infra:
- apps/portal/traefik-client-portal.yml — block /login and
/update-password on client.gigafibre.ca, redirect to /#/login.
Any stale bookmark or external link lands on the Vue page, not
ERPNext's password form.
Docs:
- docs/roadmap.md — Phase 4 checkbox flipped; MD5 migration item retired
- docs/features/billing-payments.md — replace MD5 reset note with
magic-link explainer
Online appointment booking (Plan B from the same discussion) is queued
for a follow-up session; this commit is Plan A only.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
32 lines
1.2 KiB
JavaScript
32 lines
1.2 KiB
JavaScript
/**
|
|
* Magic link helper for payment-return pages.
|
|
*
|
|
* The customer store now owns all token decoding (see stores/customer.js:
|
|
* `hydrateFromToken`). This composable is a thin read-through so the
|
|
* payment pages can render `v-if="auth.authenticated"` without caring
|
|
* about where the session came from (magic-link URL vs. existing nav).
|
|
*
|
|
* The router guard already calls `store.hydrateFromToken()` before these
|
|
* pages mount, so by the time this runs the store is either hydrated or
|
|
* still empty — no extra decoding needed here.
|
|
*/
|
|
import { useRoute } from 'vue-router'
|
|
import { useCustomerStore } from 'src/stores/customer'
|
|
|
|
export function useMagicToken () {
|
|
const route = useRoute()
|
|
const store = useCustomerStore()
|
|
|
|
// `expired` is a hint for the UI: "you arrived here with a token but we
|
|
// couldn't use it". Approximated by: URL had a token (route.query or the
|
|
// raw hash) but the store is still empty.
|
|
const urlHadToken =
|
|
!!route.query.token ||
|
|
(typeof window !== 'undefined' && window.location.hash.includes('token='))
|
|
|
|
const authenticated = !!store.customerId
|
|
const expired = urlHadToken && !authenticated
|
|
|
|
return { authenticated, expired, customerId: store.customerId }
|
|
}
|