Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Push notification settings not working as expected / privacy issue #17135

Closed
rcadmin19 opened this issue Apr 2, 2020 · 5 comments · Fixed by #19247
Closed

Push notification settings not working as expected / privacy issue #17135

rcadmin19 opened this issue Apr 2, 2020 · 5 comments · Fixed by #19247
Labels
feat: notification stat: triaged Issue reviewed and properly tagged type: bug

Comments

@rcadmin19
Copy link

Description:

We analyzed at server side the push notification content which is sent when options:
"Show Channel/Group/Username in Notification" and "Show Message in Notification" are disabled.
We noticed that even if those are disabled, sender, receiver and channel name is sent. Documentation (https://rocket.chat/docs/administrator-guides/notifications/push-notifications/) says that "Show Channel/Group/Username in Notification: Default is “TRUE”, disabling this setting prevents the Channel, Group, Discussion and Username being sent to the push notification gateway"

Steps to reproduce:

  1. Administration/Push/Privacy: Disable "Show Channel/Group/Username in Notification" and "Show Message in Notification". Reboot server.
  2. Rocket.Chat populates the "config" variable with a message before sending push notification so we printed "config" variable to console.log(config) and then got the information what was sent.

Expected behavior:

Push notification should not contain channel/group/usernames in notification content with these settings.

Actual behavior:

Push notification message contained all of these information:

{
from: 'push',
badge: 3,
sound: 'default',
priority: 10,
title: '',
text: ' ',
payload: {
host: 'https://rocketchatservername',
rid: 'xxxxxxxxxxxxxx',
sender: {
_id: 'xxxxxxxxxxxxxx',
username: 'myuser',
name: 'My User'
},
type: 'p',
name: 'Myprivatechannel',
messageType: undefined,
messageId: 'xxxxxxxxxxxxxx'
},
query: { userId: 'xxxxxxxxxxxxxx' },
notId: -1111111111111,
gcm: {
style: 'inbox',
summaryText: '%n% new messages',
image: 'https://rocketchatservername/images/logo/android-chrome-192x192.png'
},
apn: { category: 'MESSAGE' }
}

Server Setup Information:

  • Version of Rocket.Chat Server: 3.0.4
  • Operating System: Centos
  • Deployment Method: tar
  • Number of Running Instances:
  • DB Replicaset Oplog:
  • NodeJS Version: v12.14.1
  • MongoDB Version: 4.0.16
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stat: stale Stale issues will be automatically closed if no activity label Jun 19, 2020
@sampaiodiego
Copy link
Member

duplicated of #17135

@JoshMcCullough
Copy link
Contributor

Working correctly in 3.1.1.

@vplb
Copy link

vplb commented Sep 2, 2020

It is still affecting us in 3.5.0
The buttons do not change anything. Tried resetting buttons to on, restarting, setting to off, and restarting, the push notifications are still populated with user information.

@rcadmin19
Copy link
Author

vplb: I can confirm this. It's still sending user and room names on version 3.5.2. This case should be re-opened.

@sampaiodiego sampaiodiego reopened this Oct 14, 2020
@sampaiodiego sampaiodiego added type: bug Triaged and removed stat: stale Stale issues will be automatically closed if no activity labels Oct 14, 2020
@tassoevan tassoevan added stat: triaged Issue reviewed and properly tagged and removed Triaged labels Oct 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat: notification stat: triaged Issue reviewed and properly tagged type: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants