# Recreate identity paths before opening the new environment

A migrated application needs the right people and services to reach it with the right authority. Copying data and code does not recreate that access model.

By Cobnex editorial. Published 2026-09-10. Updated 2026-09-11.

## Trace a real sign-in

Test the intended identity provider, redirect path, session handling and role resolution from the target environment. Use representative user roles, including a user who should be denied access.

A successful administrator login is weak evidence for ordinary users. Administrators often bypass the policies most likely to be misconfigured.

Check links and callbacks that still point at the old environment. The application can load while authentication returns users to an obsolete endpoint.

## Rebuild service authority narrowly

Inventory the identities used for databases, storage, queues and external integrations. Map each to the operations the target service actually needs.

Avoid copying broad migration credentials into runtime configuration. Temporary authority used to transfer data should not become the permanent application's access model.

Verify secret availability and rotation ownership without displaying secret values in the run log. A reference to a missing secret can pass infrastructure deployment while failing at the first business request.

## Review copied and temporary data

Data may exist in staging buckets, replication services, exports and diagnostic snapshots during migration. Identify who can access each copy and how long it remains.

Keep target permissions appropriate before loading sensitive records, not only before opening the website. A private application does not protect a publicly accessible staging object.

Review tenant boundaries and administrative access using synthetic cross-tenant tests. Migration transformations can accidentally change ownership identifiers even when row counts match.

## Remove transitional access

After the observation period, revoke temporary grants and credentials according to the documented recovery needs. Do not remove access still required for an active recovery path without replacing that path.

Confirm that the old environment cannot resume independent writes through a forgotten service identity. Access control helps enforce the cutover's ownership decision.

Record the final runtime roles and the remaining temporary exceptions. The review should establish both that legitimate workflows work and that the migration has not left broader access than the service requires.

## Sources

- [OWASP: authorisation guidance](https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html)
- [AWS: creating migration runbooks](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-migration-playbook/task-two-drafts-runbooks.html)