This wasn't a bug but a misconfiguration on the instance. As mentioned in the comments, for this to work it's necessary to have a compatible verification configured. See documentation for Impersonations.