That is not intentional, I'll try to look at it soon. I'm probably calling the wrong proc to get the user id or something like that, now that we have trusted user id vs. non-trusted etc etc.
It is still hawk migration season, I'm planning to be out in the field part of next week, so if you want to track down where the login request is being triggered, feel free to do so.
