<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Salesforce notes on Medium]]></title>
        <description><![CDATA[Stories by Salesforce notes on Medium]]></description>
        <link>https://medium.com/@tou_sfdx?source=rss-3c0b202c8c51------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*9vK2pVYEeM-jsnSSAdjvSw.jpeg</url>
            <title>Stories by Salesforce notes on Medium</title>
            <link>https://medium.com/@tou_sfdx?source=rss-3c0b202c8c51------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:38:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tou_sfdx/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Dynamic SOQL — invalid field when accessing a lookup in Apex Salesforce]]></title>
            <link>https://medium.com/@tou_sfdx/dynamic-soql-invalid-field-when-accessing-a-lookup-in-apex-salesforce-3b96a7d9a3ba?source=rss-3c0b202c8c51------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b96a7d9a3ba</guid>
            <dc:creator><![CDATA[Salesforce notes]]></dc:creator>
            <pubDate>Wed, 16 Oct 2024 10:00:42 GMT</pubDate>
            <atom:updated>2024-10-16T14:23:37.149Z</atom:updated>
            <content:encoded><![CDATA[<h3>Dynamic SOQL — invalid field when accessing a lookup value in Apex Salesforce</h3><p>When we have a Child__c object that has a relationship to a Parent__c object, we usually use __r to query parent fields.</p><pre>SELECT Id, Parent__r.Name FROM Child__c</pre><p>Using dynamic SOQL, when you try to access the parent field, an “invalid field” exception is raised:</p><pre><br>String parentName = child.get(&#39;Parent__r.Name&#39;);<br><br>System.SObjectException: Invalid field Parent__r.Name for Child__c</pre><p>To access the parent fields in dynamic SOQL, you must use the getSObject method like this:</p><pre>String query = &#39;SELECT Id, Parent__r.Name FROM Child__c LIMIT 1&#39;;<br>List&lt;sObject&gt; records = Database.query(query);<br><br>// get 1st record<br>sObject record = records[0];<br><br>// use getSObject to access the parent<br>sObject parentObject = record.getSObject(&#39;Parent__r&#39;);<br><br>// use get to access the field<br>String result = (String) parentObject.get(&#39;Name&#39;);<br><br>System.debug(&#39;result: &#39;+ result);</pre><p>This is how i managed to access multiple parent fields :</p><pre>String lookupField = &#39;Parent1__r.Parent2__r.Parent3__r.Name&#39;;<br><br>// dynamic SOQL query <br>String query = &#39;SELECT &#39; + lookupField + &#39; FROM Child__c &#39;;<br><br>// execute query<br>List&lt;sObject&gt; records = Database.query(query);<br><br>String result = null;<br><br>// Split the lookupField &#39;x.y.z&#39; =&gt; [x,y,z]<br>List&lt;String&gt; parts = new List&lt;String&gt;();<br>for (String part : lookupField.split(&#39;\\.&#39;)) {<br>    if (part != null &amp;&amp; part.trim() != &#39;&#39;) {<br>        parts.add(part);<br>    }<br>}<br><br>// access the parents 1 by 1<br>for(SObject record : records) {<br>  sObject currentRecord = record;<br>  for(String part : parts) {<br>    // check last part<br>    if(part == parts[parts.size() - 1]) {<br>        result = (String) currentRecord.get(part);<br>    } else {<br>        currentRecord = (sObject) currentRecord.getSObject(part);<br>    }<br>  }<br>}<br><br>System.debug(&#39;result: &#39;+ result);</pre><p>The most important take is that when using dynamic SOQL: <strong>use</strong> <strong>getSObject(Parent__r) to access parent fields.</strong></p><pre>String result = childRecord.getSObject(&#39;Parent__r&#39;).get(&#39;Parent_Field__c&#39;);</pre><p>Thanks to Daft (<a href="https://salesforce.stackexchange.com/users/3822/daft">https://salesforce.stackexchange.com/users/3822/daft</a>) for pointing out to the solution, i just added my method to access many parent levels</p><p><a href="https://salesforce.stackexchange.com/a/76582/1029">https://salesforce.stackexchange.com/a/76582/1029</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b96a7d9a3ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Date and Datetime conversion in Salesforce Apex]]></title>
            <link>https://medium.com/@tou_sfdx/date-and-datetime-conversion-in-salesforce-apex-4476a2689710?source=rss-3c0b202c8c51------2</link>
            <guid isPermaLink="false">https://medium.com/p/4476a2689710</guid>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-apex]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <dc:creator><![CDATA[Salesforce notes]]></dc:creator>
            <pubDate>Thu, 16 Jul 2020 09:20:54 GMT</pubDate>
            <atom:updated>2024-07-13T20:42:37.413Z</atom:updated>
            <content:encoded><![CDATA[<h3>1. Convert Datetime to Date</h3><blockquote>DateTime dt = System.now();<br>Date d = Date.newInstance(dt.year(), dt.month(), dt.day());</blockquote><h3>2. Convert Date to Datetime</h3><blockquote>Date d = Date.today();<br>Datetime dt = d;</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4476a2689710" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understand and use the RelayState parameter in SAML SSO with Salesforce]]></title>
            <link>https://medium.com/@tou_sfdx/understand-and-use-the-relaystate-parameter-in-saml-sso-with-salesforce-c5131d635a1c?source=rss-3c0b202c8c51------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5131d635a1c</guid>
            <dc:creator><![CDATA[Salesforce notes]]></dc:creator>
            <pubDate>Mon, 04 May 2020 15:33:06 GMT</pubDate>
            <atom:updated>2020-05-04T15:33:06.170Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lf7xlm6e6MpL9dlC3QyhSQ.png" /></figure><p>When implementing SSO in Salesforce, often there is a need to redirect the user to a specific page after the SSO is successful for the best possible user experience. for this requirement, the RelayState parameter must be used. In this post i show a quick example for both use cases : when Salesforce is the identity provider and when Salesforce is the service provider.</p><h4><strong>Salesforce is the identity provider</strong> (IDP)</h4><p>In this scenario the user is already authenticated in Salesforce and wants to be authenticated to an external app (service provider) <strong>and automatically redirected </strong>to a specific resource (URL) after the authentication is successful.</p><p>Add the RelayState parameter to the <strong>IDP Initiated login url</strong> in the SAML connected app :</p><ul><li>Open Setup -&gt; Apps -&gt; Connected apps -&gt; manage connected apps -&gt; open the SAML Enabled connected app</li><li>Copy the IDP Initiated Login URL as shown below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tTo7M7Tq93u6TTVy-BrbvA.png" /></figure><ul><li>Add the RelayState parameter to the IDP initiated login URL like this :</li></ul><blockquote><a href="https://identity.my.salesforce.com/idp/login?app=0spE00000008XXX&amp;RelayState=/apex/test">https://&lt;sf instance&gt;/idp/login?app=0spE00000008XXX<strong>&amp;RelayState</strong>=</a><em>CUSTOM</em>_<em>URL</em></blockquote><ul><li>When the user goes to the above link Salesforce automatically adds the RelayState as an additional POST parameter. The external app (service provider) in this case will authenticate the user based on the <strong>SAMLResponse (1) </strong>parameter, and when the authentication is successful, the user is redirected to the URL in the <strong>RelayState(2) </strong>Parameter.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r874K_vbSSBnZ2PmwsT8fw.png" /></figure><h4>Salesforce is the service provider (SP)</h4><p>In this scenario the user is already authenticated into an external app and wants to be authenticated to Salesforce (service provider) <strong>and automatically redirected </strong>to a specific Salesforce URL after the authentication is successful.</p><p>The external app must send the RelayState parameter in addition to the SAMLResponse. The RelayState is <strong>automatically interpreted</strong> by Salesforce, it must contain a <strong>valid Salesforce URL</strong> in order to work properly.</p><p>For example, to automatically redirect the user to the Case Tab after the SSO is Completed :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*ZhlVIKA1N44LWr_YOnk9hQ.png" /></figure><p>If the external system doesn’t know the exact Salesforce URL to redirect to, a Salesforce developer can create a custom page or component to handle the redirection depending on the parameters received. For example, RelayState = <strong>/apex/SSO_Redirect?param1=value1&amp;param2=value2 ,</strong></p><p>Where <strong>SSO_Redirect</strong> is a custom page that reads the parameters and direct the user to the requested resource.</p><h4>Summary</h4><ul><li>For the best possible SSO experience, use the RelayState so that users are not spending valuable time looking for resources after they are authenticated between systems &amp; Salesforce.</li><li>The RelayState is fully supported in both ways in Salesforce.</li><li>Most of the time the RelayState value must be <strong>URL Encoded</strong></li></ul><p>Any questions are welcome ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5131d635a1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Salesforce REST API Tutorial]]></title>
            <link>https://medium.com/@tou_sfdx/salesforce-rest-api-tutorial-3bcd39e493f6?source=rss-3c0b202c8c51------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bcd39e493f6</guid>
            <category><![CDATA[postman]]></category>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Salesforce notes]]></dc:creator>
            <pubDate>Sat, 22 Feb 2020 14:09:22 GMT</pubDate>
            <atom:updated>2020-02-22T14:09:22.367Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3U04EgfZUngYYlfaZ-W_Ow.png" /></figure><p>Salesforce provides a native REST Api that enables external apps to read / manipulate the data located in Salesforce.</p><p>In this tutorial, we will see how to connect to REST API and send a request to create an account.</p><p>We will use <a href="https://www.postman.com/">Postman</a> for testing. you can however choose the REST API client of your choice.</p><h3>Step 1 : Create a connected app in Salesforce</h3><ul><li>Open Setup <strong>home -&gt; Apps -&gt; Manage apps -&gt; new connected app</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/433/1*Ps3b5goiW8A8P7Xh_CSRDg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pb4_P7FStCNSn1yg-4_6HA.png" /></figure><ul><li>Set the Name, API Name and contact Email</li><li>Enable OAuth Settings</li><li>Set the callback URL to <strong>sfdc://oauth/restapi/success</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VsmmIRBxGVw4w7YCnwlitA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FG2FihOpxqYik0LIMIh2bg.png" /></figure><ul><li>Select the scope : “<strong>Access and manage your data (api)</strong>”</li><li>Save the connected app and wait few minutes for it to be activated.</li><li>Note the consumer key and consumer secret to use them in the next step</li></ul><h3>Step 2 : Connect to the REST API</h3><p>To authenticate to the REST API, we use the<a href="https://help.salesforce.com/articleView?id=remoteaccess_oauth_username_password_flow.htm&amp;type=5"> OAuth Username-Password </a>flow.</p><ul><li>Create a new Postman collection</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/521/1*HlrhO63jinVtvvr1JTMm2w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4O734jFnwhXdmU3nosch1g.png" /></figure><ul><li>Create a new Request, name it “<strong>Authentication request</strong>”and add it to the collection created previously.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*OOP2Hh58O3s_IbWQtKAwXA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*VnwMMFwu-PUo7spydLBKNQ.png" /></figure><p>Configure the request as follows :</p><ol><li><strong>Method</strong> : <strong>POST</strong></li><li><strong>Endpoint</strong> : <a href="https://login.salesforce.com/services/oauth2/token">https://login.salesforce.com/services/oauth2/token</a> (<em>replace login by test if connecting to the sandbox</em>)</li><li><strong>Headers</strong></li></ol><ul><li>Content-Type : application/x-www-form-urlencoded</li></ul><p>4. <strong>Body</strong></p><ul><li>grant_type : password</li><li>client_id : paste the consumer key from the connected app</li><li>client_secret : paste the consumer secret from the connected app</li><li>username : Salesforce username</li><li>password : Salesforce password</li></ul><p>5. Hit <strong>send</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i15y-c2m5kRVRHElJgWr0A.png" /></figure><p>Salesforce returns the response that contains the <strong>access token and instance_url </strong>note these 2 values to use in the next step.</p><h3>Step 3 : Manipulate data with REST API</h3><p>In this step we create an account in Salesforce with the previously obtained access_token and instance_url,</p><h4>Create an account</h4><ul><li><strong>Method</strong> : POST</li><li><strong>Endpoint</strong> : &lt;<strong>instance_url&gt;</strong>/services/data/v20.0/sobjects/Account</li></ul><p><strong>Headers :</strong></p><ul><li>Authorization : Bearer &lt;<strong>access_token&gt;</strong></li><li>Content-Type : application/json</li></ul><p><strong>Body :</strong></p><ul><li>The body must be in JSON format</li><li>To create a new account with the Name “Test REST API Account” paste the following JSON in the body</li></ul><pre>{<br> &quot;Name&quot; : &quot;Test REST API Account&quot;<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yjlVupfXbk1umdktbFRtwA.png" /></figure><p>Body Part :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X_jayqTRcu8dPAVhMVazeA.png" /></figure><ul><li>Send the request.</li></ul><p>After the request is sent, a response is returned by Salesforce with the ID of the new account created.</p><p>Let’s see the new account created directly in Salesforce :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4NRduF_koDVG8Sb4ZSmtjg.png" /></figure><h3>Conclusion</h3><p>The REST API enables you to access (read, update, delete, export…) all data present in Salesforce from an external app, to dig deeper, read the REST API developer guide :</p><ul><li><a href="https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_what_is_rest_api.htm">https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_what_is_rest_api.htm</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bcd39e493f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Salesforce OAuth : JWT Bearer Flow]]></title>
            <link>https://medium.com/@tou_sfdx/salesforce-oauth-jwt-bearer-flow-cc70bfc626c2?source=rss-3c0b202c8c51------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc70bfc626c2</guid>
            <dc:creator><![CDATA[Salesforce notes]]></dc:creator>
            <pubDate>Thu, 20 Feb 2020 13:47:51 GMT</pubDate>
            <atom:updated>2020-02-20T14:05:29.410Z</atom:updated>
            <content:encoded><![CDATA[<h3>Salesforce OAuth : JWT Bearer Flow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tD80Yadu0HWGnx9GiLE41g.png" /></figure><p><strong>Overview</strong></p><p>The JWT Bearer Flow is an OAuth flow in which an external app (also called client or consumer app) sends a <strong>signed JSON string</strong> to Salesforce called JWT to obtain an <strong>access token. </strong>The access token can then be used by the external app to read &amp; write data in Salesforce.</p><p>Unlike some other OAuth Flows, the JWT flow doesn’t require end-user interaction to operate. The external app sends the JWT and authenticates itself without manual intervention.</p><p>This article illustrates the necessary steps required to implement this flow in Salesforce, <strong>with no focus on a specific programming language.</strong></p><h4><strong>Generate a private Key and a Certificate :</strong></h4><p>The <strong>private key</strong> is used by the external app to <strong>sign the JWT</strong> and the <strong>digital certificate</strong> is used by Salesforce to <strong>validate the signature </strong>and issue an access token.</p><p>Install OpenSSL and generate a private key and a digital certificate<strong> </strong>using the command line terminal.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2e16c6250f84866a1a8face4a56f65b3/href">https://medium.com/media/2e16c6250f84866a1a8face4a56f65b3/href</a></iframe><p>After executing the commands above, 2 files are generated : <strong>server.key</strong> and <strong>server.crt</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qpawKkoGimTi3DGxuLwLGw.png" /></figure><h4><strong>Create a connected app in Salesforce</strong></h4><p>To verify the JWT signature and control the level of access (or scopes) granted to the external app we <strong>create a connected app</strong> in Salesforce</p><ul><li>Open “Setup -&gt; Apps -&gt; App Manager -&gt; New Connected App”</li><li>Set the Name, API Name and contact Email</li><li>Enable OAuth Settings</li><li>Set the callback URL to <strong>sfdc://oauth/jwt/success</strong></li><li>Enable <strong>Use digital signatures </strong>and upload the digital certificate created in the previous step (<strong>server.crt</strong> file)</li><li>Selected OAuth Scopes : Access and manage your data <strong>(api)</strong> + Perform requests on your behalf at any time <strong>(refresh_token, offline_access)</strong></li><li>Save the connected app, it takes between 2 and 10 minutes to be activated.</li></ul><p>After saving the connected app, copy the <strong>Consumer key</strong> to use it in the next step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*COwjq96HLfJkn06dxn8X6g.png" /></figure><h4><strong>Pre-Approve the connected app with the User-Agent OAuth Flow</strong></h4><p>One way to pre-approve the connected is by using another simple OAuth Flow. We will use the User-Agent OAuth Flow in this example.</p><p>Copy and paste this link in the browser</p><pre>https://<strong>&lt;your instance&gt;</strong>.salesforce.com/services/oauth2/authorize?response_type=token&amp;client_id=<strong>&lt;consumer key&gt;</strong>&amp;redirect_uri=<strong>sfdc://oauth/jwt/success</strong></pre><p>Login to Salesforce and authorize the connected app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*eS2Fie0R_EcC20g2SilYRw.png" /></figure><h4>Build the JWT</h4><p>JWT Header :</p><pre>{<br>  &quot;alg&quot;: &quot;RS256&quot;,<br>  &quot;typ&quot;: &quot;JWT&quot;<br>}</pre><p>JWT claims :</p><pre>{<br>  &quot;iss&quot;: &quot;Consumer key&quot;,<br>  &quot;sub&quot;: &quot;<a href="/service/mailto:toufik.atba@gmail.com">U</a>sername&quot;,<br>  &quot;aud&quot;: &quot;<a href="https://login.salesforce.com/">https://&lt;login or test&gt;.salesforce.com</a>&quot;,<br>  &quot;exp&quot;: &quot;now + 2 minutes in Unix timestamp&quot;<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*nq7X_CptIhycihSWjWTWhg.png" /></figure><p>Base64 URL encode the Header and the Claims :</p><pre>jwt_part1 = Base64URLencode(JWT Header);<br>jwt_part2 = Base64URLencode(JWT Claims);</pre><p>Using the private key sign the encoded header and claims separated by a dot using SHA256 with RSA :</p><pre>jwt_signature = sign_sha256_RSA( jwt_part1+&quot;.&quot;+jwt_part2, &quot;private key&quot;)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/619/1*YW7YEkXXI1PfqZsr9P4bDg.png" /></figure><p>Build the final JWT assertion :</p><pre>jwt_assertion = jwt_part1+&quot;.&quot;+jwt_part2+&quot;.&quot;+jwt_signature</pre><p>POST the JWT assertion to Salesfoce Authorization Endpoint</p><pre>POST /services/oauth2/token HTTP/1.1<br>Host: &lt;your instance&gt;.salesforce.com<br>Content-Type: application/x-www-form-urlencoded</pre><pre><strong>grant_type</strong>=<em>urn:ietf:params:oauth:grant-type:jwt-bearer</em><strong>&amp;assertion</strong>=&lt;put the jwt assertion here&gt;<br></pre><p>The response should contain the access token :</p><pre>{<br>&quot;access_token&quot;: &quot;00DE0000000b....zcJW&quot;,<br>&quot;scope&quot;: &quot;api&quot;,<br>&quot;instance_url&quot;: &quot;https://toufik-dev-ed.my.salesforce.com&quot;,<br>&quot;id&quot;:&quot;https://login.salesforce.com/id/00DE.....MAI/005E00...IAA&quot;,<br>&quot;token_type&quot;: &quot;Bearer&quot;<br>}</pre><p>Working example with postman :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JKDgLe8Q9KnJBMuQdjcbjQ.png" /></figure><h4>Conclusion</h4><p>The JWT flow is widely used in the Salesforce ecosystem to enable external apps to access Salesforce data without user manual intervention. by sending a signed jwt to Salesforce we obtain an access token. The steps above should work for any programming language you external app is written on (java, node, python…)</p><p>More resources are available for this topic by Salesforce and the community :</p><ul><li><a href="https://help.salesforce.com/articleView?id=remoteaccess_oauth_jwt_flow.htm&amp;type=5">https://help.salesforce.com/articleView?id=remoteaccess_oauth_jwt_flow.htm&amp;type=5</a></li><li><a href="http://blog.deadlypenguin.com/blog/2019/03/08/jwt-bearer-auth-salesforce-node/">http://blog.deadlypenguin.com/blog/2019/03/08/jwt-bearer-auth-salesforce-node</a></li><li><a href="https://www.jitendrazaa.com/blog/salesforce/using-jwt-flow-to-authenticate-nodejs-application-with-salesforce/">https://www.jitendrazaa.com/blog/salesforce/using-jwt-flow-to-authenticate-nodejs-application-with-salesforce/</a></li><li><a href="https://gist.github.com/booleangate/30d345ecf0617db0ea19c54c7a44d06f">https://gist.github.com/booleangate/30d345ecf0617db0ea19c54c7a44d06f</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc70bfc626c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>