2

So I don't understand a few things, so I'll restate some things I know or believe and will move from there.

  • You don't need a package for a Connected App to be used with OAUTH flow/REST API access. I know this, I've done it.
  • You do need a package if you want IP Address restrictions to be relaxed (the admin can install it, and then change the settings). Changes to IP address restrictions settings made on the "original" DE Connected App are only propagated via package (and probably that's best left to the admin instead of the package.
  • You do need a package if you're gonna package custom objects, visual force/apex stuff, widgets, layouts, and permission sets. Or if you want the admin to be able to flip between self-authorization and permission set acccess to the app
  • You don't need a package for Canvas, but on the other hand using a package to distribute some widgets like tabs, buttons, etc, makes it easier for the admin, maybe.
  • You need a package to get whitelisted for Group/Professional edition rest api access.

Do I have the right of it?

  • Pretty much :) whatcha building? – bigassforce Aug 16 '15 at 10:08
2

You don't need a package for a Connected App to be used with OAUTH flow/REST API access. I know this, I've done it.

Correct. The connected app definition can be in any org and your code can just use the key / secret.

You do need a package if you want IP Address restrictions to be relaxed (the admin can install it, and then change the settings).

Correct. Admins cannot relax IP Restrictions unless the connected app is installed.

Changes to IP address restrictions settings made on the "original" DE Connected App are only propagated via package (and probably that's best left to the admin instead of the package.

Not quite; the installed instance is independent of the definition. IP Restrictions are not propagated.

You do need a package if you're gonna package custom objects, visual force/apex stuff, widgets, layouts, and permission sets. Or if you want the admin to be able to flip between self-authorization and permission set acccess to the app.

Correct. Without the app installed, admins can only Allow / Block access at an org-wide level.

You don't need a package for Canvas, but on the other hand using a package to distribute some widgets like tabs, buttons, etc, makes it easier for the admin, maybe.

Correct.

You need a package to get whitelisted for Group/Professional edition rest api access.

Correct. The managed package must pass Security Review, but I don't think Group Edition can use.

  • So the "Trusted IP Range for OAuth Web server flow" stuff can really only be set by the admin who installs the package, correct? – MJB Aug 17 '15 at 14:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.