Make a Callout using OAuth 2.0 Client Credentials Flow | Named & External Credentials

  Рет қаралды 11,176

Samarth Ahuja Tech Videos

Samarth Ahuja Tech Videos

Күн бұрын

Пікірлер: 13
@MaxiFiorilli
@MaxiFiorilli 7 ай бұрын
THANKS SAMARTH!!!!!! you saved, literally, my sanity today! THANK YOU!!!! already suscribed!
@nupursolanki9613
@nupursolanki9613 Ай бұрын
Great video . Really very helpful 😊
@42eslarespuesta
@42eslarespuesta 6 ай бұрын
Thank you Samarth! It has been very helpful, subscribed.
@GabeWonders-u6j
@GabeWonders-u6j 3 ай бұрын
Thanks for sharing! Looks like just giving Read Only access to the User External Credential object also provides user access to the External Credential.
@jaiaswani8039
@jaiaswani8039 11 ай бұрын
Thanks for sharing 😊
@ashutoshmishra4501
@ashutoshmishra4501 Жыл бұрын
great content
@jagadeeswaribolli6768
@jagadeeswaribolli6768 2 ай бұрын
What's the role of the callback url in this flow? We have kept dummy url.
@SfdcLearner
@SfdcLearner 7 ай бұрын
Hey thanks for sharing. But i would like to know more about integration. Instead of just single flow of integration. I would love to learn about all various options available. Can you please make a plays list of all types of integrations Atoz ❤😊
@alexandreanicio1732
@alexandreanicio1732 9 ай бұрын
Thanks for the video! Anyone know how long does the access token lifetime stands? And if it's configurable?
@MassimoTarquini-g9b
@MassimoTarquini-g9b 11 ай бұрын
thanks for sharing :). the above could have worked with the authentication flow type= browser flow too right? I usually use that flow by also creating an auth provider. I have never used the client credentials with client secret flow. why would you use this over browser flow?
@MassimoTarquini-g9b
@MassimoTarquini-g9b 11 ай бұрын
also does this grant type handles automatic refresh of the token? since with the flow type= browser flow , expiration of token is never an issue and it is handled by salesforce directly
@ig38428
@ig38428 5 ай бұрын
@@MassimoTarquini-g9b I think it sends the authorization request with every callout, instead of re-using the same access token while it is valid. Nope, scratch that... I just saw that there's a new section in the external credentials called "Callout Options". It seems it tries to re-use the same access token until it gets a 401 status code and then requests a new access token.
@Mehdi-sh7bf
@Mehdi-sh7bf 3 ай бұрын
That's awesome, thanks! would it be possible to send out the image/pdf through that integration?
OAuth 2.0 Client Credentials Flow in Salesforce
9:09
Samarth Ahuja Tech Videos
Рет қаралды 11 М.
Apex Callouts with Improved Named Credentials | Mini Hacks Solved | Season 02
25:30
Thank you Santa
00:13
Nadir Show
Рет қаралды 58 МЛН
Creative Justice at the Checkout: Bananas and Eggs Showdown #shorts
00:18
Fabiosa Best Lifehacks
Рет қаралды 35 МЛН
OAuth 2.0 explained with examples
10:03
ByteMonk
Рет қаралды 165 М.
Salesforce API Authentication and Authorization Step By Step
18:30
Cloud Developer
Рет қаралды 29 М.
How To Use The New Named Credentials (Summer '23 & Beyond)
8:43
Justin Wills
Рет қаралды 6 М.
OAuth 2 Explained In Simple Terms
4:32
ByteByteGo
Рет қаралды 473 М.
Oauth Authorization flows in Salesforce | Web Server flow | JWT Bearer token flow
1:08:26
Session Vs JWT: The Differences You May Not Know!
7:00
ByteByteGo
Рет қаралды 278 М.
OAuth 2.0 and OpenID Connect (in plain English)
1:02:17
OktaDev
Рет қаралды 1,8 МЛН
Named Credentials: Securing and Simplifying API Callouts
20:11
Salesforce Developers
Рет қаралды 16 М.
Thank you Santa
00:13
Nadir Show
Рет қаралды 58 МЛН