Timeline for OAuth Access Token Expiration
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 28, 2015 at 14:44 | comment | added | sfdcfox♦ | You should probably ask a separate question for a longer answer, but yes, each app should use its own connected app. 1. You can only have five active sessions per app. 2. Sharing tokens can cause failures on all apps if one is logged out. 3. You can identify misbehaving apps easier if they each use their own session token. | |
| Apr 28, 2015 at 14:09 | vote | accept | Brad Ullery | ||
| Apr 28, 2015 at 14:09 | comment | added | Brad Ullery | Thanks. That is very helpful. So, if I have a scheduled service/cron running Bulk Api actions and also real time Rest Api actions, should I use multiple connected apps? Is there a standard way to manage the access token usage so one process does not invalidate the access token while the other process is "working"? Would it make sense for this to be its own question? | |
| Apr 28, 2015 at 3:24 | history | answered | sfdcfox♦ | CC BY-SA 3.0 |