วีดีโอ

THANNNK YOUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU😭😭😭😭😭😭😭 I've spent hours struggling with this

Your contribution is highly appreciated 😊

great informative video Samarth 🤩 I did know about the other companies like Paypal and Google you mentioned. But Microsoft was surprise for me. Can you please make a dedicated video about the interview process. Also do they ask DSA for Salesforce development roles as well.

Also please share what and how to prepare company specific with some resources. Also share resources for system design. And if any DSA required for Salesforce roles.

WHAT IS THE JWT FLOW? Sometimes you want to authorize servers to access data without interactively logging in each time the servers exchange information. For these cases, you can use the OAuth 2.0 JSON Web Token (JWT) bearer flow. This flow uses a certificate to sign the JWT request and doesn't require explicit user interaction. However, this flow does require prior approval of the client app. With the OAuth 2.0 JWT bearer token flow, the client posts a JWT to the Salesforce OAuth token endpoint. Salesforce processes the JWT, which includes a digital signature, and issues an access token based on prior approval of the app.  BASICS OF CERTIFICATE BASED COMMUNICATION When we send data over HTTPS, the data is sent in encrypted form which the receiver will decrypt. Private Keys and Public Keys terms are used in cryptography. These keys are used to encrypt/decrypt sensitive data. Any message that is encrypted with a certificate's Public Key, can only be decrypted with the certificate's private key Anyone with access to the public key can verify that the message was created by someone access to certificate's private key. X.509 certificates are issued by trusted third-party organizations known as certificate authorities (CAs). The client can verify the certificate's authenticity by checking its digital signature against the CA's public key  CA SIGNED VS SELF SIGNED CERTIFICATES The difference between a CA certificate and a self-signed certificate is the issuer of the certificate. A self-signed certificate is created, signed, and issued by the subject of the certificate (the entity it is issued to), while a CA certificate is created, signed, and issued by a third party called a certificate authority (CA) that is authorized to validate the identity of the applicant. There is no third-party verification of the certificate's authenticity or the identity of the certificate owner for SSC. Self-signed certificates are often used for testing or internal purposes, but they are not trusted by external parties who have not explicitly trusted the certificate. The CA's public key is included with the certificate, which allows the certificate to be verified by any party that trusts the CA.  STEPS INVOLVED IN CERTIFICATE COMMUNICATION Salesforce requires a X509 certificate be uploaded to the connected app. An X.509 certificate is a digital document that is used to authenticate the identity of an individual or organization on the Internet. The third party system will make a request to the Salesforce's OAuth token endpoint by sending JWT with the certificate's private key signed using RSA-sha256, plus the client id. Using the digital certificate uploaded in the connected App, Salesforce verifies whether the sender is actually the one sending or is it someone else. Once verified Salesforce returns the access token. The external application can then use the access token to access the Salesforce API on behalf of the user. The access token is also valid for a specific period of time and can be refreshed using a refresh token. CREATION OF A SELF SIGNED CERTIFICATE We have two types of certificates: Self Signed and CA signed. For this demo we are going to create a Self Signed one since the CA signed has a cost associated with that. We are going to create a SSC using OpenSSL. For that you would need to first install openSSL for windows and then follow some commands openssl req -x509 -sha256 -nodes -days 36500 -newkey rsa:2048 -keyout salesforce.key - out salesforce.crt

Hello bro azure ad connected to Salesforce single sign on ...azure team asking for Salesforce redirect uri what will be the url

Great summary, very well explained. Looking forward to learning more from your content!

using connected app can we pass client id and client secret without exposing them in code?

Amazing 👏

you passed the attribute to custom lwc without the hypen in between as how we do , does it work that way as well ?

Why would you use a nodeserver ? can not your extension interact directly with salesforce since you never use client secret ?

This is really useful and helpful content. Thanks

Amazing Amazing. I was able to grasp it when you showed the order in which lines are executing the code. Love it man!

As far as I know, the encryption is done using Private key and decryption using public key.. Please clarify this ... Samarth

Thanks for amazing content , can you please help us where we can get pdf of your video. Thanks again

Hi Ahuja, I am a salesforce developer. Recently, I plan to develop a chrome extension for sales people for all organization, so I hope sales person populate their username and password to get access token via jump to salesforce login page and redirect to chrome extension. Can I implement it with this approach, and do you have any advice for it. Thx. Peter

❤

I can see the value that is returned from the Apex Class but when trying to use the value for mapping on the document it's not working. Am I missing something

hi Samarth, Can you please share the code link as well11

I'm a user trying to clone a private repo, I've the access to the repo and still I'm not able to clone the repo. I'm getting the same error

❤

Enjoy 😊

🫡

Thank you Samarth! It has been very helpful, subscribed.

Thanks for the update

❤

Thanks for this video but try to add your introduction in begging it will help you to increase the reach . Thanks

❤

Can you named those company name here

Very Informative. Thanks for sharing!

Thanks for the great explanation. I have a question can't we use Named Credentials for Web server flow? if so can you please explain. If not can you also expalin why we cannot use Named Credentials config for web server flow.

Amazing video

❤

Thank You for this amazing Video. I have one question which I wanted to ask. When we set a component attribute (like isSubscribed), its value is maintained by the framework, even if the component is re-rendered or reinitialized. Is it right? I am not able to find any article which tells this thing. <aura:attribute name="isSubscribed" type="Boolean" default="false" />

Hi Samarth, very useful video. One question, I am currently using experience cloud, and I've configured the redirect url to my site but when I try to use my google account it appers this error : "NO_ACCESS: User was not authorized for the community" any suggestion/recommendation? thank you.

Can we call an Integration Procedure from a DataRaptor? If yes, then How to call an Integration Procedure from DataRaptor?

Can we call an Integration Procedure from a DataRaptor? If yes, then How to call an Integration Procedure from DataRaptor?

Very informative. Thank you