I don't get it, please explain

I can answer part of that. LTB has an option where users can pick a password and log in immediately but it places them in a special role which, unlike all normal roles (except anon) is not in addition to "authenticated". That is, they are in a limbo state of not anonymous but not authenticated either.

I'm interested in the rest of the question, though. If you don't want users to be able to log in while in this state, just don't choose that option in LTB. Why would you need another module for that?

Michelle

Tried to explain this in the referred issue:
#771020: Optionally disable login capability for pre-auth users

Note that you need to choose a different pre-auth role. If you don't choose one, no double opt in is possible with logintoboggan. Thus: no email verification will occur.
The pre-auth state is the intermediate in between registration and confirmation.

This module is compatible with everything i know of... We use it with logintoboggan and e.g. email_registration together.

You need this module if you want
- Being able to specify a password on login
- Have double opt in (email verification)
- Preventing users in pre-auth state from login (during email verification phase)

I hope that's it. Thanks for helping to provide a clean description of the modules' functionality.
I'll add this description to the project front once reviewed.

Ah, I see. That makes sense. Mea culpa for not reading the linked issue and jumping on this one. :)

Thanks,

Michelle

closing this, updating the module description.