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

Client push unavailable #396

Closed
rogerhu opened this issue Feb 13, 2016 · 7 comments
Closed

Client push unavailable #396

rogerhu opened this issue Feb 13, 2016 · 7 comments

Comments

@rogerhu
Copy link
Contributor

rogerhu commented Feb 13, 2016

After #311 got merged I started testing it again. I started seeing
"Master key is invalid, you should only use master key to send push'" on Parse push registrations.

I don't believe the Android SDK has the ability to send a master key ( (https://www.parse.com/questions/using-master-key-with-android). so I had to disable this line to get push notifications registered.

Is it possible to remove this validation until the Android/iOS SDK's enable this possibility?

@wangmengyan95

@rogerhu
Copy link
Contributor Author

rogerhu commented Feb 13, 2016

After disabling it, I was able to validate user and channel pushes though!

@wangmengyan95
Copy link
Contributor

Hi @rogerhu, as we said in wiki, we do not officially support client push yet. The main reason is related to security. Since you will distribute the app with your clientKey, malicious users can use that to send push notifications to your app users if you enable client push. For Parse.com, we have the dashboard to remind you and allow you to change this setting. It is disabled by default. For open parse server, we simply disable the client push at the beginning. Compared to client push, we always recommend developers to use cloud functions to send push notifications.
I will send a PR to allow you to enable client push when you initialize parse server later. Removing the checking does not have an effect on the push functionality, just be aware of the security issue I mention to you.

@rogerhu
Copy link
Contributor Author

rogerhu commented Feb 14, 2016

Yep makes sense thanks!

@gfosco gfosco changed the title validateMasterKey() call prevents Android SDK from registering for push notifications Client push unavailable Feb 14, 2016
@rogerhu
Copy link
Contributor Author

rogerhu commented Feb 17, 2016

Thanks again for the input...the security concerns are duly noted.

Wondering if there's a PR that you have? We have a bunch of group projects that are going to be spinning up hosted Parse so curious to see if we'll be able to get it so it can be supported.

Thanks!

@edwardyue
Copy link

I encountered the same too
[Error]: Master key is invalid, you should only use master key to send push (Code: 115, Version: 1.12.0)

Could you please send us the solution?

@gfosco
Copy link
Contributor

gfosco commented Feb 20, 2016

Are you trying to send a push from Android? We are not going to support that, you should call a cloud function and send the push from there.

If you're having a problem just registering for push, not sending, please re-open.

@gowridev
Copy link

gowridev commented May 6, 2016

How to send client push notifications for multiple users using cloud code? I am able push to single user with help of this link (I am unable to come up with Query for multiple users?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants