Timeline for REST API without Connected App
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 23, 2020 at 9:45 | comment | added | Rahul Gawale |
@bigassforce I have a requirement where I need a different callback URL for the connected app in each subscriber org. I tried to create the app using the URL method, still there is a limitation that I need to have the same callback URL. otherwise, I get error=redirect_uri_mismatch&error_description=redirect_uri%20must%20match%20configuration while authenticating.
|
|
| Dec 24, 2018 at 15:58 | comment | added | Matt and Neil | @YsrShk Note, when you click "Allow" for Workbench, salesforce deploys an Installed Package using their internal automated process user. To do the same, you could invoke the Metadata API from your app. | |
| Dec 23, 2018 at 14:09 | comment | added | Ysr Shk | @bigassforce May I know, how workbench type applications work with salesforce. Like, I dont create connected app, but the workbench itself creates that in my org. How can I do that? any hint/links/references? Thanks. | |
| Sep 13, 2017 at 9:05 | comment | added | Matt and Neil | @JonathanMcIntire no. If it's for internal use, the connected app in your production instance makes sense as you say. If it's an app you plan to distribute, put the connected app in your packaging / release org with the namespace. | |
| Sep 11, 2017 at 23:14 | comment | added | Jonathan McIntire | Would it be a security issue at all to create this connected app in our production Salesforce instance instead of a standalone developer account? | |
| Nov 30, 2014 at 12:50 | vote | accept | Saranya | ||
| Nov 22, 2014 at 16:28 | comment | added | Matt and Neil |
Strongly recommend trying to use User Agent flow if you can @Saranya. It doesn't need the secret and absolves one of a lot of responsibility.
|
|
| Nov 21, 2014 at 6:01 | comment | added | Saranya | Thanks for the replies. I was able to implement the functionality via Username - password flow and I created the connected app only once. Shall I go with the Username password flow itself or switch over to User agent flow. kindly advise. | |
| Nov 19, 2014 at 0:29 | history | edited | Matt and Neil | CC BY-SA 3.0 |
deleted 13 characters in body
|
| Nov 19, 2014 at 0:27 | comment | added | metadaddy | You just don't use the secret with user-agent flow - see developer.salesforce.com/page/… | |
| Nov 18, 2014 at 3:11 | comment | added | Matt and Neil |
Ah good spot @metadaddy - secret is optional_ for that flow right?
|
|
| Nov 18, 2014 at 3:08 | comment | added | metadaddy | Don't distribute an app containing a secret. If you do, it's not really a secret any more. As Daniel says, use the user-agent flow. | |
| Nov 17, 2014 at 21:50 | comment | added | Daniel Ballinger | One catch is that you will need a separate Connected App to support sandboxes. Or at least my experience is that I needed one to use for sandboxes and one for production/dev orgs. They same may also be true for pre-release orgs. | |
| Nov 17, 2014 at 20:52 | history | edited | Matt and Neil | CC BY-SA 3.0 |
added 2 characters in body
|
| Nov 17, 2014 at 14:49 | comment | added | Matt and Neil |
Yep @Saranya you got it! The client_id and secret will be the same for everyone who uses the app. But don't use just any 'sample org', make a special org with a namespace and hold onto it.
|
|
| Nov 17, 2014 at 14:42 | comment | added | Saranya | The app is not a Salesforce app. This will be a mobile app which can be installed by anyone. This means that multiple org users will use it. Do you still mean that this app can just hard code client_id and secret from some sample org and access other orgs without creating the connected app in each and every org? | |
| Nov 17, 2014 at 14:23 | comment | added | thegogz | solid answer, this is a regular misconception of OAuth clients | |
| Nov 17, 2014 at 14:05 | history | answered | Matt and Neil | CC BY-SA 3.0 |