DAN Gateway¶
Production · Layer 2 — Authentication ·
Repo: sso-gerege-mn (dan.gerege.mn/) · dan.gerege.mn
DAN is Mongolia's unified state identification system; this is the gateway that connects to it. It consists of a Go API plus a Next.js web front end.
What it does¶
Within the Gerege ecosystem, DAN is used for two purposes:
- KYC verification — when a citizen enrols in eID Mongolia, their civil-registry details are checked against DAN. A liveness check by facial recognition is layered on top.
- An identification gateway — a single interface for the flows that need the user identified through DAN.
Structure¶
| Part | Technology | Role |
|---|---|---|
api/ |
Go | Backend that talks to DAN; the verify / authorized flow |
web/ |
Next.js | Admin interface and test screens |
Main endpoints¶
| Path | Purpose |
|---|---|
/verify |
Start an identification request |
/authorized |
Receive the authorisation result |
/try |
Test flow |
/health |
Health check |
/admin |
Admin screens |
The paths that start identification and receive authorisation carry a strict rate limit at the edge (brute-force protection).
Who uses it¶
The DAN Gateway is an internal service — third-party applications do not call it directly. Its usual callers are:
- eID Mongolia — for KYC during enrolment,
- Gerege SSO — for the flows that require it.
DAN vs eID
Both are about "identification", but their roles differ. DAN checks a citizen against the state registry (KYC). eID issues that citizen cryptographic keys and certificates, which then let them sign in and produce signatures. To enrol in eID you must first be checked through DAN.
Full documentation¶
Implementation documentation lives in the dan.gerege.mn/ directory of the
sso-gerege-mn repository.