Skip to content
English - United States
  • There are no suggestions because the search field is empty.

Step-by-Step Guide for Federated Apple ID Setup with SnippetSentry

Step 1: Schedule an Initial Call with SnippetSentry Engineering

  • Objective: Assess if development work will be needed for federated Apple ID compatibility with iMessage.
  • Action: Schedule a 15-minute Zoom call with the SnippetSentry Engineering team and the customer. During this call, the customer should log in to iMessage with the exact same flow as the end-users will have, allowing SnippetSentry’s team to observe the login screen.
  • Outcome: This call helps determine if specific development work is necessary to integrate iMessage with the customer’s federated Apple IDs.

Step 2: Provide Test Logins for Evaluation

  • Context: SnippetSentry will require test login credentials, which will allow SnippetSentry to replicate the iMessage login process exactly as it functions for the customer.
  • Action:
    • The customer should record their iMessage login process, ensuring they capture any "unhappy paths" (such as incorrect password entry or multi-step verifications) that users may encounter.
    • Create test accounts with restricted permissions for SnippetSentry team members Anish Sahu and Jeremy Elwood. These accounts should have minimal access, limited only to what is required to sign into iMessage
      • Contacts for Test Accounts:
        • Anish Sahu - anishs@snippetsentry.com, +917005824802
          • *please note that this is an international number for an employee based out of India. Please allow permissions, as needed.
        • Jeremy Elwood - jeremy.elwood@snippetsentry.com, +19714388717

Step 3: SnippetSentry Evaluation of Federated Login Flow

  • Objective: SnippetSentry Engineering will use the test accounts to evaluate and verify the federated login process.
  • Outcome: After a thorough review, SnippetSentry will determine if the process requires additional development to support the customer’s federated Apple ID setup.

Step 4: Development Timeline and Implementation

  • Standard Development Timeline: Typically, 4-6 weeks of development and testing are expected before the integration is complete and ready for production use.
  • End-User Testing: Once development is complete, a small group of end-users from the customer’s team should log in to iMessage using the federated IDs. This final test ensures the setup functions smoothly and meets user expectations.

Step 5: Account for User-Specific Nuances (Caveat)

  • Unexpected Variations: Occasionally, specific user accounts may have unique setup configurations that differ from the test accounts provided. In such cases, additional development work may be required to accommodate these variations.
  • Additional Development Time: If unexpected nuances are encountered, SnippetSentry may need an extra 1-2 weeks to adjust the integration to ensure a seamless user experience across all accounts.