Parse-server: Push documentation update regarding .p12 file password

Created on 24 May 2016  路  2Comments  路  Source: parse-community/parse-server

The documentation should be updated to make it clear that your .p12 files should not have a password. parse-server does not handle .p12 files that use a password. By default, Apple keychain access will prompt you to set a password on your .p12 file when you export it. You should leave the password blank when you export your push certificates to .p12 files.

If your .p12 file has a password set, you will see the following error in your nodejs.log:

Error: mac verify failure

Most helpful comment

The default push adapter uses node-apn. While it is not formally documented anywhere, you can set the .p12 password in your Parse Server push configuration by setting the passphrase key.

push: {
  android: { ... },
  ios: [{
    pfx: __dirname + "/production.p12",
    bundleId: 'com.some.appname',
    passphrase: 'password-here',
    production: true
  }, {
    pfx: __dirname + "/dev.p12",
    bundleId: 'com.some.appname',
    passphrase: 'password-here',
    production: false
  }]
}

All 2 comments

The default push adapter uses node-apn. While it is not formally documented anywhere, you can set the .p12 password in your Parse Server push configuration by setting the passphrase key.

push: {
  android: { ... },
  ios: [{
    pfx: __dirname + "/production.p12",
    bundleId: 'com.some.appname',
    passphrase: 'password-here',
    production: true
  }, {
    pfx: __dirname + "/dev.p12",
    bundleId: 'com.some.appname',
    passphrase: 'password-here',
    production: false
  }]
}

@JeremyPlease I updated the docs here: https://github.com/ParsePlatform/parse-server/wiki/Push#2-configure-parse-server

Was this page helpful?
0 / 5 - 0 ratings