Skip to content

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

Closed
hipwelljo opened this issue Sep 28, 2017 · 6 comments

Comments

@hipwelljo
Copy link

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!

@montymxb
Copy link
Contributor

@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.

@flovilmart
Copy link
Contributor

I believe the APNS node module supports token based auth, we’ll probably need to update the docs to reflect thatz

@hipwelljo
Copy link
Author

Confirmed this format works:

push: {
    ios: [
      {
        token: {
          key: path.join(__dirname, 'AuthKey_XXXXXXXXXX.p8'),
          keyId: "XXXXXXXXXX",
          teamId: "YYYYYYYYYY"
        },
        topic: 'com.domain.appname',
        production: false
      }
      //add for production: true...
   ]
}

@montymxb
Copy link
Contributor

montymxb commented Oct 15, 2017

@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.

@flovilmart
Copy link
Contributor

Docs have been merged, closing! Thanks for the PR!

@montymxb
Copy link
Contributor

Thanks again @hipwelljo !

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

3 participants