Why can users still see people they shouldn't?
Is there a way to get rid of the custom "Contacts" group Pandion creates when it finds users in a person's roster that are no longer supposed to be visible to that person? I thought it was a server side problem, but I used a different client and was not able to reproduce my issue.
We recently made some changes to our shared group settings on our Openfire server and took the ability to see certain groups away from members of other groups. Afterwards, many of our users started to get a custom generated "Contacts" group showing up in their client rosters. Within this group are users that the person should no longer be able to see, but for some reason still can.
We recently made some changes to our shared group settings on our Openfire server and took the ability to see certain groups away from members of other groups. Afterwards, many of our users started to get a custom generated "Contacts" group showing up in their client rosters. Within this group are users that the person should no longer be able to see, but for some reason still can.
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?The Contacts group is simply the default group in which other users are ranked when there is no other label for them. This would mean that Openfire is still sending Pandion some kind of information about those unlabeled users. Otherwise it would not know about them at all.
In other clients, where do those contacts appear (if at all)? -
Most of the users are assigned to groups on the server. It is just that the group they are a member of may have had its visibility restricted. In Pandion, they show up in the proper group for users who are still allowed to see them, but end up in the Contacts group for users that should not. In Spark, its the same thing. If the group they are in is allowed to be seen by other users, it displays fine. For the users that should not see the group, they aren't showing up at all (which is what we want). What's most confusing for us is that some of the users populating the Contacts group no longer work here and have no user account on the Openfire server. Yet they appear in the roster. -
Most of the users are assigned to groups on the server. It is just that the group they are a member of may have had its visibility restricted. In Pandion, they show up in the proper group for users who are still allowed to see them, but end up in the Contacts group for users that should not. In Spark, if the group they are in is allowed to be seen by other users, it displays fine. For the users that should not see the group, they aren't showing up at all (which is what we want). What's most confusing for us is that some of the users populating the Contacts group no longer work here and have no user account on the Openfire server. Yet they appear in the roster.
As a side note, I posted this issue on the Openfire forums as well and they suggested it was a client problem merely due to the fact that I can't reproduce the issue with a different client. -
Inappropriate?Pandion, like most other XMPP clients, never stores roster contacts offline. So it can only be displaying in that "Contacts" group what the server sends it.
Those user accounts might have been removed from your Openfire server but they could still be existing as roster items in each of the other people's accounts. Just like removing an email account from the mail server doesn't take it out of everyone's address books.
So have a look in the Openfire admin panel or directly in the server's database to see if there are discrepancies in the contact list items. Or maybe in the shared groups, I'm not sure how Openfire implements those. -
Is there any way I can prevent Pandion from showing the group? We've been very successful in implementing a bunch of other mods over the past few years, so I was hoping there might be one for this.
If not, I can go on the server and individually remove each account from a user's roster. -
Inappropriate?I don't have any mod available for that particular task but a bit of scripting inside /src/main/ClientRoster.js would be able to remove the default Contacts group.
-
For lack of a better term, I am a scripting idiot. All of the mods we have made to Pandion have come directly from the Pandion forums. I took a look at ClientRoster.js, but I wouldn't know where to begin. If you could perhaps give me some insight? -
Inappropriate?I did some more looking around. Once we remove a user from the Openfire server, it is supposed to send an unsubscribe request to all of the clients. For some reason either the request is being sent, or Pandion is not getting it. I can manually remove the deleted users from everyone's rosters and then refreshs the cache on the server, but it is certainly not fun doing it this way. Is there a chance that the change to XMPPonPresence.js to prevent the "User has removed you from their contact list" error is also preventing the real unsubscribe requests from getting through?
I’m confused.
-
Inappropriate?Does Openfire send "unsubscribe" or "unsubscribed" presence packets?
- unsubscribe: Pandion 2.5 used to show an alert but that's it. In Pandion 2.6 the alert doesn't even appear anymore.
- unsubscribed:
a) If the roster item was previously still with the "ask" flag then it will be removed from the list and an alert will tell the user that the contact most likely does not exist. This is usually when adding contacts but entering the wrong JID.
b) If the roster item was not with the ask flag then nothing is done to remove the item from the roster. It could be someone blocked you or removed you from their list.
Loading Profile...



EMPLOYEE