Package an External Client App with First-Generation Managed Packages

Use first-generation managed packages to distribute external client apps to other orgs. Create an external client app with Packaged distribution state, add it to your managed package, and install the package in subscriber orgs.

Note
Note External client apps can only be packaged with 1GP managed packaging in the org where they were created.

Before you package an external client app with a first-generation managed package:

  • Create an external client app and set its distribution state to Packaged. To convert a local external client app to packaged in Setup, go to App Manager, view your external client app, and set Distribution State to Packaged.
  • Have an existing first-generation managed package or enable a namespace to create one.
  1. From Setup, in the Quick Find box, enter Package Manager, and then select Package Manager.
  2. Create a new managed package or select an existing one.

    To create a new package, you need a namespace enabled in your org. From Setup, go to Namespace Settings to enable a namespace.

  3. Click Add to add components to your package.
  4. From the Component Type dropdown, select External Client Application.
    Note
    Note Only external client apps with Packaged distribution state appear in the list. If you don't see your external client app, confirm that the distribution state is Packaged in the External Client App Manager.
  5. Select your external client app and add it to the package.

    Adding an external client app automatically includes dependent plugin entities. You can add other related entities.

  6. Create a package version.

    Select Beta or Released based on your distribution needs.

  7. Install the package in subscriber orgs by using the package installation link.

After installation, update external client app policies as needed before performing authorization flows.

Note
Note If you delete the external client app from the source org, the subscriber org's external client app breaks. The subscriber org depends on information in the global OAuth settings on the source org. Removal of the external client app causes the OAuth flow to fail in the subscriber org.