Timeline for OAuth Named Credential Callout Issue
Current License: CC BY-SA 4.0
14 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
S Aug 8, 2023 at 11:06 | vote | accept | user28452 | ||
Aug 18, 2021 at 21:44 | answer | added | user28452 | timeline score: 0 | |
Nov 13, 2020 at 15:52 | comment | added | Ashish | How did you add Okta as an authentication provider ? I have been struggling with setting up Okta authentication in salesforce | |
Oct 8, 2020 at 11:06 | comment | added | Mantvydas Ozerenskis | I have the same issue. Calls with service-to-service (machine-to-machine) okta authentication does not work in salesforce "Named Credentials". The only way right now is author suggested solution. :( | |
Apr 22, 2020 at 20:02 | vote | accept | user28452 | ||
S Aug 8, 2023 at 11:06 | |||||
Apr 17, 2020 at 0:59 | comment | added | user28452 | @Kevin Br: It should be the base URL. But I ended up doing the normal as posted in the solution. I was successful in getting OKTA access token through this. | |
Apr 17, 2020 at 0:58 | answer | added | user28452 | timeline score: 1 | |
Apr 15, 2020 at 21:32 | comment | added | Kevin Br | @user28452 - is the URL in the named credential the base URL, or the full REST endpoint? (ie, acme.okta.com vs. acme.okta.com/api/v1/authn ) | |
Oct 18, 2019 at 18:00 | comment | added | Bryan Anderson | Are you able to show this callout working in another too like cURL or POSTMAN? | |
Oct 18, 2019 at 16:29 | comment | added | user28452 | @Bryan: Yes that is the response I am getting. | |
Oct 18, 2019 at 14:18 | comment | added | Dhanik Lal Sahni | Looks like URL is not correct. Please check once. | |
Oct 18, 2019 at 13:43 | comment | added | Bryan Anderson |
So this is the response you're getting from System.debug(res.getBody())
|
|
Oct 18, 2019 at 11:14 | history | edited | user28452 | CC BY-SA 4.0 |
added 54 characters in body
|
Oct 18, 2019 at 6:10 | history | asked | user28452 | CC BY-SA 4.0 |