Telegram verification
JWKS, issuer, audience, signing algorithm, and expiration are verified on the server.
OPENID CONNECT BACKEND
The server verifies the Telegram ID token signature, persists the user in SQLite, and issues its own revocable session.
JWKS, issuer, audience, signing algorithm, and expiration are verified on the server.
Subsequent sign-ins find the same user by the stable Telegram sub.
SQLite stores only the SHA-256 token hash; sessions expire and can be revoked.
API
The Android app sends the ID token only after completing the native Telegram Login flow.
POST /auth/telegramRegistration or sign-inGET /auth/sessionValidate the current sessionDELETE /auth/sessionSecure sign-outGET /api/health/readyReadiness for Docker and reverse proxies