<?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 Rutuja Gupta on Medium]]></title>
        <description><![CDATA[Stories by Rutuja Gupta on Medium]]></description>
        <link>https://medium.com/@rutuja.chandrakant.gupta?source=rss-1b7c4d687245------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sLivydHnKbn28inCEPpmWg.jpeg</url>
            <title>Stories by Rutuja Gupta on Medium</title>
            <link>https://medium.com/@rutuja.chandrakant.gupta?source=rss-1b7c4d687245------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:34:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rutuja.chandrakant.gupta/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[Implementing One Way SSL for MuleSoft Application]]></title>
            <link>https://medium.com/@rutuja.chandrakant.gupta/implementing-one-way-ssl-for-mulesoft-application-28b02b6e2ac2?source=rss-1b7c4d687245------2</link>
            <guid isPermaLink="false">https://medium.com/p/28b02b6e2ac2</guid>
            <dc:creator><![CDATA[Rutuja Gupta]]></dc:creator>
            <pubDate>Sun, 15 Oct 2023 19:30:30 GMT</pubDate>
            <atom:updated>2023-10-15T19:32:21.068Z</atom:updated>
            <content:encoded><![CDATA[<p>One-way SSL authentication, also referred to as SSL/TLS client authentication, is a security protocol employed to create a secure connection between a client and a server. Within the framework of MuleSoft, a widely used integration platform, you can implement one-way SSL authentication to enhance the security of interactions between MuleSoft applications and external services.</p><ul><li>The server responds with a “ServerHello” message, along with its public certificate. This certificate is used to prove the server’s identity.</li><li>The client verifies the authenticity of the server’s public certificate. It checks if the certificate is signed by a trusted Certificate Authority (CA) and whether it’s still valid.</li><li>The client generates a random symmetric session key, encrypts it with the server’s public key from the certificate, and sends it to the server. This key will be used for secure data encryption and decryption during the session.</li><li>The server uses its private key to decrypt the symmetric session key sent by the client. Once decrypted, both the client and server have the same session key, allowing them to establish an encrypted channel for secure communication. The server acknowledges the successful decryption by sending a message to the client.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/1*OIHq5WV6WMQB2rMwlL_rzw.png" /></figure><p><strong>Implementation:</strong></p><ol><li><strong>Generate Server Keystore</strong></li></ol><pre>keytool -genkey -alias mule -keysize 2048 -keyalg RSA -keystore C:/Certificates/server-keystore.jks</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1sMc3CJt019OB3HsBHkiCA.png" /></figure><p>2. <strong>Export the Public Certificate From Server Keystore</strong></p><pre>keytool -export -alias mule-server -keystore C:/Certificates/server-keystore.jks -file C:/Certificates/server_public.crt</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qO7aNnQZjwBfCGa_bEsT5A.png" /></figure><p>3. <strong>Import Server Public Certificate Into Client Truststore</strong></p><pre>keytool -import -alias mule-client-public -keystore C:/Certificates/client-truststore.jks -file C:/Certificates/server_public.crt</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rHnts9BxiQRZmgOdi8lRDQ.png" /></figure><p><strong>4. Let’s explore how to set up Keystore and truststore configurations within the MuleSoft application.</strong></p><p>To begin, we’ll configure the server-Keystore for the MuleSoft HTTP Listener. In the General Settings, ensure that the Protocol is set to “HTTPS.” It’s crucial to place the server-Keystore.jks and client-truststore.jks files, generated in the previous steps, within the src/main/resources folder. This directory is where MuleSoft expects to find these security assets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/577/1*1QKDYAxlyeBbzlWInguYRQ.png" /></figure><p>Now, we will configure a TLS Key Store, specifying the Provider Type, Keystore Path, Keystore and Key Password, as well as the Alias Name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*_qYc-_TybidiLgOoFan44Q.png" /></figure><p>This configuration pertains to the server-side setup.</p><p>Next, let’s explore the client-side configuration. To achieve this, we’ll utilize the MuleSoft HTTP requester component. Here, you need to provide the connection settings within the HTTP requester configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*fbpFk_O5FDJwAib0F0XTcw.png" /></figure><blockquote>Happy Learning!!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28b02b6e2ac2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>