My-IT.uz
One identity for an entire ecosystem.
In plain words
- What it is
- One account to sign in to many sites and services — like “Sign in with Google”, but for its own family of products.
- Who it’s for
- People who use PayX, ORAX, Telegroup, LinkJob, the library, the chess game and other services — and developers who want this login on their own site.
- What it gives
- No new password for every site. One place shows which devices are signed in and which apps have access — and any of it can be switched off.
My-IT is an identity and access platform: one account that signs users into many applications through OAuth 2.0. It gives users control over their security, devices and privacy, and gives developers a portal to register and manage applications. Today it is the sign-in of PayX, ORAX, Telegroup, ITProduct, LinkJob, the Business Catalog, Amir Temur Chess, the library and Musiqiy.
Business context
Payments, hosting, jobs, a marketplace, a library and a game all needed sign-in. Building a login into each would repeat the same security work again and again.
The problem
When every product implements its own login, users juggle passwords, security practices drift between systems and there is no single place to see sessions, devices or granted access.
The solution
An authorization server built on Laravel Passport: the OAuth 2.0 authorization code flow with PKCE support, scoped access to profile data and one security center where users manage devices, sessions, activity and consents.
What I built
Built alone — architecture, code and production. No other developers worked on it.
Architecture
- One authorization server for the whole ecosystem
- A client registry with admin approval and “official” apps
- A scope model: profile, email, phone, passport status, trust and business scopes
Backend
- OAuth 2.0 on Laravel Passport: authorization code flow, token endpoint, /api/me
- PKCE support through code_challenge
- Developer API: client registration, secret rotation, suspend/resume, insights
Frontend & apps
- Vue 3 account center and developer portal
- Consent screen
- Popup SDK (MYIT.signIn) with response_mode=web_message
APIs & integrations
- 9 services sign in with My-IT
- A public catalog of connected apps with their scopes
Database
- MySQL: users, clients, tokens, consents
- Passport verification exposed only as a yes/no status
Security
- 2FA, passkeys (WebAuthn) and recovery codes
- Sessions and trusted devices, a security checkup, risk and incident alerts
- An audit log with integrity verification; data export and account deletion
Delivery & operations
- Runs in production as the sign-in of every service in the ecosystem
Engineering deep dive: Sign in with MyIT — authorization code flow
- The user clicks “Sign in with MyIT” in a connected app.
- The app sends the user to /oauth/authorize with its client_id, scopes, a state value and, optionally, a PKCE code_challenge.
- My-IT authenticates the user — with 2FA or a passkey if enabled — and shows the consent screen.
- The user approves the requested scopes.
- My-IT redirects back to the app with a one-time authorization code.
- The app’s backend exchanges the code at /oauth/token, authenticating with its client secret.
- It receives a Bearer access token.
- The app calls /api/me with the token.
- My-IT returns only the fields the approved scopes allow — profile, email, phone.
Technical decisions & trade-offs
- One authorization server, many clients — Every service delegates sign-in to My-IT instead of storing passwords itself. (Trade-off: The ecosystem depends on one service — in return, 2FA, passkeys and session revocation are built once.)
- Scopes per kind of data — Apps ask only for what they need: profile, email, phone, passport status, trust or business scopes. (Trade-off: More consent screens to design — and users see exactly what each app receives.)
- Verification as a status, not a document — The passport scope tells an app only whether the identity is verified. (Trade-off: Apps get less detail, by design.)
- A popup SDK — MYIT.signIn opens sign-in in a popup and returns the result with response_mode=web_message, so the app keeps its state. (Trade-off: Popups can be blocked; the standard redirect flow stays available.)
Core modules
- Single Sign-On
- OAuth 2.0 authorization
- PKCE support
- Scopes & consents
- Developer portal
- Client approval
- Digital identity
- Security center: 2FA, passkeys
- Devices & sessions
- Audit log
- Data export & deletion
my-it.uz
Boburbek