Objective
To modernize the Zendesk SDK integration by allowing administrators to upload .p8 (Token-based) files for iOS push notifications, replacing the restrictive and high-maintenance .p12 (Certificate-based) method.
Problem Statement
Currently, Zendesk Messaging for mobile requires .p12 certificates. For organizations managing multiple products (Product 1 through 4), this creates:
- High Operational Overhead: Certificates expire every 13 months, requiring manual rotation and risking downtime if missed.
- Scalability Friction: Each product requires its own specific certificate, increasing the surface area for configuration errors.
- Security Rigidity: Unlike .p8 keys, .p12 certificates are tied to specific App IDs, preventing a streamlined "one-key-to-rule-them-all" approach for a suite of apps.
Proposed Solution
Update the Admin Center > Channels > Messaging configuration to include a "Token-based (p8)" upload option. Fields should include:
- Key ID: The 10-character unique identifier for the .p8 key.
- Team ID: The Apple Developer Team ID.
- App Bundle ID: The specific identifier for the product app.
Use Case Scenario: The Multi-Product Scaling
The Profile
- Company: A multi-vertical SaaS provider supporting four distinct mobile applications (Product 1, 2, 3, and 4) under a single Zendesk instance.
- Support Goal: Maintaining 99.9% uptime for proactive messaging and real-time support notifications across all platforms.
The Conflict
The Engineering team has shifted all internal services to Appleās token-based authentication. However, because Zendesk Messaging only supports .p12, the DevOps team is forced to maintain a "legacy" pipeline specifically for the Zendesk integration.
The Impact of No Change
- The "Blackout" Risk: If the .p12 for Product 3 expires and the Admin is OOO, customers stop receiving push notifications. The conversation dies, CSAT drops, and the "Messaging" channel becomes a liability.
- Maintenance Debt: With four products, the team is performing manual certificate rotations every quarter. This is 4x the work, 4x the documentation, and 4x the chance for a mismatch between the production and sandbox environments.
- Authentication Conflict: Running .p12 for Zendesk while the rest of the app's infrastructure uses .p8 creates technical debt and complicates the handshake between the Apple Push Notification service (APNs) and the Zendesk SDK.
The Desired Outcome
By implementing .p8 support, the company uploads one key to Zendesk that covers all four products. This key never expires, requires zero annual maintenance, and ensures that the support experience is as modern as the products being supported.
