Timeline for session is not valid for use with the REST API
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 30, 2018 at 9:54 | vote | accept | CommunityBot | ||
| Jul 30, 2018 at 9:54 | |||||
| Jul 30, 2018 at 9:53 | vote | accept | CommunityBot | ||
| Jul 30, 2018 at 9:53 | |||||
| Jul 17, 2018 at 7:20 | comment | added | Amit Singh | Yes. You need to change OR you can create a User Specific for this functionality with Password Never Expires Policy. | |
| Jul 17, 2018 at 7:14 | comment | added | Amit Singh | Access Token is what we are generating with Code. Because UserInfo.getSessionId and Named Credentials will not work in case of Batch Class and future method while calling the Salesforce Own API. For Token Value, you need to put the Security token there, See the link for resetting the toke: - Reset Your Security Token | |
| Jul 17, 2018 at 6:03 | comment | added | Amit Singh | Yes. That's correct | |
| Jul 17, 2018 at 6:00 | comment | added | Amit Singh | Using the connected to get the ClientId and Client Secret. Yes, UserName and Password will be different but in every org, you need to create an instance of Custom Setting where you can store the username and password. | |
| Jul 17, 2018 at 5:58 | history | edited | Amit Singh | CC BY-SA 4.0 | Added the Description for Remote Site Ssettings and Connected Application |
| Jul 17, 2018 at 5:25 | comment | added | Amit Singh | Yes. it will work for the scheduled classes. I Have updated the answer with the reference image for the connected application. You need to generate the Session from the execute method and be sure that every time a batch runs you are generating the token only one not for all execute chunks | |
| Jul 17, 2018 at 5:24 | history | edited | Amit Singh | CC BY-SA 4.0 | Added the Reference Image for Connected Application |
| Jul 17, 2018 at 3:47 | history | answered | Amit Singh | CC BY-SA 4.0 |