{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":35172,"path":"mobile/sg-push-setup-ios.md","title":"Configure push applications for iOS branded apps using certificate based authentication","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure push applications for iOS branded apps using certificate based authentication\n\nInstall an iOS push certificate to use push notifications on your branded ServiceNow mobile apps for iOS.\n\n## Before you begin\n\nRole required: admin\n\nTo use push notifications on your branded ServiceNow mobile apps for iOS, you must upload your Apple certificates p12 file, and enter your key store password into your instance.\n\n**Note:** These steps are not necessary if you are not using a custom branded mobile apps. For more detail on custom branding, see [Request, test, and publish a branded mobile app](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/request-test-pub-branded-mob-app.md).\n\n## Procedure\n\n1.  Navigate to **All** > **System Notification** > **Push** > **Push Application**.\n\n2.  Open the record for the push application you want to modify.\n\n    -   Open **ServiceNow Mobile Application** for the Mobile Agent app.\n    -   Open **ServiceNow Request Application** for the Now Mobile app.\n    If you are using a branded mobile application, select the record for the branded app. For example, select **ServiceNow Intune Mobile Application** if you are using the Microsoft Intune branded application.\n\n3.  In the **Push** field, change the value from **REST API** to **Direct**.\n\n4.  In the Apple-Certificate Based Authentication tab, click the reference icon \\(\\[Omitted image \"reference-lookup-icon.png\"\\] Alt text: Reference icon\\) next to the **Certificate** field.\n\n5.  In the X.509 Certificates list pop-up, click **New**.\n\n6.  In the X.509 Certificates form, fill in the fields.\n\n    |Field|Value|\n    |-----|-----|\n    |Name|Name for your certificate.|\n    |Notify on expiration|User to receive a notification when the certificate expires.|\n    |Type|Certificate type. Enter **PKCS12 Key Store** in this field.|\n    |Key store password|Your Apple key store password.|\n    |Warn in days to expire|Number of days before certificate expiration to receive an expiration warning.|\n    |Short Description|Description for your certificate.|\n\n7.  Click the attachment icon \\(\\[Omitted image \"attach-icon.png\"\\] Alt text: Attachment icon\\).\n\n8.  Upload your .p12 certificates file.\n\n    **Note:** Due to an Apple internal policy, all iOS push certificates \\(.p12 files\\) expire after 13 months. To continue using push notifications without disruption, you should request an updated build within 60 days of your certificate expiration date to receive a new .p12 file. New .p12 files cannot be generated without an updated or new build.\n\n9.  Click **Save**.\n\n10. Re-open your X.509 Certificates record and click the **Validate Stores/Certificates** link at the bottom of the form to validate your certificates and stores.\n\n11. On the push application form, click **Update**.\n\n\n**Parent Topic:**[Mobile push notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/sg-mobile-push-notifications.md)\n\n"}}