Portal Request Lifecycle - Login to DNO

Portal Request Lifecycle - Login to DNO A sequence diagram generated by Archify. GET portal-xx response serves the SPA static bundle login -> SSO redirect callback + profile session cookie session row in Portal MySQL GET views + permissions tenant views, role keys permission set keys -> sidebar (OR) GET /comFooExpSvc/v1/xxx proxy + service token routes.json literal key; any listed permission passes 200 data 200 JSON -> render Login Boot + menu Feature call Browser · operator staff, Vue SPA · Sequence participant Browser operator staff, Vue SPA portalBackend · Express BFF · Sequence participant portalBackend Express BFF SSO IdP · Okta / Azure AD · Sequence participant SSO IdP Okta / Azure AD Portal MySQL · sessions, views, roles · Sequence participant Portal MySQL sessions, views, roles DNO Service · one of ~115 · Sequence participant DNO Service one of ~115 Legend request return security default message

Four independent gates

  • • Tenant view enabled, role has the key
  • • Sidebar + route guard: isUserAllowed, OR over keys
  • • Proxy route re-checks; UI passing never implies API passing

Literal routes

  • • routes.json keys match exact URL strings, no /:id
  • • Dynamic ids travel as ?id= and are spliced upstream
  • • Both sides must be wired or the call 404s

What lives where

  • • Session + permission truth: Portal MySQL
  • • Business data: only in DNO services
  • • Upstream calls ride a service token, not the user token
← Docs home