Add an event to TSphinxConfig that traps a failed login where the outcome can be set in code. The outcomes could be
Handle normally
Convert to a change password request
Block - refer to sys admin
The second one would be very useful.
Add an event to TSphinxConfig that traps a failed login where the outcome can be set in code. The outcomes could be
Handle normally
Convert to a change password request
Block - refer to sys admin
The second one would be very useful.
I don't understand this request.
Currently, if user try to login too many times, his account is locked (this is configurable).
Also, at any time, if the user forgets or types wrong password, he can use the "forgot my password" mechanism, which allows him to change password.
You wouldn't believe the problems that some users have with that
I understand users can have all kind of problems, my question is how different this request is from what already exists, and how this doesn't qualify somehow as duplicated functionality.
The idea is based on the fact that we have converted from a legacy system where the encrypted password used a different scheme to that in Sphinx. Despite telling users that their password needed to be reset they continue to just keep typing in their old password.
However, I see this is too narrow a case and I have written a new, more general, feature request which is much more flexible in it's use cases.
So this has been marked as a solution.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.