I run the admin page of my anonymous chat as a container on a Raspberry Pi, and made it reachable from outside with Cloudflare Tunnel and Cloudflare Access. Login is handed to Google over OIDC, and Rails validates the JWT it receives and returns 403 if it does not check out. Using the terms from my earlier OAuth and OIDC posts, this post sorts out who plays which role and follows how it works.
Yosuke Ueki
I am a software engineer based in Tokyo (JST, UTC+9). I design and build APIs with Python and TypeScript, and take projects end to end — requirements, design, implementation, testing, operations, and maintenance. I also work independently across AWS and Docker infrastructure and CI/CD, React / Vue front-end development, and LLM integration. See About for my background, and Work for past projects.
MISCI recently released an anonymous chat app. → anonymtopic
RECENT POSTS
Over a long weekend, I took apart a PC I built ten years ago and numbered the connectors on its motherboard, an ASRock H270 Pro4. Using photos of the real board, this post goes through where the power supply, CPU, memory, storage, graphics card and fans plug in, and what the parts around the CPU do.
OAuth decides what an app may do, but it does not tell the app who logged in. That is the job of OpenID Connect (OIDC). Using the authorization code flow and PKCE from the previous posts, this post shows with diagrams what OIDC adds, including what goes into an ID token and how to validate it.
Operations and maintenance, the phase that comes after development, has a reputation for cleaning up other people's bugs and doing routine work that never makes you better at engineering. Looking back on my own time doing ops and maintenance as a new grad with zero technical skill, I lay out what I would do if I could start over, and what you can only really learn in ops.
For project enquiries, please review the terms on Work, then get in touch via About.