The last time I had a requirement to allow users to change passwords in the browser it was the R5 days. Back then it was still a case of us building a front-end to an agent that updated the HTTPPassword field in the user's NAB entry. The trouble with this approach being that it was anybody's guess when the change would take effect.
Web users, quite rightly, expect the change password feature to work in the same way on any site and on most sites it does. On Domino sites it's not as easy, but it seems to be getting there. The need for a change password feature has come my way again. This time it's Domino 6.5. How have things changed? Let's see.
My initial tests with the change password form show that it works, but in an odd way. The new and old passwords both work. You can log in with either. Also, if you want to change password again, straightaway, it's the old one you need to put in the change password form. Confusion ahoy.
I wanted to achieve all of this using standard (or maybe slightly tweaked) Domino forms and features. Instead it's starting to look more likely that still, all these years on, I need to write my own code to do it all. Surely I'm not the first person who has needed to achieve this (basic!) functionality. Anybody?