ISVforce Guide

Welcome to the ISVforce Guide
ISVforce Quick Start
Grow Your AppExchange Business
Design and Build Your Solution
Create a Secure Solution
Overview of Packages
Components Available in Managed Packages
About API and Dynamic Apex Access in Packages
Architectural Considerations for Group and Professional Editions
Connected Apps
Create a Connected App
Configure Basic Connected App Settings
Enable OAuth Settings for API Integration
Integrate Service Providers as Connected Apps with SAML 2.0
Create a Connected App for Mobile App Integration
Create a Custom Connected App Handler
Expose Your Connected App as a Canvas App
Test Push Notifications
Edit a Connected App
Manage Access to a Connected App
Environment Hub
Developer Hub
Notifications for Package Errors
Package and Test Your Solution
Pass the AppExchange Security Review
Publish Your Solution on AppExchange
Sell on AppExchange with Checkout
Monitor Performance with Analytics for AppExchange Partners
Manage Orders
Manage Licenses
Manage Features
Provide a Free Trial of Your Solution
Support Your AppExchange Customers
Update Your Solution
Appendices
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Create a Connected App for Mobile App Integration

A connected app is a primary means by which a mobile app connects to Salesforce. Although not required, you can use Salesforce Mobile SDK to build mobile applications as connected apps. These connected apps can access Salesforce OAuth services and call Salesforce REST APIs.
Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
Connected Apps can be created in: Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions

Connected Apps can be installed in: All Editions

User Permissions Needed
To read, create, update, or delete connected apps: Customize Application AND either

Modify All Data OR Manage Connected Apps
To update all fields except Profiles, Permission Sets, and Service Provider SAML Attributes: Customize Application AND either

Modify All Data OR Manage Connected Apps
To update Profiles, Permission Sets, and Service Provider SAML Attributes: Customize Application AND Modify All Data AND Manage Profiles and Permission Sets
To install and uninstall connected apps: Customize Application AND either

Modify All Data OR Manage Connected Apps
To install and uninstall packaged connected apps: Customize Application AND either

Modify All Data OR Manage Connected Apps

AND Download AppExchange Packages

For more information about Salesforce Mobile SDK, see Mobile SDK Development Guide.

  1. Create your connected app, and complete its basic information.
  2. Enable these OAuth Settings:
    1. Enter a callback URL. Mobile SDK uses this URL to call back to your application during authorization. For Mobile SDK, this value must match the OAuth redirect URI specified in your app’s project configuration.
    2. Select the following OAuth scopes: Access and manage you data (api), Perform requests on your behalf at any time (refresh_token, offline_access), and Provide access to your data via the Web (web).
    3. Deselect Require Secret for Web Server Flow if the Mobile SDK app performs authorization through the device’s native browser.
  3. Enter the mobile start URL to direct users to a specific location when the app is accessed from a mobile device.
    If you don’t enter a mobile start URL, users are sent to the start URL defined under Web App Settings.
    If the connected app you’re creating is a canvas app, you can skip this field. The Canvas App URL field contains the URL that gets called for the connected app.
  4. Select PIN Protect if your app supports PIN protection. This setting allows the admin to set the session timeout and PIN length for mobile applications after installing the connected app.
    Salesforce Mobile SDK supports PIN protection. You can also implement it manually by reading the mobile_policy object from the user’s Identity URL.
  5. For App Platform, specify the app platform, such as iOS.
  6. For Restrict to Device Type, specify the supported device form factors for the mobile app. If the app supports all form factors, don’t choose a value.
  7. For App Version, enter the version number of the mobile app.
  8. For Minimum OS version, enter the version required for the app.
  9. To confirm that this app is only for internal (non-public) distribution, select Private App . This setting is required because Apple doesn’t allow distribution of public mobile apps outside of its App Store.
  10. If the mobile app is private, specify the location of the Mobile App Binary file. The format of the file is IPA for iOS, and APK for Android.
  11. For iOS apps only:
    1. Specify the location of the Application Icon that is displayed while the app is being downloaded and installed on an iOS device.
    2. Specify the iOS Bundle Identifier.
      For iOS 7 and later, use the same bundle identifier that you used when developing the app in XCode. If you don’t, users see two app icons during installation.
  12. If the mobile connected app is a public app and you haven’t uploaded its binary file to Salesforce, enter the app binary URL.

    If you remove mobile integration from a new version of an existing connected app, mobile integration is removed from all versions of the app. For example, you publish a package containing version 1.0 of your connected app with mobile integration. You then remove mobile integration from the app, repackage it, and publish it as version 1.1. If a customer installs the earlier package with version 1.0, the connected app doesn’t contain mobile integration.

    Note

  13. Enable push notifications, as needed. See Mobile Push Notifications.
  14. When you’ve configured all settings for your connected app, click Save.