When you use the Account Administration tool to configure an application role for an Enterprise account, you can select "Enable Secure Content." If you select this option and publish v30 or later retail folios with the "Encrypt Folio" option selected, the content in those folios becomes secure on iOS devices in the following ways:

  • Folios in a secure account are not available through the Folio Producer Service (acrobat.com). Folios are available only when published to the Adobe Distribution Service.
  • Retail folios published to the Adobe Distribution Service are encrypted.
  • Folios delivered to an app are encrypted.
  • When the device is locked or powered off, secure folios remain encrypted. The folios become available after the device is unlocked using a pass code. This feature uses standard iOS functionality provided by the operating system. For more information on secure apps, see Apple's iOS Security document (PDF).

Note:

Use this option only if you have confidential or sensitive information in your app. Social sharing, web viewer, and background downloads are not available in a secure account. Use this option only for an app with direct entitlement and retail folios published as v30 or later.

Secure content resources

Watch Colin Fleming's Secure Content Video.

Read James Lockman's article Considerations for using Secure Content with DPS.

Read James Lockman's article Protecting Content on an iOS Device with DPS.

Restrictions and limitations of secure content

  • The app must include direct entitlement.
  • Only retail folios can be encrypted. 
  • Social Sharing via the web viewer is not available.
  • Wireless preview of secure folios via Folio Producer is disabled by design. Use Preview on Device or a development app to preview secure folios.
  • Background downloading and progressive downloading are not supported. On a device, the entire folio must be downloaded prior to being decrypted.
  • At this time, folios are secure only on iOS viewers, not Android or Windows Store.

Enabling secure content

To enable secure content for an application account, do the following:

  1. Use the Account Administration to configure an application account (Enterprise only), and choose Enable Secure Content.

    Secure Content
  2. Create folios with a v30 or later viewer version.

    Folios with pre-v30 viewer versions cannot be encrypted.

    You cannot encrypt folios that have already been published. Instead, unpublished the folio, create a new v30 folio, and publish the new folio with Encrypt Folio selected.

  3. When using Folio Producer to publish the folio, select Encrypt Folio, and publish the folio as Public and Retail. (Free folios cannot be encrypted.)

    Publish Folio
  4. In the Apple iOS developer site, create or configure your App ID to enable Data Protection. Build new mobileprovision files, and then use DPS App Builder to build the app.

    Configure your App ID to enable Data Protection
  5. If you are submitting your app to Apple, indicate that your app includes encryption during the iTunes Connect submission process. See the Apple guidelines.

    iTunes Content Submission

After signing in to the Adobe Content Viewer, secure folios will not show up in your library as available for download because they are not available through the Folio Producer Service. To preview folios in a secure account, you can use the Preview on Device or Preview on Desktop menu setting from both the Overlay Creator Panel and the Folio Builder Panel in InDesign. Alternatively, you can build a custom app and view folios published as Public and Retail.

Updating the security patch level

Adobe can release security patches as needed to ensure secure content. If a security breach occurs, Adobe will make a new security patch available. Publishers can then specify the newest security patch and deprecate the older version of the app, preventing users from continuing to take advantage of the security breach.

To fix a security breach, Adobe might need to change both server components and the app client. If the security breach requires a new app client, publishers should follow these steps to build a new app version with the newest patch. Users should install the new app version to get security patches. In this case, the app with a new security patch will detect the need for an upgrade and prevent users from downloading additional secure folios.

Use the Account Administration tool to specify the newest security patch, if necessary.

  1. Use the Account Administration to configure the application account in which secure content is enabled.

  2. Under "Security patch level," specify the desire security patch for iOS.

    Secure content is not yet enabled for Android and Windows apps.

  3. After specifying the patch level, click Submit at the bottom of the window.

    It may take as long as 15 minutes for the security patch update to go into effect.

  4. Use DPS App Builder to rebuild the app, and resubmit it to the App Store or re-post it if it's a private Enterprise app.

  5. In Folio Producer Organizer, update the published folios. Leave the "Update content" option selected.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy