Marco

Thanks! First of all, this library is intended to “just work”, so you shouldn’t have to worry about any of these time limits, validity periods and throttling mechanisms. But, of...

Thank you! Do you want this (a) for security reasons, (b) for UX reasons or (c) for storage efficiency reasons? In other words: Why do you want to achieve the...

Thanks! That behavior is currently the same for email changes and password resets, both when you request a new one already while the old one might still be “on its...

Thank you! Let’s keep this issue open, though, because I’m not really sure yet which solution we should prefer.

Good question! The fact that your `username` column is empty means that you didn’t collect and store a username during registration, right? If you want to let users change (or...

Thanks for trying this and for your feedback! We will definitely add this feature to the library soon.

> Registration by the user then classic procedure. Works, obviously. > I have email and I want create an account with email verification with a password random that will be...

Regarding your first problem, is sending *two* emails within a *short period of time* not enough? How many attempts to you want to make? You have one email sent after...

So it’s really only the case without an initial email address that’s still unclear, right? That is, the following scenario: > You use `Auth#register` or `Auth#registerWithUniqueUsername` as usual, but instead...

> When an Admin login as user happen a switch account ? I mean there is an logout as Admin and a login as User ? when the admin AS...