How To Use The New Named Credentials (Summer '23 & Beyond)

Get In Touch: 1sync.co/contact
-----------------------------------
In this video, we discuss how to use Named Credentials to take your authentication credentials outside your Apex code. Using Named Credentials is a great way to implement oauth 2.0 in Salesforce. In Winter 23, Named credentials were changed to add an additional component, External Credentials. In Summer 23' Named Credentials were updated to use principals to manage end user management. In this video, we discuss the 5 step process on how to implement Named Credentials for a custom Oauth 2.0 system. This includes how to setup custom metadata for an auth provider. How to extend AuthProviderPluginClass in an apex class for a custom implementation. How to configure the Auth. Provider metadata and add custom fields. How to create an external credential. How to create a named credential. And how to use named credential in Apex.
-----------------------------------

[@igorkudryk]

New named credentials are powerful, but so damn painful :D And as always, Salesforce creates new features without fully supporting old functionality.
In the case of named credentials, it's storing the password and username named credentials :)

[@vinayaksharma3666]

great job

[@MangeshKadam-s5x]

Are you setting the newly generated Callback Url from Auth Provider as the redirect URL in QB setup.

[@JustinWills]

Yes that is correct

[@marcb2814]

Why didn't you use Open ID Connect for this?

[@JustinWills]

You may be able to use Open ID Connect

[@manasadharmendran]

Can we use custom setting instead of metadata?

[@JustinWills]

No. The auth. provider is coded to use metadata in the background. If you need to update values from your code, I recommend storing that information in a custom setting outside the named credential storage.