<?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 Kajal Katoke on Medium]]></title>
        <description><![CDATA[Stories by Kajal Katoke on Medium]]></description>
        <link>https://medium.com/@kajal_24040?source=rss-f0feef935980------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Kajal Katoke on Medium</title>
            <link>https://medium.com/@kajal_24040?source=rss-f0feef935980------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:44:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kajal_24040/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 OAuth2 Token Exchange Grant Between Asgardeo and WSO2 API Manager 4.5.0]]></title>
            <link>https://medium.com/@kajal_24040/configuring-oauth2-token-exchange-grant-between-asgardeo-and-wso2-api-manager-4-5-0-2a5e041b3990?source=rss-f0feef935980------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a5e041b3990</guid>
            <category><![CDATA[token-exchange-grant-type]]></category>
            <category><![CDATA[jwt-token]]></category>
            <category><![CDATA[token-exchange]]></category>
            <category><![CDATA[asgardeo-as-km]]></category>
            <category><![CDATA[jwks-endpoint]]></category>
            <dc:creator><![CDATA[Kajal Katoke]]></dc:creator>
            <pubDate>Sun, 14 Jun 2026 09:11:54 GMT</pubDate>
            <atom:updated>2026-06-18T14:30:21.611Z</atom:updated>
            <content:encoded><![CDATA[<h3>Configuring OAuth2 Token Exchange Grant Between Asgardeo and WSO2 API Manager 4.5.0 — <strong>A Practical Guide</strong></h3><h3>Introduction</h3><p>If you’ve ever worked with <strong>WSO2 API Manager (APIM)</strong>, you already know it ships with its own built-in OAuth2 authorization server — the <strong>Resident Key Manager</strong>. It’s great for getting started fast. But the moment your organization adopts a dedicated <strong>Identity as a Service (IDaaS)</strong> platform like <strong>Asgardeo or Identity server</strong>, a very natural question pops up:</p><blockquote><em>“My users already log in via Asgardeo and get a token from there… do they now need to log in again to APIM just to call an API? 🤦”</em></blockquote><p>Thankfully — no 🙂<br>That’s exactly the problem the <strong>OAuth 2.0 Token Exchange Grant (RFC 8693)</strong> solves. In this post, we’ll go from the absolute basics (what Asgardeo is, what a Resident Key Manager is) all the way to a working, end-to-end configuration where an <strong>Asgardeo-issued JWT gets exchanged for an APIM access token</strong> with real configs, and a test flow. 🚀</p><p>By the end of this article, you’ll be able to:</p><ul><li>✅ Understand Asgardeo’s role as an external IdP</li><li>✅ Understand APIM’s Resident Key Manager and why it still matters</li><li>✅ Enable the Token Exchange grant type in APIM</li><li>✅ Register Asgardeo as a Key Manager in APIM (exchange tokens method)</li><li>✅ Run the full token exchange flow end-to-end with curl</li></ul><p>Grab your coffee ☕ — let’s get into it.</p><h3>Part 1: What is Asgardeo?</h3><p><strong>Asgardeo</strong> is WSO2’s AI-powered cloud-native <strong>Identity as a Service (IDaaS)<br></strong>platform. Think of it as “Identity Server, but hosted, managed, and ready in minutes.” It gives you:</p><ul><li>🔑 OAuth2 / OpenID Connect / SAML2 based login flows</li><li>👥 User and group management</li><li>🌐 Social and federated login</li><li>🔐 Risk-adaptive, multi-factor authentication, Passwordless authentication</li><li>Conditional authentication</li><li>SSO integration</li><li>🧩 SDKs for React, Node.js, Java, .NET, and more</li><li>📜 Fine-grained API authorization with scopes and User impersonation</li></ul><p>and many more facilities<br>In short — Asgardeo becomes the <strong>single source of truth for “who is this user, and what are they allowed to do?”</strong></p><p>In API security terms, Asgardeo can act purely as an <strong>OAuth2 token service</strong>: it authenticates the user and issues tokens, while a separate API management layer (APIM, in our case) enforces authorization on the API side. This is a very common pattern for organizations that want <strong>centralized identity management</strong> across many apps and APIs.</p><h3>Part 2: WSO2 API Manager and its Resident Key Manager</h3><p>Now let’s talk about APIM. WSO2 API Manager is the platform that lets you <strong>design, publish, secure, and manage APIs</strong> — complete with a Developer Portal where consumers can discover APIs, subscribe to them, and generate keys.</p><p>WSO2 API Manager is a complete platform for building, integrating, and exposing your digital services as managed APIs in the cloud, on-premises, and hybrid architectures to drive your digital transformation strategy.</p><p>It allows API developers to design, publish, and manage the lifecycle of APIs and API product managers to create API products from one or more APIs.</p><p>Every APIM instance comes bundled with a <strong>Resident Key Manager, </strong>its own built-in authorization server. It handles authentication, authorization, and token management natively The Resident KM :</p><ul><li>Issues access tokens used to invoke APIs through the APIM gateway</li><li>Lets you create OAuth applications directly from the Developer Portal</li></ul><p>Here’s the important bit 👇 Even when you bring in an external IdP like Asgardeo, <strong>the Resident Key Manager doesn’t disappear</strong> , in the Token Exchange scenario, it actually plays a starring role, because it’s the resident km that ultimately <em>issues</em> the token your client uses to call the API.</p><h3>Part 3: What is the Token Exchange Grant Type?</h3><p>The <strong>OAuth 2.0 Token Exchange grant</strong> (defined in<a href="https://datatracker.ietf.org/doc/html/rfc8693"> RFC 8693</a>) defines a standard way for a client to present a token issued by <strong>one authorization server</strong> and receive, in return, a token issued by <strong>a different authorization server</strong>.</p><p>This is <em>the</em> pattern for federated identity scenarios where:</p><ul><li>👤 Users authenticate against an <strong>external IdP</strong> (Asgardeo, WSO2 IS, Keycloak, Azure AD, etc.)</li><li>🛡️ APIs are fronted and protected by <strong>WSO2 API Manager</strong></li><li>🔁 You need to <strong>exchange</strong> the external token for an <strong>APIM-issued token</strong> to actually invoke those APIs</li></ul><blockquote><strong>The grant type identifier<br></strong>grant_type=urn:ietf:params:oauth:grant-type:token-exchange</blockquote><h3>The high-level flow</h3><ol><li>The user authenticates with <strong>Asgardeo</strong> and receives a <strong>JWT access token</strong>.</li><li>The client sends that JWT to <strong>APIM’s /oauth2/token endpoint</strong>, using the token-exchange grant type, along with credentials of an application registered against APIM’s <strong>Resident Key Manager</strong>.</li><li>APIM <strong>validates</strong> the incoming Asgardeo JWT — using the Key Manager configuration you registered (signature check via JWKS, issuer check, etc.).</li><li>APIM issues a <strong>new access token</strong> from its <strong>Resident Key Manager</strong>.</li><li>The client uses this new APIM token to <strong>invoke the protected API</strong> through the gateway.</li></ol><p><strong>The diagram below explains the complete flow we’re trying to achieve here:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nzyNnbfAyNjgWF7BwNyIiQ.png" /></figure><h3>Part 4: Direct Tokens vs Exchange Tokens — know the difference!</h3><p>When you register a third-party IdP as a Key Manager in APIM’s Admin Portal, you’ll be asked to choose an <strong>API invocation method</strong>:<br><strong>Direct Token:</strong> The token issued by the external IdP (e.g., Asgardeo) is used as-is to invoke APIs through the gateway</p><p><strong>Exchange tokens:</strong> The IdP-issued token is exchanged for an APIM-issued token (via Token Exchange grant), and that token is used to invoke APIs|</p><p>This article focuses on the <strong>Exchange tokens</strong> approach, it keeps your Resident Key Manager as the single issuer of tokens that the gateway trusts, while Asgardeo remains your identity source of truth.</p><h3>Part 5: Step-by-Step Configuration</h3><p>Alright, hands on keyboard time! 💻 Here’s the full setup.</p><h3>Prerequisites</h3><ul><li>WSO2 API Manager <strong>4.5.0</strong> up and running</li><li>An <strong>Asgardeo organization</strong> (free tier works fine — sign up at<a href="https://wso2.com/asgardeo/"> asgardeo.io</a>)</li><li>🌐 Network connectivity between your APIM instance and <a href="https://api.asgardeo.io/">https://api.asgardeo.io</a></li></ul><h3>Step 1 — Enable the Token Exchange grant in APIM</h3><p>Verify if The Token Exchange grant type is enabled by checking below config in deployement.toml if not add below config in deployment.toml (located at &lt;APIM_HOME&gt;/repository/conf/):</p><pre>[oauth.grant_type.token_exchange]<br>enable = true<br>allow_refresh_tokens = true<br>iat_validity_period = &quot;1h&quot;</pre><p>Restart APIM after this change. 🔄</p><h3>Step 2 — Create an application in Asgardeo</h3><ol><li>Log in to the <strong>Asgardeo Console</strong>: <a href="https://console.asgardeo.io/">https://console.asgardeo.io</a></li><li>Go to <strong>Applications</strong> → <strong>New Application</strong> → choose <strong>Standard-Based Application</strong> and select OpenID Connect as protocol</li><li>Give it a name — e.g., apim-token-exchange-client</li><li>Under the <strong>Protocol</strong> tab:</li></ol><ul><li>Note down the <strong>Client ID</strong> and <strong>Client Secret</strong></li><li>Make sure the appropriate <strong>Allowed Grant Types</strong> are enabled (e.g., Client Credentials, password or Authorization Code if real users will log in)</li><li>Ensure tokens are issued as <strong>JWT</strong></li><li>Click <strong>Update</strong> to save.</li></ul><p>This is the application your end users (or test clients) will authenticate against to get their initial Asgardeo-issued JWT.</p><h3>Step 3 — Get a JWT from Asgardeo</h3><p>Before touching APIM, confirm you can get a token from Asgardeo:<br>Curl for Client credential Grants type:</p><p>Curl for client-credential grant type:</p><pre>curl -v -k -X POST https://api.asgardeo.io/t/&lt;organization_name&gt;/oauth2/token \<br> - header &quot;Authorization: Basic &lt;Base64Encoded(ASGARDEO_CLIENT_ID:ASGARDEO_CLIENT_SECRET)&gt;&quot; \<br> - header &quot;Content-Type:application/x-www-form-urlencoded&quot; \<br> - data-urlencode &quot;grant_type=client_credentials&quot; \<br> - data-urlencode &quot;scope=&lt;scopes&gt;&quot;</pre><p>Curl for password grant type:</p><pre>curl -v -k -X POST https://api.asgardeo.io/t/organizationone/oauth2/token \<br> - header &quot;Authorization: Basic &lt;Base64Encoded(ASGARDEO_CLIENT_ID:ASGARDEO_CLIENT_SECRET)&gt;&quot; \<br> - header &quot;Content-Type:application/x-www-form-urlencoded;charset=UTF-8&quot; \<br> - data-urlencode &quot;grant_type=password&quot; \<br> - data-urlencode &quot;username=&lt;USERNAME&gt;&quot; \<br> - data-urlencode &quot;password = &lt;PASSWORD&gt;&quot; \<br> - data-urlencode &quot;scope=openid&quot;</pre><p>Expected response:</p><pre>{<br>&quot;access_token&quot;: &quot;eyJ4NXQiOiJNe…&quot;,<br>&quot;Scope&quot; : &quot;&lt;SCOPES&gt;&quot;<br>&quot;id_token&quot; : &quot;eyJ4NXQiO…&quot;<br>&quot;token_type&quot;: &quot;Bearer&quot;,<br>&quot;expires_in&quot;: 3600,<br>}</pre><p>Save this access_token — it’s the <strong>subject_token</strong> we’ll exchange in Step 6. ✅</p><h3>Step 4 — Register Asgardeo as a Key Manager in APIM</h3><p>This is the crucial step that teaches APIM how to <strong>validate</strong> incoming Asgardeo tokens.</p><ol><li>Log in to the <strong>APIM Admin Portal</strong>: https://&lt;APIM_HOST&gt;:&lt;PORT&gt;/admin</li><li>Navigate to <strong>Key Managers</strong> → <strong>Add Key Manager</strong></li><li>Fill in the details:</li></ol><blockquote><strong>Name :</strong> Asgardeo<br><strong>Display Name</strong>: Asgardeo IDaas<br><strong>Key Manager:</strong> WSO2 Identity Server 7 OR other<br><strong>API Invocation Method:</strong> Exchange tokens ✅|<br><strong>Allowed Token Audience:</strong> This should be client ID of application created on asgardeo(in step2)|<br><strong>Well-Known URL :</strong> <em>https://api.asgardeo.io/t/&lt;your-org-name&gt;/oauth2/token/.well-known/openid-configuration</em></blockquote><ol><li>Click <strong>Import</strong> — APIM will auto-fetch the issuer, token endpoint, JWKS endpoint, and other metadata from Asgardeo’s discovery document.</li><li>In the <strong>Certificates</strong> section, either:</li></ol><ul><li>Paste Asgardeo’s signing certificate, <strong>or</strong></li><li>Point to the <strong>JWKS endpoint</strong></li></ul><p>3. Click <strong>Add</strong> to save. 💾</p><p>Make sure the aud (audience) and iss (issuer) claims in the Asgardeo-issued JWT line up with what APIM expects after import.</p><h3>Step 5 — Create an Application + Generate Keys from the Resident Key Manager</h3><p>Now, in the <strong>Developer Portal</strong>:</p><ol><li>Log in: https://&lt;APIM_HOST&gt;:9443/devportal</li><li><strong>Applications</strong> → <strong>Add New Application</strong> → give it a name, e.g., TokenExchangeDemoApp</li><li>Open the app → <strong>Production Keys/ Sandbox Keys </strong>tab</li><li>Under <strong>Key Manager</strong>, select <strong>Resident Key Manager</strong></li><li>Under <strong>Grant Types</strong>, ensure these are checked:</li></ol><ul><li>✅ Token Exchange</li><li>✅ Refresh Token (optional, but handy)</li></ul><ol><li>Click <strong>Generate Keys</strong></li><li>You’ll now have an &lt;APIM_CONSUMER_KEY&gt; and &lt;APIM_CONSUMER_SECRET&gt;. <strong>Save these securely</strong>. We’ll use them as the <em>client credentials</em> in the token exchange call itself. 🔐</li><li>Go to <strong>APIs</strong> → find your published API → <strong>Subscribe</strong> → choose TokenExchangeDemoApp → <strong>Subscribe</strong>.</li></ol><p>This gives your application permission to invoke that API once it has a valid APIM access token.</p><h3>Step 6 — Generate access token and invoke api</h3><p>With everything configured, here’s the actual token exchange request:</p><pre>curl -k -X POST \<br>https://&lt;APIM_HOST&gt;:&lt;APIM_PORT&gt;/oauth2/token \<br>-H &#39;Content-Type: application/x-www-form-urlencoded&#39; \<br>-H &#39;Authorization: Basic &lt;Base64(APIM_CONSUMER_KEY:APIM_CONSUMER_SECRET)&gt;&#39; \<br>-d &#39;grant_type=urn:ietf:params:oauth:grant-type:token-exchange&#39; \<br>-d &#39;requested_token_type=urn:ietf:params:oauth:token-type:jwt&#39; \<br>-d &#39;subject_token=&lt;ASGARDEO_JWT_FROM_STEP_3&gt;&#39; \<br>-d &#39;subject_token_type=urn:ietf:params:oauth:token-type:jwt&#39;</pre><p>You can also use apim devportal to generate access token as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sQ3XPWlLfxTDuIwb8fae2A.png" /></figure><p>If everything’s wired up correctly, APIM responds with a <strong>new access token</strong> issued by the <strong>Resident Key Manager</strong>.</p><p>You can verify issue and other token details by decoding it using tool: <a href="https://wso2-cs.github.io/cs-tools/">https://wso2-cs.github.io/cs-tools/</a></p><pre>{<br>&quot;access_token&quot;: &quot;eyJhbGciOiJSUzI1NiIs…&lt;APIM_JWT&gt;&quot;,<br>&quot;refresh_token&quot; :&quot;0bb1385f-2……&quot;,<br>&quot;issued_token_type&quot;:&quot;urn:ietf:params:oauth:token-type:jwt&quot;,<br>&quot;scope&quot;: &quot;default&quot;,<br>&quot;token_type&quot;: &quot;Bearer&quot;,<br>&quot;expires_in&quot;: 3600<br>}</pre><p>💡You can also do this exchange visually from the Developer Portal: under the application’s <strong>Production Keys</strong> or <strong>Sandbox keys</strong> tab, there’s an option to paste an external IdP token and exchange it interactively. Great for demos!</p><h3>Step 7 — Call the Protected API 🎯</h3><pre>curl -k -X GET \<br>https://&lt;APIM_HOST&gt;:8243/&lt;api-context&gt;/&lt;version&gt;/&lt;resource&gt; \<br>-H &#39;Authorization: Bearer &lt;APIM_ACCESS_TOKEN_FROM_STEP_6&gt;&#39;</pre><p>If you see your API’s actual response - <strong>congratulations</strong>, you’ve just completed a full federated identity → API invocation journey! 🥳</p><h3>🧯 Common Troubleshooting</h3><p>🔴 <strong>“Unsupported grant type” error</strong> —</p><ol><li>Double-check [oauth.grant_type.token_exchange] is enabled and APIM has been restarted.</li><li>Check if particular grant type is anbaled for application from devportal</li></ol><p>🔴 <strong>Signature validation failure</strong> — Make sure the JWKS URL (or certificate) registered against the Asgardeo Key Manager is correct and reachable from the APIM server.</p><p>🔴 <strong>Issuer mismatch</strong> — The iss claim in the Asgardeo JWT must match the issuer registered for the Asgardeo Key Manager in APIM (format: https://api.asgardeo.io/t/&lt;org_name&gt;/oauth2/token).</p><p>🔴 <strong>Wrong Key Manager selected when generating keys</strong> — Remember: for the token-exchange <em>call itself</em>, your application’s consumer key/secret must come from the <strong>Resident Key Manager</strong>, not Asgardeo.</p><p>You can verify flow by enable debug logs for below components in case any error occurs:</p><ul><li>org.wso2.carbon.identity</li><li>org.apache.http.wire</li></ul><p>This pattern gives you the best of both worlds: centralized identity via Asgardeo, and full API lifecycle management via APIM — without forcing users to juggle multiple logins. 🙌</p><p><strong>📚 References:</strong></p><p><a href="https://wso2.com/asgardeo/docs/references/grant-types/#oauth2-grant-types">https://wso2.com/asgardeo/docs/references/grant-types/#oauth2-grant-types</a></p><p><a href="https://wso2.com/asgardeo/docs/references/tokens/">https://wso2.com/asgardeo/docs/references/tokens/</a></p><p><a href="https://apim.docs.wso2.com/en/4.5.0/administer/key-managers/overview/">https://apim.docs.wso2.com/en/4.5.0/administer/key-managers/overview/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a5e041b3990" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MTLS Certificate Expired? Automate API Identification & Renewal!]]></title>
            <link>https://medium.com/@kajal_24040/mtls-certificate-expired-automate-api-identification-renewal-32d1aeef712f?source=rss-f0feef935980------2</link>
            <guid isPermaLink="false">https://medium.com/p/32d1aeef712f</guid>
            <dc:creator><![CDATA[Kajal Katoke]]></dc:creator>
            <pubDate>Sun, 30 Mar 2025 18:31:46 GMT</pubDate>
            <atom:updated>2025-03-30T18:31:46.458Z</atom:updated>
            <content:encoded><![CDATA[<p>Managing certificate renewals for <strong>MTLS (Mutual TLS)</strong> in <strong>WSO2 API Manager</strong> (WSO2 APIM) can be a time-consuming and complex task. In this article, we’ll explore an efficient way to automate the identification of APIs using a particular certificate, making renewal much easier.</p><h3>Understanding MTLS in WSO2 APIM</h3><p>WSO2 APIM provides the option to secure APIs using MTLS, which enhances security by ensuring that both the client and server authenticate each other.</p><ul><li>In a one-way SSL authentication, only the client verifies the server’s identity.</li><li>In mutual SSL, both parties verify each other’s identity, ensuring a high-trust environment.</li><li>This eliminates the need for clients to send credentials such as usernames and passwords, as long as the server recognizes the client certificate.</li></ul><h3>The Challenge: Manual Certificate Renewal</h3><p>When securing APIs with MTLS, certificates are stored in the client-truststore-temp.jks file. Each certificate is assigned a unique alias when added via the WSO2 Publisher Portal UI.</p><p><strong>Problem Statement<br></strong>Imagine a system with 500+ APIs, where multiple APIs have 10+ certificates and some of which are shared . If that common certificate expires, the manual renewal process involves:<br>1. Identifying which APIs are using the expired certificate.<br>2. Manually updating the certificate for each API.</p><p>Since there’s no direct API to fetch this mapping, this process becomes tedious and inefficient.</p><p><strong>Solution: Automating Certificate Identification</strong></p><p>This blog provides a tool to automate the process of identifying APIs linked to a particular certificate using its Common Name (CN).</p><p><strong>How It Works</strong></p><ul><li>The tool scans your WSO2 APIM environment and fetches all APIs using the given certificate CN.</li><li>It returns a list of API IDs and Names associated with the certificate.</li></ul><p><strong>Steps to Use the Tool :<br></strong>1. Download and Configure</p><ul><li>Clone the repository: git clone <a href="https://github.com/kajal1410/WSO2-api-cert-checker.git">https://github.com/kajal1410/WSO2-api-cert-checker.git</a></li><li>Update the parameters in config.properties file</li></ul><pre>CN=localhost # Common Name of the certificate<br>TENANT_DOMAIN=carbon.super # Tenant domain to scan APIs from</pre><p>For different WSO2 APIM versions, update</p><pre>CLIENT_REGISTRATION_URL, json.payload, ACCESS_TOKEN_URL, PUBLISHER_REST_API_URL</pre><p>Here I have used APIM:4.2.0 publisher Rest APIs. If you are using a different version you need to update the below parameter according to publisher Rest AP definition.</p><p>2. Build and Run</p><ul><li>Build the project using Maven: mvn clean install</li><li>Run the tool: java -jar target/Certificate_Manager-0.0.1-SNAPSHOT.jar</li></ul><p>3. Sample Output</p><pre>API ID: 2965df32-e08c-4898-a4fe-3dad59444816 and Name: admin-PizzaShackAPI-1.0.0 has a certificate with CN=localhost<br>API ID: 5885fa59–8fe8–4dd0-ab75–3064ed7ec585 and Name: admin-Test1–1.0.0 has a certificate with CN=localhost</pre><p>Now, you have a complete list of APIs using a particular certificate!<br>By using this tool, you can eliminate the manual effort of searching for APIs linked to expired certificates. This improves efficiency and reduces the risk of missing certificate renewals.</p><p><strong>Next Steps: Automating Certificate Updates<br></strong>If you want to automate certificate updates, you can integrate an external certificate management tool like<a href="https://github.com/keyfactor"> Keyfactor</a>. Alternatively, you can extend the tool by implementing logic to call Update certificate rest API as per document[1]</p><p>🚀 <strong>Try it out and make certificate management easier in WSO2 APIM and keep your APIs happy!<br></strong>Hope this document will be helpful to reduce your effort of searching APIs for particular certificates 🙂<br><strong>Related documents:<br></strong>[1] <a href="https://github.com/kajal1410/WSO2-api-cert-checker.git">https://github.com/kajal1410/WSO2-api-cert-checker.git</a><br>[2] <a href="https://apim.docs.wso2.com/en/4.2.0/reference/product-apis/publisher-apis/publisher-v4/publisher-v4/#tag/Client-Certificates/operation/updateAPIClientCertificateByAlias">https://apim.docs.wso2.com/en/4.2.0/reference/product-apis/publisher-apis/publisher-v4/publisher-v4/#tag/Client-Certificates/operation/updateAPIClientCertificateByAlias</a><br>[3] <a href="https://apim.docs.wso2.com/en/4.2.0/reference/product-apis/publisher-apis/publisher-v4/publisher-v4/">https://apim.docs.wso2.com/en/4.2.0/reference/product-apis/publisher-apis/publisher-v4/publisher-v4/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32d1aeef712f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>