Replies: 1 comment 1 reply
-
If you are requiring login configuration and password configuration, and the confirmation values do not match, those are treated as errors well before anything is saved to the database or the session is updated. Hard to know what is going wrong in your application, but you would at least need to post a self-contained minimal example. Most import would be your Rodauth configuration. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I added a custom page for create_account as follows:
I then removed the
login-confirm
andpassword-confirm
inputs because they were slowing me down. I did this as follows:Using this custom create_account page, I found that I could "create" an account that never made it into the database. I was logged in as the new account and my site worked fine, but the account never made it in to postgres. After I logged out, I was no longer able to log in as this new account (because it never made it into the database) but I could "create" it on demand.
I was unable to see any errors or failures reported when I did this.
Restoring the
login-confirm
andpassword-confirm
inputs fixed the problem, but I think this could have interesting possibilities if a user can create a session with an account that is never persisted?Beta Was this translation helpful? Give feedback.
All reactions