-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Update Parse Server Guide for token based authentication for push notifications #4215
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
Comments
@hipwelljo I took a look and it looks like you're referring to this section. @flovilmart I'm not 100% on whether this is the case, I haven't been using push personally. Is this something that has in fact changed? If so we can close this out and open a relevant issue in the docs instead, following up with a PR when we have some time. |
I believe the APNS node module supports token based auth, we’ll probably need to update the docs to reflect thatz |
Confirmed this format works:
|
@hipwelljo if you have a moment can you open up a PR with the relevant changes added? The corrected text would go about here in the docs repo. |
Docs have been merged, closing! Thanks for the PR! |
Thanks again @hipwelljo ! |
Issue Description
The Parse Server Guide in the Push Notifications section states "Token-based authentication instead of a certificate is not supported yet." But this is no longer true, authorization token support was added into the push adapter earlier this year (looking at this pull request). If this would be updated and the config option examples added for that approach, that would be great!
The text was updated successfully, but these errors were encountered: