Timeline for How to Configure Named Credentials in Salesforce for External Callouts Using Client ID and Client Secret?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 11, 2023 at 17:47 | comment | added | identigral | It's unclear what oAuth flow your app supports but it sounds like you've answered your own question. | |
| Aug 8, 2023 at 19:00 | comment | added | Akif | Hi @identigral, thank you for your reply. I couldn't find any answer despite reading so many posts. In our scenario: SF makes a call to the token end point with client id, client secret and scope to get access token. (Oauth 2) Than makes a POST request to an endpoint with access token header alongside other headers and payload. In External Credentials, there are two OAuth 2.0 flow types: Browser Flow and JWT Bearer Flow. None of them seem to be suitable for us. Can Named Credential/External Credential handle authentication in this scenario, or auth should be done manually in Apex? | |
| Aug 6, 2023 at 18:08 | comment | added | identigral | Welcome to SFSE! Please take a moment to read How to Ask and take the tour. Have you done any research into what NC supports versus what you need? There's official documentation and Q&As here. If you have tried implementing, including a Minimal, Complete and Reproducible Example would be helpful. The scope of oAuth flows supported out of the box is the same for both legacy and new (External) NCs. | |
| Aug 6, 2023 at 15:57 | history | asked | Akif | CC BY-SA 4.0 |