Authentication

VijiHub supports two primary credentials against the Gateway:

  1. OIDC access tokens (Authorization Code + PKCE) — Console and user sessions
  2. API keys (vh_…) via X-Api-Key — customer backends and scoped browser clients

OIDC / JWT

Identity is hosted on the Gateway via OpenIddict.

ItemPath / value
Discovery/.well-known/openid-configuration
Authorize/connect/authorize
Token/connect/token
UserInfo/connect/userinfo
Login UI/auth/login
Register/auth/register

Flow: Authorization Code + PKCE (no password grant to the token endpoint).

  1. Client redirects to /connect/authorize.
  2. Unauthenticated users complete /auth/login (or register / external providers).
  3. Client exchanges the code at /connect/token.
  4. Call APIs with Authorization: Bearer <access_token>.

TypeScript helper: @vijihub/auth. .NET helper: VijiHub.Auth.

Seeded Console client (Development): vijihub-console with redirect http://localhost:5500/auth/callback.

Production issuer: https://console.vijitek.com/api/.

Platform APIs only accept access tokens whose audience is vijihub-api (console tokens with the api scope). Tokens issued to customer apps through Sign in with Vijitek carry the app's client ID as audience and are rejected by platform APIs.

API keys

Project API keys are created in the Console under the project. Send:

X-Api-Key: vh_...

Key scopes

ScopeTypical use
* / emptyFull server key — backends, admin APIs, Maps data, Storage admin, push send
analytics:ingestBrowser/server ingest for Analytics
crashlytics:ingestCrash report ingest
messaging:liveMessaging live / SignalR clients
notifications:registerDevice registration from browsers

Never embed an unrestricted full key in a public frontend bundle. Prefer scoped client keys or a BFF that holds the full key.

Dual-auth endpoints

Many project-scoped routes accept either a valid owner JWT or an API key with sufficient scope. Service pages document which auth mode each route requires.

Auth UI rate limits

Login, register, forgot-password, and reset-password POSTs use shared token-bucket rate limiting (vijihub.auth), partitioned by client IP.