One Hoberg account for Maji and every authorized Hoberg application.
Hoberg ID is our dedicated identity provider. Register using your existing Gmail, Outlook, or work email address and set a separate Hoberg password—no Google sign-in is required. Sign in once at account.hoberg.com.ng and use “Continue with Hoberg” across connected products.
Works with @gmail.com, @outlook.com, or any valid domain using a separate Hoberg password.
You review and approve exact scopes (openid, profile, email) before any app receives data.
Continue with Hoberg
OAuth 2.1 + PKCE (S256) • OIDC 1.0
How Maji & Ecosystem Sign-In Works
- 1You select “Continue with Hoberg” inside Maji.
- 2Maji redirects you to account.hoberg.com.ng/oauth/authorize with a PKCE S256 code challenge.
- 3You sign in with your Hoberg password and review the requested scopes on the consent screen.
- 4Hoberg ID returns a single-use authorization code only to Maji's registered callback URL.
Identity Architecture & Security Principles
Built around explicit verification boundaries, least-privilege scopes, and user-controlled data governance.
Inbox Verification vs. Legal Identity
Email verification proves inbox access via a cryptographic one-time token. Self-reported profile fields are explicitly labeled as such.
Dedicated Hoberg Credentials
Register with any valid email provider without relying on third-party social login providers for registration, sign-in, or recovery.
OAuth 2.1 + PKCE & RS256 JWKS
Enforces exact callback URI matching, S256 code challenges, single-use authorization codes, and asymmetric RS256 token verification.
Row Level Security & Portability
PostgreSQL RLS isolates user data at the database layer. Users can revoke app permissions, export data, or delete their account at any time.