Hello
I've this behaviour too... Seems to be a bug, it has been reported in other posts in the forum...
My workaround at the moment: set authenticate to 0, put a link to 'First identification on the site' on my confirmRegister page... In the "First identification page" a basic Login call....
Not ideal but it works...
Cheers