Thank you for the response, but no. The user logged in is Userx. The stored procedure executes as UserX. Not exactly the same situation

I can create this scenario, when I log in as myself and use execute as.