Menu

Email Change Migration: How to Preserve Proof and Notify the Old Address
📰

Email Change Migration: How to Preserve Proof and Notify the Old Address

DEV Community: authentication·AshtonBlake6879·about 1 hour ago
#1NK1Hx1V
#devtoauthentication#devto#dev#email#account
Reading 0:00
15s threshold

Migrate a B2B SaaS email-change flow only when the replacement preserves proof of the new address, notification to the old address, and a separate path for containing a stolen session. An account update alone does not establish that boundary.

TL;DR: Start the change, send confirmation to the new address, notify the old address, and complete the change on confirmation. Then re-verify the account state before refreshing downstream caches. Keep refresh-token rotation and session revocation as explicit security decisions; a successful email change is not evidence that either occurred.

This architecture decision record evaluates migration off a managed identity provider through the evidence the application must retain. Infrai offers a single key and one bill through a unified REST API, with no SDK required. For an identity-and-notification handoff, that means fewer credentials and integration contracts to operate; public discovery schemas also help review the adapter.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.