Re: [JDEV] unregister/remove

[Justin Georgeson]

xdb_file by default caches user data in memory. So until the user's data 
is removed from the cache [s]he will still be able to login. You can 
disable the cache by setting the timeout to 0. Other xdb backends (like 
xdb_sql, probably xdb_ldap) should have a more immediate realisation of 
the change.

David Rosenbloom wrote:
It appears that the jabberd  behavior allows login from users who
have unregistered via a /remove. So that:
- a user registers;
- same user unregisters (/remove with key);
- same user logs in later.
Login is permitted without re-registration.

So my questions are:
- Is this the desired /remove behavior?
- Must the client's datastore be rinsed so that they do not present the
old creds, in order to force re-registration?
thanks,
- davidr


_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
--
Justin Georgeson
UnBound Technologies, Inc.
http://www.unboundtech.com
Main   713.329.9330
Fax    713.460.4051
Mobile 512.789.1962
5295 Hollister Road
Houston, TX 77040
Real Applications using Real Wireless Intelligence(tm)
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev