BackendAPIDevOps

STEKOM Passport

An OpenID Connect provider for the whole campus. One login for every internal app, with typed SDKs for TypeScript, Python and PHP.

Client
Universitas STEKOM
Year
2026
STEKOM Passport — main screen
11+ AppsSSO ecosystem
3 SDKsTypeScript, Python, PHP

The problem

Every new internal system came with its own user table and its own password reset. When someone left, their accounts were scattered across apps nobody remembered.

What I did

Authorization Code with PKCE, ID-token verification, and both RP-initiated and back-channel logout, so logging out once really ends the session everywhere. The SDKs mean another team can plug in an existing app in an afternoon.

Stack

NestJS 11BunReact 19PostgreSQLRedisSocket.IO

More case studies

ENDContact

Want something like this built?

Hiring for a remote role, or have a system that needs untangling? My inbox is open.