Demystifying Salesforce Flow with HTTP Callout using OAuth 2.0 Open ID Connect (Video Tutorial)

preview_player
Показать описание
Topics:
1. How to acquire Consumer Key and Consumer Secret,
2. Where to find Authorize and Token Endpoint URLs,
3. Setting the Callback URL on your 3rd Party App,
4. OAuth 2.0 Authentication Provider,
5. External Credential & Named Credential,
6. Create an Invocable Action that uses External Service,
7. Producing a Sample Response with Postman,
8. Build a fully-functioning Screen Flow, and
9. Detailed steps to fix the most common error messages!
Рекомендации по теме
Комментарии
Автор

Extremely Helpfull .Very Few people have explained web server flow Using Named Credentails

SharmaJiSFDCBlogs
Автор

Thank you for actually walking through every step. Very helpful.

JeffGreenNV
Автор

This is an incredible video!
Thank you for demonstrating how to address issues instead of giving up when encountering an error.
Very helpful!

rachelsilver
Автор

This was extremely helpful and easy to follow. Thank you! I learned a new skill thanks to you.

KukkisOy
Автор

For the List error in JSON validation, you can replace [ ] with [{ }] and the error goes way - was facing this issue earlier today and drove me nuts till I figured out the error was in the empty arrays ☺ - great video tutorial by the way - thank you for taking the time to explain this!

sfmctrailblazers
Автор

This was unbelievably helpful, thank you!

stayawakestudios
Автор

Thank you so much..This is very helpful..I have been searching for this info from past 3 weeks n i finally got what i want..

chandrikahatti
Автор

This was extremely helpful. Much thanks

salaadnur
Автор

Thak you for this demo. it was really helpful.. I have question. I was abel to set HTTP request using flow and named credentials.. problem is, Authorization token is valid only for 2 minutes and then, authentification failed. To be waorkable, I have to go to ext Named credentails => principal =. authorize.. then it is working but only for 2 minutes.. I thought whole feature of named credentials is, that authorization is done when Http request is called.. but it is not case. How would you solve it?

jurajkopecky
Автор

Great video!
I have similar scenario to setup open ID connect as auth provider and use that auth provider (auth0) to issue token for apis that use the provider as sso.
I was able to setup the auth provider and external and named credentials, however I keep getting 403 despite it works manually on postman or directly in apex without using named credentials.
Any thought on such scenario where auth provider is used to issue token for third party api? much appreciated

ikec
Автор

As of Summer 23 use Principals rather than Permission Set Mappings(which no longer will be on the page)

abark
Автор

hi, im setting the same thing here but mine requires in the body, is there any way to add it in ? stuck at the authenticate step minute 12:49

TaiNguyen-qdws