In production, a developer can impersonate a user (for example, to help reproduce a bug) but must first enter a reason. In a development environment this reason request is skipped since no real users are involved.
When exiting impersonation in production, the developer password is required, to ensure that it is really the developer exiting the impersonation before giving back developer level access. In a development environment this seems unnecessary. Could the password check be skipped in development in the same way that the initial reason is skipped in development?
In production, a developer can impersonate a user (for example, to help reproduce a bug) but must first enter a reason. In a development environment this reason request is skipped since no real users are involved.
When exiting impersonation in production, the developer password is required, to ensure that it is really the developer exiting the impersonation before giving back developer level access. In a development environment this seems unnecessary. Could the password check be skipped in development in the same way that the initial reason is skipped in development?