Flipping the auth provider without logging everyone out
Changing identity providers is a one-way door if you get the order wrong. A checklist for cutting over with a live fallback and a real rollback.
Rhay ParraSoftware Developer and Architect
I design the system, write the decision record, and then write the code. Currently a senior architect at a US advocacy platform and founder of Loxben Apps, working remotely from Montevideo.
A few problems I've worked on recently — what was actually wrong, what it took, and what it cost.
At work I'm running two threads: a telephony voice-agent proof of concept on LiveKit and Twilio SIP, and the compliance layer under a document-upload feature — managed malware scanning, content moderation, and field-level encryption with KMS envelope keys. At Loxben, the Vendor Contract Analyzer is first out of the Finance Ops Hub.
The notes are where I write down what a decision cost and whether I'd make it again.
Changing identity providers is a one-way door if you get the order wrong. A checklist for cutting over with a live fallback and a real rollback.
In a chat-led app, some actions have to appear at the right moment every single time. That's not a job for tool calls. Here's the pattern we used instead.
Un pipeline en verde no significa que tu código está sirviendo. Cómo verificar de verdad que un cambio llegó a producción.