<?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 Dilan Lasantha on Medium]]></title>
        <description><![CDATA[Stories by Dilan Lasantha on Medium]]></description>
        <link>https://medium.com/@dilanchanukalasantha?source=rss-76d78636ef0a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FKaHd70ONwDX640t-sdEqA.jpeg</url>
            <title>Stories by Dilan Lasantha on Medium</title>
            <link>https://medium.com/@dilanchanukalasantha?source=rss-76d78636ef0a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:25:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dilanchanukalasantha/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[Configuring Azure AD as a Key Manager in WSO2 API Manager]]></title>
            <link>https://medium.com/@dilanchanukalasantha/configuring-azure-ad-as-a-key-manager-in-wso2-api-manager-fee2cf5b13ac?source=rss-76d78636ef0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/fee2cf5b13ac</guid>
            <category><![CDATA[external-key-manager]]></category>
            <category><![CDATA[api-security]]></category>
            <category><![CDATA[azure-active-directory]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[wso2-api-manager]]></category>
            <dc:creator><![CDATA[Dilan Lasantha]]></dc:creator>
            <pubDate>Mon, 17 Mar 2025 15:05:00 GMT</pubDate>
            <atom:updated>2025-03-17T15:05:00.649Z</atom:updated>
            <content:encoded><![CDATA[<p>Integrating Azure Active Directory (Azure AD) as a Key Manager in WSO2 API Manager (WSO2 APIM) allows organizations to utilize Microsoft’s identity management system for API security. This article provides a step-by-step guide on configuring Azure AD as a Key Manager and testing its integration with APIM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*PWaodJMhVjRhp0TCunXWRQ.png" /></figure><h3>Understanding Key Concepts</h3><h4>What is Azure Active Directory (Azure AD)?</h4><p>Azure Active Directory (Azure AD) is a cloud-based identity and access management service from Microsoft. It helps organizations authenticate users and manage access to various applications and services, including Microsoft 365, Azure resources, and external APIs.</p><h4>Role of a Key Manager in WSO2 API Manager</h4><p>In WSO2 API Manager, a Key Manager is responsible for handling security and access control by:</p><p>✅ Issuing and validating tokens to enforce API security policies.</p><p>✅ Managing authentication and authorization for API consumers.</p><p>✅ Integrating with external identity providers such as Azure AD, Keycloak, and Okta to enable centralized identity management.</p><p>WSO2 API Manager supports multiple Key Managers, allowing organizations to use different authorization servers. By default, WSO2 API Manager comes with an inbuilt resident Key Manager, but it also allows integration with external Key Managers using connectors.</p><p>To facilitate seamless integration with Azure AD, WSO2 API Manager provides the <a href="https://github.com/wso2-extensions/apim-km-azure-ad/">WSO2 API-M KM Azure AD Connector</a>, which enables out-of-the-box connectivity with Azure AD as a third-party Key Manager.</p><h3>Prerequisites</h3><p>Before getting started, ensure you have the following:</p><p>✔ An active Azure subscription with the necessary permissions to manage Azure AD applications. If you don’t have a subscription, you can sign up for a free trial to test and explore the concepts.</p><p>✔ WSO2 API Manager (4.0.0 or later) installed and running. You can download the latest version from the <a href="https://apim.docs.wso2.com/en/latest/">WSO2 official website</a>.</p><p>✔ An appropriate tool for API testing and validation.</p><h3>Step-by-Step Configuration Guide</h3><h4>Registering an Application in Azure AD</h4><ol><li>Sign in to the<a href="https://portal.azure.com/"> Azure portal</a>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*803U-89IxkaeeUdX" /></figure><p>2. Navigate to <strong>Azure Home → Microsoft Entra ID → App registrations → New registration</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8dOiga4ujUPWBQWo" /></figure><p>3. Enter an application name (e.g., “KeyManager Client”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gwlxDomnQfg98rMm" /></figure><p>4. Click <strong>Register</strong>.</p><h4>Generate a Client Secret</h4><ol><li>In the newly created application overview section, click <strong>‘Add a certificate or secret’</strong> under Client Credentials.</li><li>You will be redirected to the <strong>Certificates &amp; Secrets</strong> section.</li><li>Click <strong>New Client Secret</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IV4r07rBfswhP0ck" /></figure><p>4. Fill in the required details, select <strong>Custom</strong> as the expiration value, and set the start and end dates.</p><p>5. Click <strong>Add</strong>.</p><p>6. <strong>Copy the secret immediately</strong>, as it is only displayed once.</p><h4>Configuring API Permissions in Azure AD</h4><ol><li>Go to <strong>Permissions → Application registration</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Qj_ZyjoVJr48iN8J" /></figure><p>2. Click <strong>Add Permissions</strong> and select <strong>APIs my organization uses</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XmGtHBOdDLnrnNTJ" /></figure><p>3. Choose <strong>Microsoft Graph</strong> from the list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*htOwgqZnxjqQjB_N" /></figure><p>4. Click <strong>Application permissions</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/0*FcI28iGFpv6EIIXf" /></figure><p>5. Add the required permissions under <strong>Application</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/0*XTSnv95i_Y0qnPzZ" /></figure><p>6. Click <strong>Grant admin consent for Default Directory</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yU2EANLaVtIOkgan" /></figure><p>7. Ensure the permissions are successfully granted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NTx_DAqob2VWT-Ru" /></figure><h4>Copy Application Details</h4><ol><li>Navigate to <strong>Microsoft Entra ID → App registrations</strong>.</li><li>Select your newly created application under <strong>All Applications</strong>.</li><li>Click <strong>Endpoints</strong> and copy the following links:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3jfyMPXqGDyp6Y2c" /></figure><ul><li><strong>OAuth 2.0 token endpoint (v2)</strong></li><li><strong>OpenID Connect metadata document</strong></li><li><strong>Microsoft Graph API endpoint</strong></li></ul><p>4. Copy the <strong>Application (client) ID</strong> from the <strong>Overview</strong> section.</p><h3>Setting Up Azure AD as a Key Manager in WSO2 API Manager</h3><ol><li>Start the API Manager server and log in to the Admin portal at https://&lt;hostname&gt;:9443/admin.</li><li>Navigate to <strong>Key Managers</strong> → <strong>Add Key Manager</strong>.</li><li>Fill in the following details:</li></ol><ul><li><strong>Name</strong>: AzureAD</li><li><strong>Display Name</strong>: Azure AD Key Manager</li><li><strong>Key Manager Type</strong>: Azure AD</li><li><strong>Well-known URL</strong>: Paste the <strong>OpenID Connect metadata document</strong> URL from Azure and click <strong>Import</strong>. This will auto-fill some fields.</li><li><strong>Client Registration Endpoint</strong>: Microsoft Graph API endpoint</li><li><strong>Introspection Endpoint, Token Endpoint, Display Token Endpoint, Revoke Endpoint, Display Revoke Endpoint</strong>: OAuth 2.0 token endpoint (v2) for all the endpoints.</li><li><strong>Authorize Endpoint</strong>: <a href="https://login.microsoftonline.com/%7Btenant-id%7D/oauth2/v2.0/authorize">https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/authorize</a></li><li><strong>Grant Types</strong>: client_credentials (This is recommended in the <a href="https://apim.docs.wso2.com/en/4.3.0/administer/key-managers/configure-azure-ad-key-manager/">WSO2 documentation</a>, as using the password grant type may lead to scope validation issues when invoking APIM APIs. Therefore, client_credentials is the preferred option.)</li><li><strong>JWKS URL (for certificates)</strong>: <a href="https://login.microsoftonline.com/%7Btenant-id%7D/discovery/v2.0/keys">https://login.microsoftonline.com/{tenant-id}/discovery/v2.0/keys</a></li><li><strong>Connector Configurations → Microsoft Graph API Endpoint</strong>: Microsoft Graph API endpoint</li><li><strong>Microsoft Graph API Endpoint Version</strong>: v1.0</li><li><strong>Client ID</strong>: Paste the Application (client) ID</li><li><strong>Client Secret</strong>: Paste the generated client secret</li></ul><p><strong>4. Keep the rest of the fields with default values.</strong></p><p><strong>5. Ensure the Issuer is set correctly to validate access tokens.</strong> The default imported Issuer URL may be incorrect. It should be similar to this format: “<a href="https://sts.windows.net/%7Btenant-id%7D/">https://sts.windows.net/{tenant-id}/</a>”. Once you obtain a JWT token, verify this URL by decoding the JWT token and comparing the issuer of the token. The Issuer field and the JWT token issuer URL should be equal.</p><p>6. Click <strong>Add</strong>.</p><h4>Creating an Application &amp; Generating Keys</h4><ol><li>Navigate to the <strong>API Manager Developer Portal</strong>.</li><li>Go to the <strong>Applications</strong> section and click <strong>Add New Application</strong>.</li><li>Provide an application name and configure the parameters as required.</li><li>Go to the <strong>Production Keys</strong> section of the created application.</li><li>Select <strong>Azure AD Key Manager</strong> and click <strong>Generate Keys</strong>.</li></ol><h4>Testing the New Key Manager</h4><p>To test the new key manager, use the following <strong>cURL</strong> command to obtain an access token:</p><pre>curl --location &#39;https://login.microsoftonline.com/&lt;your-tenant&gt;/oauth2/v2.0/token&#39; \<br>--header &#39;Content-Type: application/x-www-form-urlencoded&#39; \<br>--header &#39;Authorization: Basic {base64-encoded-consumer-key-consumer-secret}&#39; \<br>--data-urlencode &#39;grant_type=client_credentials&#39; \<br>--data-urlencode &#39;scope=&lt;Application-ID&gt;/.default&#39;</pre><p>Alternatively, in <strong>Postman</strong>, configure <strong>Basic Auth</strong> for authentication using the <strong>Consumer Key</strong> and <strong>Consumer Secret</strong> of the application created in the Developer Portal under Azure AD Key Manager.</p><p>Once you obtain the access token, you can use it to invoke APIs published through WSO2 APIM.</p><h3>Final Thoughts</h3><p>Congratulations! You have successfully configured Azure AD as a Key Manager in WSO2 API Manager. This setup enables seamless authentication and authorization using Microsoft’s identity management system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fee2cf5b13ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Configuring Custom Host/Domain Names using Nginx for WSO2 API Manager]]></title>
            <link>https://medium.com/@dilanchanukalasantha/configuring-custom-host-domain-names-using-nginx-for-wso2-api-manager-79cd51e1e51a?source=rss-76d78636ef0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/79cd51e1e51a</guid>
            <category><![CDATA[custom-domain]]></category>
            <category><![CDATA[wso2-api-manager]]></category>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[hostname]]></category>
            <dc:creator><![CDATA[Dilan Lasantha]]></dc:creator>
            <pubDate>Thu, 13 Mar 2025 10:11:27 GMT</pubDate>
            <atom:updated>2026-03-25T13:33:39.519Z</atom:updated>
            <content:encoded><![CDATA[<p>This article guides you through configuring custom host/domain names for WSO2 API Manager using Nginx as a reverse proxy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a-zamf95UeyxZ1Xn1XhRxQ.png" /></figure><p>In this article, I will walk through the process of configuring custom hostnames for <strong>WSO2 API Manager (APIM) 4.4.0</strong>, which is a crucial step for creating a more user-friendly and secure environment. By setting up custom domain names and hiding port numbers, you can improve both the aesthetic and security aspects of your API Manager interface. This guide focuses on using Nginx as a reverse proxy server to achieve these goals, allowing you to easily customize your hostname and ensure seamless access to your APIM instance. <a href="https://apim.docs.wso2.com/en/latest/"><strong>You can download WSO2 API Manager from the official WSO2 website.</strong></a></p><p>Managing API endpoints and portals with custom domain names is essential for organizations looking to create a consistent and branded user experience, especially when deploying production-ready API Management solutions. The flexibility of Nginx allows you to configure SSL, load balancing, and proxying to efficiently route traffic without exposing internal ports.</p><p>This article is divided into two key sections:</p><ol><li><strong>Custom hostname configuration to hide the ports and add a custom domain name</strong>: In this section, I will explore how to set up a custom hostname and hide port numbers to ensure that your API Manager’s endpoint remains clean and professional.</li><li><strong>Configuring custom domain names for APIM portals</strong>: This section will guide you through the steps needed to assign custom domain names to the APIM Publisher and Developer portals, providing a better user experience for both developers and API consumers.</li></ol><p>By the end of this article, you will have a fully functional setup with custom hostnames for both your WSO2 API Manager and its associated portals, secured with SSL and ready for production deployment.</p><h3><strong>Custom Hostname Configuration to Hide the Ports and Add a Custom Domain Name</strong></h3><h4>Step 1: Modify deployment.toml</h4><p>📂 <strong>File Path:</strong> &lt;APIM_HOME&gt;/repository/conf/deployment.toml</p><p>In the deployment.toml file, you need to define the custom hostname and enable proxy settings.</p><pre>[server]<br>hostname = &quot;dev.local&quot;  # Your custom domain name<br><br>[transport.https.properties]<br>proxy_enabled = true<br>proxyPort = 443  # Standard HTTPS port</pre><h4>Step 2: Update Nginx Configuration</h4><p>Modify the nginx.conf file to set up reverse proxy rules for WSO2 APIM:</p><p>📂 <strong>File Path:</strong> /opt/homebrew/etc/nginx/nginx.conf (or the relevant location based on your installation)</p><pre>http {<br>    include       mime.types;<br>    default_type  application/octet-stream;<br>    sendfile        on;<br>    keepalive_timeout  65;<br><br>    upstream sslapi.am.wso2.com {<br>        server localhost:9443;  #WSO2 APIM Server(9443 - Default port)<br><br>    }<br><br>    upstream sslgw.am.wso2.com {<br>        server localhost:8243; #WSO2 APIM Server&#39;s default GW port - 8243)<br>    }<br><br>    server {<br>        listen 80;<br>        server_name dev.local;  # Custom domain<br>        rewrite ^/(.*) https://dev.local/$1 permanent;<br>    }<br><br>    server {<br>        listen 443 ssl;<br>        server_name dev.local;<br>        proxy_set_header X-Forwarded-Port 443;<br>        ssl_certificate /opt/homebrew/etc/nginx/ssl/newcert.crt;<br>        ssl_certificate_key /opt/homebrew/etc/nginx/ssl/newcert.key;<br>        location / {<br>            proxy_set_header X-Forwarded-Host $host;<br>            proxy_set_header X-Forwarded-Server $host;<br>            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<br>            proxy_set_header Host $http_host;<br>            proxy_read_timeout 5m;<br>            proxy_send_timeout 5m;<br>            proxy_pass https://sslapi.am.wso2.com;<br>        }<br>    }<br>    server {<br>        listen 443 ssl;<br>        server_name gw.am.wso2.com;<br>        proxy_set_header X-Forwarded-Port 443;<br>        ssl_certificate /opt/homebrew/etc/nginx/ssl/newcert.crt;<br>        ssl_certificate_key /opt/homebrew/etc/nginx/ssl/newcert.key;<br>        location / {<br>            proxy_set_header X-Forwarded-Host $host;<br>            proxy_set_header X-Forwarded-Server $host;<br>            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<br>            proxy_set_header Host $http_host;<br>            proxy_read_timeout 5m;<br>            proxy_send_timeout 5m;<br>            proxy_pass https://sslgw.am.wso2.com;<br>        }<br>    }<br>}</pre><p>After completing these steps, your <strong>servlet transport</strong> will use the dev.local domain name, ensuring that all API Manager-related services are accessible through this custom hostname. Meanwhile, gw.am.wso2.com will utilize <strong>passthrough transport</strong>, allowing API requests to be securely routed through the gateway without direct exposure to backend services.</p><h3><strong>Configuring Custom Domain Names for APIM Portals</strong></h3><p>WSO2 API Manager allows configuring custom domain names for the APIM portals to make them more accessible and fit into your existing domain infrastructure.</p><p>For more detailed guidance on configuring custom domain names for the APIM portals, I recommend reading the Medium article<a href="https://medium.com/@kds.madhusanka/configuring-wso2-api-manager-portals-for-multi-domain-access-in-kubernetes-d40bd686eef0"> “Configuring WSO2 API Manager Portals for Multi-Domain Access in Kubernetes”</a> by <a href="https://medium.com/@kds.madhusanka">Sajith Madhusanka</a>. This article explains, step by step, how to set up multi-domain access using Nginx ingress configurations in a Kubernetes environment. I have referenced this article for its in-depth insights, so you can use it as a detailed guide to further enhance your understanding of the process.</p><p>In this article, I will use Nginx for the reverse proxy and continue the guide, focusing on configuring custom domain names for APIM portals in a single node environment.</p><h4>Step 1: Modify deployment.toml</h4><p>Update the deployment.toml file to reflect the custom domain names for the portals:</p><p>📂 <strong>File Path:</strong> &lt;APIM_HOME&gt;/repository/conf/deployment.toml</p><pre>[server]<br>hostname = &quot;dev.local&quot;  # Custom domain for APIM server<br><br>[transport.https.properties]<br>proxy_enabled = true<br>proxyPort = 443<br><br>[apim.devportal]<br>url = &quot;https://devportal.local/devportal&quot;<br><br>[apim.idp]<br>server_url = &quot;https://dev.local/&quot;<br>authorize_endpoint = &quot;https://dev.local/oauth2/authorize&quot;<br>oidc_logout_endpoint = &quot;https://dev.local/oidc/logout&quot;<br>oidc_check_session_endpoint = &quot;https://dev.local/oidc/checksession&quot;</pre><p>⚠️ <strong>Important Note:</strong> Make sure to configure [apim.idp] to avoid “Invalid URL redirection” errors during login.</p><h4>Step 2: Configure Callback URLs</h4><p>Add the callback URLs for the Developer Portal and Publisher Portal to the Service Providers:</p><p><strong>Log in to WSO2 Management Console</strong></p><ul><li>Open a browser and navigate to:<br> 📌 https://&lt;your-apim-host&gt;/carbon/</li><li>Enter admin credentials (default: <strong>admin/admin</strong>).</li></ul><p><strong>Navigate to Service Providers</strong></p><ul><li>In the <strong>Management Console</strong>, go to <strong>Service Providers</strong> under the <strong>Identity</strong> section.</li><li>Find the service providers for <strong>Developer Portal</strong> and <strong>Publisher Portal</strong>.</li></ul><p><strong>Configure OAuth2/OpenID Connect</strong></p><ul><li>Click on the <strong>OAuth/OpenID Connect Configuration</strong> section.</li><li>Click <strong>Configure</strong> to open the OAuth settings.</li></ul><p><strong>Add Callback URLs</strong></p><p>In the <strong>Callback URL field</strong>, enter the required regex pattern for each portal:</p><ul><li><strong>Developer Portal:</strong></li></ul><pre>regexp=(https://devportal.local/devportal/services/auth/callback/login|https://devportal.local/devportal/services/auth/callback/logout)</pre><ul><li><strong>Publisher Portal:</strong></li></ul><pre>regexp=(https://publisher.local/publisher/services/auth/callback/login|https://publisher.local/publisher/services/auth/callback/logout)</pre><p><strong>Save the Configuration</strong></p><p>Click <strong>Update</strong> to save changes.</p><h4>Step 3: Modify settings.json</h4><p>Update the settings.json files for both the Developer Portal and Publisher Portal:</p><p>📂 <strong>File Path:</strong> &lt;APIM_HOME&gt;/repository/deployment/server/webapps/devportal/site/public/theme/settings.json</p><p>📂 <strong>File Path:</strong> &lt;APIM_HOME&gt;/repository/deployment/server/webapps/publisher/site/public/conf/settings.json</p><pre>&quot;customUrl&quot;: {<br>  &quot;enabled&quot;: true,<br>  &quot;forwardedHeader&quot;: &quot;X-Forwarded-Host&quot;<br>},<br>&quot;singleLogout&quot;: {<br>  &quot;enabled&quot;: false<br>}</pre><p>The “<strong>X-Forwarded-Host</strong>” header is important because it ensures the API Manager portals recognize and resolve the correct custom domain when accessed through a reverse proxy like Nginx.</p><h4>Step 4: Configure Keystores</h4><p>Configure the <strong>wso2carbon.jks</strong> and <strong>client-truststore.jks</strong> keystores accordingly. You can refer to the <a href="https://apim.docs.wso2.com/en/latest/install-and-setup/setup/security/configuring-keystores/keystore-basics/creating-new-keystores/">Creating Keystores documentation</a> for detailed instructions on this step.</p><p>After configuring the keystores with the new DNS names, the wso2carbon alias certificate in wso2carbon.jks and client-truststore.jks should have the following SubjectAlternativeNames to ensure proper use of the new custom domain names.</p><p>📂 <strong>File Path:</strong> &lt;APIM_HOME&gt;/repository/resources/security/wso2carbon.jks</p><p>📂 <strong>File Path:</strong> &lt;APIM_HOME&gt;/repository/resources/security/client-truststore.jks</p><pre>SubjectAlternativeName [<br>  DNSName: dev.local<br>  DNSName: devportal.local<br>  DNSName: publisher.local<br>  DNSName: localhost<br>]</pre><h4>Step 5: Update Nginx Configuration</h4><p>Update the nginx.conf file to handle the reverse proxy for each of the custom domains:</p><p>📂 <strong>File Path:</strong> /opt/homebrew/etc/nginx/nginx.conf (or the relevant location based on your installation)</p><pre>http {<br>    include       mime.types;<br>    default_type  application/octet-stream;<br>    sendfile        on;<br>    keepalive_timeout  65;<br><br>    upstream sslapi.am.wso2.com {<br>        server localhost:9443;<br>    }<br><br>    upstream sslgw.am.wso2.com {<br>        server localhost:8243;<br>    }<br><br>    server {<br>        listen 80;<br>        server_name dev.local;<br>        rewrite ^/(.*) https://dev.local/$1 permanent;<br>    }<br><br>    server {<br>        listen 443 ssl;<br>        server_name dev.local;<br>        proxy_set_header X-Forwarded-Port 443;<br>        ssl_certificate /opt/homebrew/etc/nginx/ssl/newcert.crt;<br>        ssl_certificate_key /opt/homebrew/etc/nginx/ssl/newcert.key;<br>        location / {<br>            proxy_set_header X-Forwarded-Host $host;<br>            proxy_set_header X-Forwarded-Server $host;<br>            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<br>            proxy_set_header Host $http_host;<br>            proxy_read_timeout 5m;<br>            proxy_send_timeout 5m;<br>            proxy_pass https://sslapi.am.wso2.com;<br>        }<br>    }<br><br>    server {<br>        listen 443 ssl;<br>        server_name gw.am.wso2.com;<br>        proxy_set_header X-Forwarded-Port 443;<br>        ssl_certificate /opt/homebrew/etc/nginx/ssl/newcert.crt;<br>        ssl_certificate_key /opt/homebrew/etc/nginx/ssl/newcert.key;<br>        location / {<br>            proxy_set_header X-Forwarded-Host $host;<br>            proxy_set_header X-Forwarded-Server $host;<br>            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<br>            proxy_set_header Host $http_host;<br>            proxy_read_timeout 5m;<br>            proxy_send_timeout 5m;<br>            proxy_pass https://sslgw.am.wso2.com;<br>        }<br>    }<br><br>    server {<br>        listen 443 ssl;<br>        server_name devportal.local;<br>        ssl_certificate /opt/homebrew/etc/nginx/ssl/newcert.crt;<br>        ssl_certificate_key /opt/homebrew/etc/nginx/ssl/newcert.key;<br>        location / {<br>            proxy_set_header X-Forwarded-Host $host;<br>            proxy_set_header X-Forwarded-Server $host;<br>            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<br>            proxy_set_header Host $http_host;<br>            proxy_read_timeout 5m;<br>            proxy_send_timeout 5m;<br>            proxy_pass https://sslapi.am.wso2.com/;<br>        }<br>    }<br><br>    server {<br>        listen 443 ssl;<br>        server_name publisher.local;<br>        ssl_certificate /opt/homebrew/etc/nginx/ssl/newcert.crt;<br>        ssl_certificate_key /opt/homebrew/etc/nginx/ssl/newcert.key;<br>        location / {<br>            proxy_set_header X-Forwarded-Host $host;<br>            proxy_set_header X-Forwarded-Server $host;<br>            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<br>            proxy_set_header Host $http_host;<br>            proxy_read_timeout 5m;<br>            proxy_send_timeout 5m;<br>            proxy_pass https://sslapi.am.wso2.com/;<br>        }<br>    }<br>}</pre><h4>Step 6: Verify Configuration</h4><p>After completing the configuration, verify the setup:</p><ul><li>Carbon Console: <a href="https://dev.local/carbon/">https://dev.local/carbon/</a></li><li>Developer Portal: <a href="https://devportal.local/devportal">https://devportal.local/devportal</a></li><li>Publisher Portal: <a href="https://publisher.local/publisher">https://publisher.local/publisher</a></li></ul><p>The portals will use the above-mentioned URLs, with gw.am.wso2.com utilizing passthrough transport to securely route API requests through the gateway without exposing backend services directly.</p><p>Note: If you’re testing this setup in a local environment, you may need to add the hostname mapping to the hosts file (/etc/hosts) to ensure the custom domain resolves correctly.</p><h3>Conclusion</h3><p>In conclusion, configuring custom hostnames and domain names for WSO2 API Manager using Nginx enhances both security and user experience. By hiding internal ports and creating cleaner, more professional URLs, you can ensure seamless access to the API Manager and its portals. With the added flexibility of SSL, load balancing, and reverse proxy features, your setup will be secure and optimized for production environments. Following the steps outlined ensures a robust configuration that aligns with best practices for managing API endpoints and portals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79cd51e1e51a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decoding Life: How Bioinformatics Bridges Biology and AI]]></title>
            <link>https://medium.com/@dilanchanukalasantha/decoding-life-how-bioinformatics-bridges-biology-and-ai-ca4ff25bab64?source=rss-76d78636ef0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca4ff25bab64</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[bioinformatics]]></category>
            <dc:creator><![CDATA[Dilan Lasantha]]></dc:creator>
            <pubDate>Sat, 01 Mar 2025 20:08:45 GMT</pubDate>
            <atom:updated>2025-03-17T14:43:51.317Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In the intricate dance of life’s code, bioinformatics emerges as the key to deciphering the language of DNA, bridging the gap between biology and artificial intelligence to unlock the mysteries of our genetic blueprint.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I9XqgxoFVHDlPb0mr6mrlQ.jpeg" /></figure><p>We are living in an era where data-driven discoveries are revolutionizing how we understand life itself. From decoding the human genome to designing AI-powered drug discovery pipelines, <strong>bioinformatics</strong> has emerged as the bridge between biology and computation.</p><p>The vast amount of biological data generated daily requires sophisticated computational methods to analyze and interpret it. This is where bioinformatics plays a pivotal role — bringing together molecular biology, artificial intelligence, and big data analytics to uncover hidden patterns in biological systems.</p><h3>The Foundation of Bioinformatics</h3><p>At its core, bioinformatics is a multidisciplinary field that applies computational tools to biological questions. The main branches of bioinformatics include:</p><p>🔬 <strong>Genomics</strong> — The study of entire genomes, helping us understand genetic variations, hereditary diseases, and evolutionary relationships.<br>🧬 <strong>Proteomics</strong> — Investigating protein structures and interactions to decode their functions in cells.<br>📊 <strong>Transcriptomics</strong> — Analyzing gene expression to reveal how cells respond to different conditions.<br>🔄 <strong>Systems Biology</strong> — Modeling biological pathways and networks to predict cellular behavior.<br>🌱 <strong>Metagenomics</strong> — Studying microbial communities in environments like the human gut, soil, and oceans.</p><p>With advancements in <strong>high-throughput sequencing</strong>, we can now analyze entire genomes in hours, leading to breakthroughs in medicine, agriculture, and environmental science.</p><h3>The Role of AI in Bioinformatics</h3><p>Artificial intelligence has become a transformative force in bioinformatics, offering unprecedented precision in analyzing vast and complex biological datasets. By leveraging machine learning algorithms, researchers can decode intricate genetic patterns and uncover relationships that were previously difficult to detect. These AI-driven approaches are accelerating breakthroughs in various domains:</p><ul><li><strong>Predicting disease-related mutations:</strong> AI models analyze genomic sequences to identify genetic variants linked to diseases, enabling early diagnosis and personalized treatment strategies.</li><li><strong>Identifying drug-target interactions:</strong> Machine learning helps predict how different molecules interact with biological targets, streamlining drug discovery and reducing the time and cost of developing new therapies.</li><li><strong>Detecting regulatory elements:</strong> AI enhances the identification of functional elements in DNA, RNA, and proteins, improving our understanding of gene expression and cellular regulation.</li><li><strong>Classifying cancer subtypes:</strong> Deep learning techniques analyze gene expression profiles to categorize cancer types with high accuracy, aiding in precise treatment selection and advancing precision medicine.</li></ul><p>As AI continues to evolve, its integration into bioinformatics is reshaping the way we understand, diagnose, and treat diseases, bringing us closer to a future of data-driven, personalized healthcare.</p><h3>Applications of Bioinformatics in Healthcare</h3><p>Bioinformatics is reshaping the medical field with applications such as:</p><p>🧑‍⚕️ <strong>Personalized Medicine</strong> — Tailoring treatments based on an individual’s genetic makeup, leading to more effective and targeted therapies.<br>💊 <strong>Drug Discovery &amp; Development</strong> — Using AI to design new drugs and repurpose existing ones, reducing development costs and timelines.<br>🦠 <strong>Infectious Disease Surveillance</strong> — Tracking viral mutations (e.g., COVID-19) to predict outbreaks and guide vaccine development.<br>🧬 <strong>Cancer Genomics</strong> — Identifying biomarkers for early cancer detection and targeted therapy.</p><p>Bioinformatics is transforming healthcare by providing data-driven insights into disease prevention and treatment. With personalized medicine, it enables tailored therapies based on an individual’s genetic profile, improving treatment outcomes. In drug discovery, bioinformatics speeds up the identification of potential drugs, reducing costs and timeframes. It also plays a crucial role in infectious disease surveillance, helping track mutations and predict outbreaks. In cancer genomics, it aids in early detection and the development of targeted treatments, ultimately leading to more effective and precise healthcare solutions.</p><h3>Challenges and Future Directions</h3><p>Despite its vast potential, bioinformatics faces key challenges:</p><p>⚠️ <strong>Big Data Management</strong> — The sheer volume of biological data requires efficient storage, processing, and retrieval systems.<br>⚠️ <strong>Model Interpretability</strong> — Many AI models operate as “black boxes,” making it difficult to interpret their predictions in biological contexts.<br>⚠️ <strong>Computational Resources</strong> — Advanced bioinformatics applications demand high-performance computing power, which may not be accessible in all research settings.</p><p>The future of bioinformatics will likely be driven by <strong>quantum computing, federated learning, and explainable AI</strong>, allowing for more efficient and transparent data analysis. The integration of these technologies will push the boundaries of what’s possible in genomics, drug discovery, and precision medicine.</p><h3>Final Thoughts</h3><p>Bioinformatics is more than just a tool — it is a <strong>revolution in biological research</strong>, enabling us to decode the fundamental principles of life. As AI and computational power continue to evolve, bioinformatics will remain at the forefront of scientific innovation, shaping the future of medicine, agriculture, and beyond.</p><p>If you’re intrigued by the potential of bioinformatics and how it intersects with cutting-edge AI, I invite you to explore our research. We focus on leveraging ensemble deep learning models to uncover valuable insights in genetic data, particularly in the prediction of binding sites. Feel free to refer to our publications for a deeper dive into how these innovative approaches are shaping the future of bioinformatics.</p><ol><li><a href="https://www.sciencedirect.com/science/article/abs/pii/S001048252400550X"><strong>CRIECNN: Ensemble convolutional neural network and advanced feature extraction methods for the precise forecasting of circRNA-RBP binding sites</strong></a> — A study on ensemble deep learning models for circRNA-RBP binding site prediction.</li><li><a href="https://www.sciencedirect.com/science/article/abs/pii/S0952197623005365"><strong>Deep learning and ensemble deep learning for circRNA-RBP interaction prediction in the last decade: A review</strong> </a>— A comprehensive review discussing bioinformatics techniques and their applications in AI-driven research.</li></ol><h3>References</h3><ul><li><a href="https://www.sciencedirect.com/science/article/abs/pii/S001048252400550X">Lasantha, D., Vidanagamachchi, S. and Nallaperuma, S., 2024. CRIECNN: Ensemble convolutional neural network and advanced feature extraction methods for the precise forecasting of circRNA-RBP binding sites. <em>Computers in biology and medicine</em>, <em>174</em>, p.108466.</a></li><li><a href="https://www.sciencedirect.com/science/article/abs/pii/S0952197623005365">Lasantha, D., Vidanagamachchi, S. and Nallaperuma, S., 2023. Deep learning and ensemble deep learning for circRNA-RBP interaction prediction in the last decade: A review. <em>Engineering Applications of Artificial Intelligence</em>, <em>123</em>, p.106352.</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca4ff25bab64" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>