Server Openfire 3.5.0, clients Spark 2.5.8. Users and auth from MS AD.
In the server setting “Avatar/VCard - (Spark Only) Allow users to change their profiles and avatars” set to Disabled.
But look:
spark1.jpg - I click to my avatar and there is dialog of VCard data,
spark2.jpg - I wrote 2222 after my nickname,
spark3.jpg - I press OK and get error message,
spark4.jpg - I click to my avatar again and what ? how it saves 2222 ?
After relogon user’s VCard data again right data (imported from LDAP). But between “unsuccessfully” VCard changes and relogon user have changed nick in rooms and converstions. So user can hack room’s disabled setting “Allow Occupants to change nicknames”…
Spark can not change the vCard data of an LDAP user regardless of the settings in openfire. It will try and cache the change locally but will be over-written on each reload of spark. As for nicknames spark should not allow the change of nicknames in MUC rooms with that restricted. Are you saying that it does allow this?
Strange. I have tested this with Spark 2.5.8 right after Client Plugin was released. And it worked. Spark wasnt saving anything. And now i’m using Spark 2.6.0 (SVN version) and it saves changes easily without any error messages. Must be a bug in a 2.6.0 version.
Spark can not change the vCard data of an LDAP user regardless of the settings in openfire. It will try and cache the change locally but will be over-written on each reload of spark. As for nicknames spark should not allow the change of nicknames in MUC rooms with that restricted. Are you saying that it does allow this?
Yes. More screenshots:
spark5.jpg - I can’t change nickname in room (Allow Occupants to change nicknames - Disabled),
spark6.jpg - but after “unsuccessfully” VCard changes in room my nick is new (not from LDAP), and another users see that.
