<?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 Mendisdumindu on Medium]]></title>
        <description><![CDATA[Stories by Mendisdumindu on Medium]]></description>
        <link>https://medium.com/@mendisdumindu21?source=rss-239de47cb557------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HLp1F4im7p9DvL9c</url>
            <title>Stories by Mendisdumindu on Medium</title>
            <link>https://medium.com/@mendisdumindu21?source=rss-239de47cb557------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:34:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mendisdumindu21/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[Tips for Setting Up Stripe Monetization in WSO2 API Manager 4.5.0]]></title>
            <link>https://medium.com/@mendisdumindu21/tips-for-setting-up-stripe-monetization-in-wso2-api-manager-4-5-0-bb3d7773eca3?source=rss-239de47cb557------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb3d7773eca3</guid>
            <dc:creator><![CDATA[Mendisdumindu]]></dc:creator>
            <pubDate>Mon, 24 Nov 2025 10:45:30 GMT</pubDate>
            <atom:updated>2025-11-24T10:52:41.768Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/839/1*DHJrPW4wJ0CwC0ox9VW2dQ.png" /></figure><p>While I was trying to integrate Stripe as a monetization provider in WSO2 API Manager 4.5.0, I ran into a few challenges even though I followed the official documentation and learned some useful tricks that can make the process faster, smoother, and less confusing.</p><p>In this post, I’ll share the small but valuable tips I discovered along the way, so you can avoid unnecessary troubleshooting and get your Stripe monetization configuration working with minimal friction.When you’re Setting up monetization for WSO2 APIM 4.5.0 .</p><p>For the reference, you can find the official guide here: <a href="https://apim.docs.wso2.com/en/latest/manage-apis/design/api-monetization/monetizing-an-api/">Monetize an API — WSO2 API Manager Documentation</a></p><ul><li>Make sure to <strong>set the time zone</strong> of Stripe to UTC before starting the process.</li></ul><pre>                   Settings → Business → Account Details.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ySbV5rcDqPWMvDpyZJ-Jw.png" /></figure><p>You will find the Option to set the Time zone by scrolling down.</p><ul><li>In the deployment.toml file of APIM 4.5.0, On-premises key of choreo is used twice. Make sure to use the same key for both configurations otherwise the setup won’t work properly.</li></ul><pre>[apim.monetization]<br>analytics_access_token = &lt;on-prem key from choreo&gt;<br><br>[apim.analytics]<br>auth_token = &lt;on-prem key from choreo&gt;</pre><ul><li>Make sure to Always use the production keys from choreo dev-portal application in the [apim.monetization] config.</li></ul><pre>[apim.monetization]<br>choreo_insight_app_consumer_key = &lt;production key of choreo Application&gt;<br>choreo_insight_app_consumer_secret = &lt;production secret of choreo Application&gt;</pre><ul><li>When adding the workflows make sure to edit the workflow-extensions.xml file using a proper text editor (Visual Studio Code,Notepad++ etc.)</li><li>Make sure to use WSO2 APIM stripe plugin version 1.5.x .</li><li>When You are creating the application in Choreo, Make sure to set the organization of choreo console to “ Choreo System ” otherwise You won’t be able to subscribe to the Insights API.</li></ul><p>These are the tips I’ve gathered so far, and I hope you find them helpful. If I discover more along the way, I’ll be sure to update this post with additional insights in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb3d7773eca3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Configuring Asgardeo as the IDP for SSO in WSO2 API Manager 4.2.0.]]></title>
            <link>https://medium.com/@mendisdumindu21/configuring-asgardeo-as-the-idp-for-sso-in-wso2-api-manager-4-2-0-5657ad52a664?source=rss-239de47cb557------2</link>
            <guid isPermaLink="false">https://medium.com/p/5657ad52a664</guid>
            <dc:creator><![CDATA[Mendisdumindu]]></dc:creator>
            <pubDate>Thu, 30 Oct 2025 05:31:44 GMT</pubDate>
            <atom:updated>2025-10-30T05:31:44.659Z</atom:updated>
            <content:encoded><![CDATA[<h3>🔐 Introduction</h3><p>In today’s API-driven world, seamless and secure user authentication is a must for any enterprise platform. <strong>Single Sign-On (SSO)</strong> plays a crucial role in enhancing user experience by allowing users to access multiple applications with a single set of credentials.</p><p>When it comes to implementing SSO in <strong>WSO2 API Manager</strong>, integrating with a trusted <strong>Identity Provider (IdP)</strong> like <strong>Asgardeo</strong> — WSO2’s cloud-native CIAM solution — offers both convenience and security.</p><p>In this article, we’ll go step-by-step through configuring <strong>Asgardeo as the Identity Provider (IdP)</strong> for enabling <strong>Single Sign-On (SSO)</strong> in <strong>WSO2 API Manager 4.2.0</strong>. By the end, you’ll have a fully functional setup where developers and administrators can log in to WSO2 portals using their Asgardeo credentials — streamlining access control and centralizing identity management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*eDivPvYpJXjIlYHJ96EGQg.png" /></figure><h4>🧭 High-Level Steps</h4><p>Here’s a quick overview of the steps we’ll be covering:</p><h4>Configure Asgardeo.</h4><ul><li>Create an Asgardeo Application.</li><li>Create Attributes.</li><li>Add the Attributes to the OpenID scope.</li><li>Create User/Users.</li></ul><h4>Configure APIM.</h4><ul><li>Create a New Identity Provider.</li><li>Configure Federated Authentication.</li><li>Configure Role Mapping.</li><li>Configure Claim Configurations.</li><li>Configure Roles in APIM.</li><li>Add the Scopes to the role.</li><li>Configure Service Providers.</li><li>Visit the devPortal and test user Login.</li></ul><h3>“ Configure Asgardeo</h3><h3>1. Create a new Standard Based Application.</h3><p>1.1. Visit the Asgardeo console <a href="https://console.asgardeo.io/">asgardeo.io</a>.</p><p>1.2. Login and Click on Applications from the left navigation bar and click on “ + New Application ”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wBHoJp2B2SpymK0zzQhXcA.png" /></figure><p>1.3. Click on “Standard-Based Application” in the next page and you will be redirected to the following page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nvnuuGhnHWnAL0kYAqyh_Q.png" /></figure><p>1.5. provide an Application name, example :- API_invokeApp, select OAuth2.0 OpenID Connect and click on Create button.</p><ul><li>You will be redirected to the Application Configuration page.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Msp69lROBvaLcuuFOrApZA.png" /></figure><p>1.6. Go to the protocol tab and Select ‘Code’ grant type. ‘Client Credential’ grant will be pre-selected, if not select it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n-qKOApIMxGWW942gZaR7A.png" /></figure><p>1.7. Then set “https://&lt;APIM-host&gt;:&lt;APIM-port&gt;/commonauth” as the Authorized redirect URL and press enter.</p><pre>https://&lt;APIM-host&gt;:&lt;APIM-port&gt;/commonauth</pre><p>Example : —</p><pre>https://dev.apim.com:9443/commonauth</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O3JvoqWFbbHdYGsDgh8SIg.png" /></figure><h3>2. Create Attributes</h3><p>2.1. In the left Navigation menu go to ‘User Attributes &amp; stores -&gt; attributes ‘</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gUsQxS56DDFDUROxT7O6yw.png" /></figure><p>2.2. Click on Attributes → + New Attribute</p><p>2.3. Create an attribute called ‘asgardeo_role’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*by_IXqfWQ2szAxb6VwQ0oQ.png" /></figure><p>2.4. Follow the same procedure and create another attribute called ‘asgardeo_user’.</p><p>2.5. Find the Asgardeo Role from the attribute list and scroll to the bottom section, you will find the ‘Attribute Configuration’ section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4I82h6X7ZGnL6XPnBesO7Q.png" /></figure><p>2.6. Mark the below rows and click on ‘Update’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VztAysb8eTtSj1D2SRujUQ.png" /></figure><p>2.7. Follow the same steps for asgardeo_user Attribute.</p><h3><em>3. Add the Attributes to the Open ID scope</em></h3><p>3.1. Go back to the attributes page from the left navigation menu.</p><p>3.2. Click on <strong>OpenID Connect</strong> from the Manage Attribute Mappings, There click on Scopes</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q2MT9XJZI6gXnbjiWOlkQA.png" /></figure><p>3.3. Click on ‘Open ID’ from the Scopes list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M1U0aDIULcR8YHND5Je_zg.png" /></figure><p>3.4. In the Next page click ‘+ New Attribute’ and add the ‘asgardeo_role’ and ‘asgardeo_user’ attributes to the scope and click save.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*keV2nElWUY6pxhQ57jy4tw.png" /></figure><h3>4. Add the attributes to Application users</h3><p>4.1. Click on applications item from the left navigation menu and select the API_InvokeApp.</p><p>4.2. Go to the User Attributes tab on the application configuration page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d72NgsVZ8f3h5O3aRsdamw.png" /></figure><p>4.3. Add the “asgardeo_user” and “asgardeo_role” attributes and make them mandatory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0I0ufmyd2vNA_F1DCw4fug.png" /></figure><p>4.4. Then add asgardeo_user as the subject attribute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oHCOJDfRqFwsAbqR3GYRuw.png" /></figure><p>4.5. Click on ‘Update button’ at the bottom of the page.</p><h3>5. Create a User/Users</h3><p>5.1. Go to user management from the left Navigation menu and click on ‘Users’ from the drop down.</p><p>5.2. Click on ‘+ Add User’ -&gt; Single User in the Users Page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*enABBh9LgBnMxKD-47UMzw.png" /></figure><p>5.3. Fill the form with user’s details and add ‘APIM’ as asgardeo_role. Add a unique name as the asgardeo_user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OIOPchq5ooNU29RQJj_MZA.png" /></figure><p>5.4. Click ‘Save &amp; Continue.</p><h3>“APIM setup</h3><h4>1. Create a New Identity Provider</h4><p>1.1. Click Add on the Identity Providers section from the left navigation menu.</p><p>1.2. Put ‘Asgardeo’ as identity provider name</p><p>1.3. As Identity provider JWKS endpoint</p><pre>            https://api.asgardeo.io/t/&lt;org_name&gt;/oauth2/jwks</pre><p>1.4. As Issure Name</p><pre>             https://api.asgardeo.io/t/&lt;org_name&gt;/oauth2/token</pre><p><strong>Note: make sure to replace the org name from the Asgardeo as the &lt;org_name&gt;.</strong></p><p>Example :-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDQyuinLlmAousdGQbUaTg.png" /></figure><h4>2. Configure Federated Authentication</h4><p>2.1. Go to the Federated Authenticators section from the bottom of the page and click OAuth2/OpenID Connect configurations.</p><p>2.2. Fill the details as below</p><pre>Enable OAuth2/OpenIDConnect : True<br>Default : True<br>Client Id : &lt;client_id&gt;<br>Client Secret : &lt;client_secret&gt;</pre><p><strong>Note : You can find the client ID and secret in protocol tab of the asgardeo Application.</strong></p><p><strong>Note: When filling the below URL’s make sure to replace &lt;org_name&gt; with the organization name from Asgardeo.</strong></p><p><strong><em>Authorization Endpoint URL</em></strong></p><pre>            https://api.asgardeo.io/t/&lt;org_name&gt;/oauth2/authorize</pre><p><strong><em>Token Endpoint URL</em></strong></p><pre>            https://api.asgardeo.io/t/&lt;org_name&gt;/oauth2/token</pre><p><strong><em>Callback Url</em></strong></p><pre>                https://&lt;APIM-host&gt;:&lt;APIM-port&gt;/commonauth</pre><p><strong><em>Userinfo Endpoint URL</em></strong></p><pre>            https://api.asgardeo.io/t/&lt;org_name&gt;/oauth2/userinfo</pre><p><strong><em>Logout Endpoint URL</em></strong></p><pre>               https://api.asgardeo.io/t/&lt;org_name&gt;/oidc/logout</pre><p>2.3. OpenID Connect User ID Location set to “User ID found in ‘sub’ attribute”</p><p>2.4. add the following parameter exactly in the Additional Query Parametes field</p><pre>                            scope=openid</pre><p>Example:-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3gE_4PvrvEZEbNOrHP4ZwA.png" /></figure><p>2.5. Enable JIT Provisioning and select Provision Silently</p><h4>3. Configure Role Mapping</h4><p>3.1. Click on the role mapping and click ‘+Add Role Mapping’</p><pre>             &#39;APIM&#39; as Identity provider role <br>             &#39;Internal/subscriber&#39; as the Local Role </pre><p>Example :-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DzBT0vEDcstbSyUjkhhWbw.png" /></figure><h4>4. Configure Claim Configurations</h4><p>4.1. Click on the Claim configurations and click on Basic Claim configuration drop Down ‘Define Custom Claim Dialect’</p><pre>          Identity provider claim URI -&gt; &#39;asgardeo_role&#39;<br>          Local Claim URI -&gt; &#39;http://wso2.org/claim/role&#39;<br>          Role Claim -&gt; &#39;asgardeo_role&#39;<br>          Role Claim URI -&gt; asgardeo_role</pre><p>4.2. Click on Register Button to save the Identity provider configuration.</p><p>Note : if you have already registered the Identity provider then click on the ‘update’ button.</p><h4>5. Configure Service Providers</h4><p>5.1. Visit the Carbon Portal again and login using admin credentials.</p><p>5.2. Click ‘List’ in the Service Providers section from the left Navigation menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uOjVqZEgs_j3hS9KQhL_Vg.png" /></figure><p>5.3. Click Edit on the ‘apim_devportal’ Service Provider.</p><p><strong>Note: for the apim_devportal provider to appear here, you must have been logged on to the dev portal of APIM at least once.</strong></p><p>5.4. Click on Local &amp; Outbound Authentication Configuration.</p><p>5.5. Select “Federated Authentication” as Authentication type and select “Asgardeo”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V-ErQGYQN4fG7MqaxHwUgQ.png" /></figure><p>5.6. Click on the Update button.</p><h4>6. Visit the devPortal and test user Login.</h4><p>💡 <strong>Summary:</strong><br> In this setup, we created two custom user attributes — asgardeo_role and asgardeo_user — within Asgardeo and added them to the application configured for SSO. When a user logs in through Asgardeo, these attributes are sent to WSO2 API Manager as part of the authentication token. In APIM, we mapped the asgardeo_role attribute to the local Internal/subscriber role, ensuring that authenticated users automatically gain access to the Developer Portal with the appropriate permissions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5657ad52a664" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>