At jabber.org (running jabberd 1.4.2cvs plus patches, it's a long story, don't ask), I see the following behavior with regard to password changes:
1. Log in with pw1, change password to pw2 (confirmed as changed in database), log out, successfully log in with pw2. All is happy. 2. Log in with pw1 as resource1, log in with pw1 as resource2, change password to pw2 from resource2 (confirmed as changed in database), log out of resource2, leave resource1 logged in, try to log in with pw2 as resource2, get 401 error (but can successfully log in with pw1 as resource2). Once I log out of resource1 (no more connected resources), I am then able to successfully log in with pw2. So it seems that there is some kind of session caching happening, even though pgmillard confirms that we have all xdb caching turned off. Is there a way to configure jabberd 1.4 to not cache anything, do we need to finally and definitively upgrade to 1.4.3, or is this a bug? Thanks! /psa _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
