Parse-server: Update Parse Server Guide for token based authentication for push notifications

Created on 28 Sep 2017  路  6Comments  路  Source: parse-community/parse-server

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!

All 6 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鈥檒l probably need to update the docs to reflect thatz

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...
   ]
}

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

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jiawenzhang picture jiawenzhang  路  4Comments

sanergulec picture sanergulec  路  4Comments

omyen picture omyen  路  3Comments

carjo422 picture carjo422  路  3Comments

dcdspace picture dcdspace  路  3Comments