-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/01/2014 21:15, Leho Kraav wrote: >> Maybe it's a stale bug status, but logging in with multiple resources >> on a single account most *definitely* works on OpenFire - I use it all >> the time on my 3.8.2 install, no issues. It even nicely lists the >> different resource connections in the web based admin interface when >> calling up session details, so I'm not sure what would not be working >> there. > > It doesn't work for MUC-s, where previous resources simply get kicked > out. If you browse around the bug links (duplicates, archived) you'll see > specific code was introduced to do this. >
There is a (configurable!) option to kick users if there is a resource conflict (always, never, allow 1 grace connection, or assign a kick value), meaning if you try to log in using the *same* resource on the same account. By default this is set to kick the old resource. If you are using a different resource however, you can have plenty of connections on the same account with different resources. That being said, I have my server configured to allow a single grace connection in case of a (jid+resource) conflict, so maybe that works around the MUC issue linked to? Whatever it may be: no issues for me that I can find. I do hope Prosody is worth losing your admin interface - personally, I'd be hard pressed to go back to config file editing in a text editor. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) iQEcBAEBAgAGBQJSycbhAAoJEKxqDlWrbd26WagH/js6kxBJO0iJsVYLuhwMZBFG OTcaznx6B/W6+YbRcCQ1iy/HlcuSoBQU9tCnDSu+QjBWM/Ov6/9lG/9+bLT/VkWz c/oV1BDFLZ8TL+HwAdgHWKb7SsZMI2PufzuXLsDz8dqrzBZUrVfyRygjFUbUWOBJ BiqZSG/9ys8yj3vfG44nrLFksbozRu4J/PZ/WuCQdOx2AI36b0RxRH/OTWsAl+dt q3B+ejd4zy3zy1kLzAUp4qI2BQS1ZDaFusFGg2Xv0xcDXWisLB34AtVrRksXixVM KLAejz417wPL7MbFfmIVtCn5DQOb4HLO+KGJt6dnvD6FQgNXnBS2TgCfEhioWJ0= =dpk5 -----END PGP SIGNATURE-----
