Callback URL for Deep destination in Connected App

We have a connected app and using oAuth.

The requested URL is a resource within a connected app…so not the home page.

It is dynamic so, it can request any page within the target app.

How can we configure the call back URL so that it will respect the requested destination URL after authorization given the fact that it can be any page on the connected site and not necessarily what we define the callback url to be?

Is this a limitation or do we need to make the callback URL page detect the actual destination?


The callback URL must match the callback URL of the connected app configuration settings. It is for this reason that developers are allowed to use the state parameter (see docs) so that the callback URL can load the appropriate state information, which may be redirecting to a deep URL, calling some JavaScript function, etc.

Source : Link , Question Author : Quade , Answer Author : sfdcfox

Leave a Comment