SMF single sign-on for our aMember installation works fine initially, but it fails after a users changes their password. Can anyone help figure out why this is happening?
This makes sense if they are changing their password within SMF as there is no way for SMF to hook into the amember database and change the password there too. But... if the user changes their password in their amember profile I would expect the SMF plugin to update the SMF database. I'm currently trying to get the SMF plugin to *work*. If I can figure that out (currently member accounts are not being created in SMF) I'll look at this for you.