You are here:
Connected App to External Client App Migration
Create a local external client app based on one of your existing local connected apps. As the next generation of connected apps, external client apps provide many of the features of connected apps while offering increased security.
See Comparison of Connected Apps and External Client Apps Features.
External client apps don’t support username-password flow. If you migrate a connected app that uses username-password flow, the flow doesn’t work on the external client app. Instead of the username-password flow, we recommend using the OAuth 2.0 web server flow with Proof Key for Code Exchange (PKCE) or the OAuth 2.0 client credentials flow.
If a push is configured, but the push settings aren't valid, the connected app migration will fail. Invalid push settings include an expired P12 certificate for Apple and deprecated Server Key configuration instead of service account settings on Android.
- Create an External Client App from a Connected App
Use the automated process to create external client apps that replace your existing local connected apps. After migration, the old connected app remains as a read-only version in App Manager. External client apps created through migration are secure.
