Portal identity deserves a target model

Many Edge portals accumulated users through built-in registration flows. Those users may include active partner developers, old test accounts, personal email addresses, and users who no longer represent a valid consumer organization. Migrating them blindly can reproduce the weakest part of the old model.

External identity provider pattern

Use migration to establish an external identity provider for portal authentication. Map active users to verified identities, require domain or partner validation, and define lifecycle rules for joiner, mover, and leaver events. Account migration should include communication, reset flow, and support readiness.

Execution steps

  • Export portal users and app ownership relationships.
  • Classify users as active, invite, archive, or exception.
  • Federate portal access with the external provider.
  • Validate app ownership visibility after login.

The target portal should improve identity assurance, not merely preserve access.