<?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 Mahima Sanketh on Medium]]></title>
        <description><![CDATA[Stories by Mahima Sanketh on Medium]]></description>
        <link>https://medium.com/@mahimasanketh?source=rss-f8694579e10f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*42MklcbM4ph7LQ_piqr4lQ.png</url>
            <title>Stories by Mahima Sanketh on Medium</title>
            <link>https://medium.com/@mahimasanketh?source=rss-f8694579e10f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:35:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mahimasanketh/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[Fundamentals of Identity and Access Management]]></title>
            <link>https://medium.com/@mahimasanketh/fundamentals-of-identity-and-access-management-26591ca4d584?source=rss-f8694579e10f------2</link>
            <guid isPermaLink="false">https://medium.com/p/26591ca4d584</guid>
            <category><![CDATA[authorization]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[identity-management]]></category>
            <category><![CDATA[ami]]></category>
            <dc:creator><![CDATA[Mahima Sanketh]]></dc:creator>
            <pubDate>Fri, 21 Aug 2026 17:42:53 GMT</pubDate>
            <atom:updated>2026-08-21T17:42:53.517Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LQqT0nxesvp3a9igV2OLnQ.jpeg" /><figcaption>four pillars of IAM</figcaption></figure><p>When we talk about the fundamentals of IAM, it really comes down to three core pillars: who you are, whether you can prove it, and what you can do. Everything in IAM depends on these three.</p><p>Let me walk through each pillar one by one, with examples.</p><h3>Who you are (Identification)</h3><p>Identification is the claim of an identity (“I am doe@example.com”). At this stage it is just an assertion. Nothing is proven yet.</p><p>Think about onboarding at a new company. As part of the process, you get an email address created for you on the company domain, so that is identification for you. But it does not mean you can prove it yet. Just having the new company email is not enough.</p><h3>Can you prove it (Authentication)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EgQkDWqv6j-7giQmIOlH6g.jpeg" /><figcaption>major authentication factors</figcaption></figure><p>Authentication (AuthN) is proving that claim. This rests on factors: something you know (password, PIN), something you have (a device, a hardware token, a passkey), and something you are (biometrics). Multi-factor authentication combines two or more of these categories. A password plus an SMS code is two factors. Two passwords is still one factor.</p><p>Let me make it real. When you log in to your banking app, you probably enter a password or a PIN, right? That is something you know, and if you forget it, you lose access. Then you have the key to open your front door. That is something you have, a physical thing that belongs to you, and if you lose it you cannot get into your home either. Finally, you probably unlock your iPhone with your face. That is something you are. It is you. You do not need to memorize it or carry it around to get access, right?</p><p>Haha, and I did not forget you, my Android friend. You can unlock your Android with a fingerprint or even face unlock, while the iPhone does not do fingerprint, LOL 😁, just FYI.</p><h3>What you can do (Authorization)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ovRvZps0bNA10xXQ0-7QvQ.jpeg" /><figcaption>people connected by lines to different locked doors and cloud servers</figcaption></figure><p>Authorization (AuthZ) is deciding what an authenticated identity may do. This is where access-control models live:</p><ul><li><strong>RBAC (role-based):</strong> permissions attach to roles, and users get roles. Simple, and dominant in practice.</li><li><strong>ABAC (attribute-based):</strong> decisions are computed from attributes (user department, resource sensitivity, time of day). More flexible, more complex.</li><li><strong>ReBAC (relationship-based):</strong> access is derived from relationships between entities (the Google Zanzibar model, “user X is an editor of document Y”). Increasingly relevant for fine-grained, collaborative apps.</li><li><strong>PBAC / policy engines (OPA, Cedar):</strong> generalize all of these into externalized policy.</li></ul><p>Here is an example. Say you are an engineer at XYZ LLC. The company gives you a cloud console so you can deploy servers. The HR admin probably does not need that access, right? Haha, and if HR does need it, drop a comment with a valid reason. The other way around, the HR admin needs the ability to transfer payments to employees, but engineers usually do not, unless you happen to be the tech founder or the CEO wearing every hat.</p><h3>The pillar people forget: Accountability / auditing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xs02Exf_bNiLVHVUlgyk0g.jpeg" /><figcaption>auditing rows of entries</figcaption></figure><p>Accountability, or auditing, is the fourth pillar most people forget: logging who did what, and when. This is what makes the first three trustworthy, and it is non-negotiable for any enterprise.</p><h3>Wrapping up</h3><p>So that is IAM in a nutshell. Identification is your claim, authentication is you proving it, authorization is what you are actually allowed to touch, and auditing keeps a record so no one can hide. Everything else you will read about IAM, all the fancy protocols and enterprise tooling, sits right on top of these four. Nail the fundamentals first, right? The rest gets a whole lot easier once these click.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26591ca4d584" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Boring Little Code That Tells You a Company Is Real]]></title>
            <link>https://medium.com/@mahimasanketh/the-boring-little-code-that-tells-you-a-company-is-real-e9dfd25da54b?source=rss-f8694579e10f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9dfd25da54b</guid>
            <category><![CDATA[kyb]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[kyc]]></category>
            <category><![CDATA[identity-verification]]></category>
            <dc:creator><![CDATA[Mahima Sanketh]]></dc:creator>
            <pubDate>Tue, 28 Jul 2026 14:03:08 GMT</pubDate>
            <atom:updated>2026-07-28T14:12:48.834Z</atom:updated>
            <content:encoded><![CDATA[<p><em>What an LEI actually is, and why it quietly matters for verifying businesses online</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*XCW0KJGGA1soEu9UvsjfPw.jpeg" /><figcaption>Every one of these needs a unique label. Companies have the same problem and the LEI is one answer.</figcaption></figure><p>Here is a problem that sounds trivial until you try to solve it: how do you know a company is who it says it is?</p><p>A person is comparatively easy. There’s a passport, a face, a fingerprint, a government that will vouch for them. A company is slipperier. It’s a legal fiction, a thing that exists on paper. Two businesses can share a name. One business can operate under five. Companies get bought, renamed, dissolved, and re-registered in a different country by lunchtime. “Acme Ltd” in London is not “Acme LLC” in Delaware, except sometimes it secretly is.</p><p>If you’re building anything where businesses sign up as businesses (a payments platform, a B2B SaaS, a marketplace, a bank), this stops being a philosophical question and becomes your Tuesday. You need a reliable way to point at an organisation and say: that one, specifically, and here’s proof it exists.</p><p>That’s the gap the LEI was invented to fill.</p><h3>So what is an LEI?</h3><p>LEI stands for Legal Entity Identifier. It’s a 20-character code, letters and numbers, that points to exactly one legal entity anywhere in the world. Think of it as a company&#39;s passport number, not a person&#39;s.</p><p>The format is deliberately dull:</p><ul><li><strong>Characters 1 to 4:</strong> the organisation that issued the code</li><li><strong>Characters 5 to 6:</strong> reserved, always zeros</li><li><strong>Characters 7 to 18:</strong> the part unique to the entity</li><li><strong>Characters 19 to 20:</strong> a check digit, so a typo doesn’t silently point you at the wrong company</li></ul><p>Attached to that code is a public record: the entity’s legal name, its registered address, where it’s incorporated, its registration status, and, importantly, who its parent company is. That last part matters more than it sounds, which we’ll get to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BP3ihVgL_IlSitK2UaV_wA.png" /><figcaption>The anatomy of an LEI. Deliberately dull, deliberately unique.</figcaption></figure><h3>Where it came from (the short version)</h3><p>The LEI isn’t a startup’s clever idea. It emerged from the 2008 financial crisis.</p><p>When Lehman Brothers collapsed, regulators trying to untangle who was exposed to whom hit a wall: there was no consistent way to identify the counterparties. The same institution appeared under a dozen different names and codes across different systems. Nobody could see the full picture of the risk because nobody could reliably match “this entity here” to “that entity there.”</p><p>So the G20 and the Financial Stability Board backed a fix: one global identifier, one open system. That system is run by GLEIF, the Global Legal Entity Identifier Foundation, a non-profit set up to keep the whole thing neutral and public. The actual codes are handed out by accredited issuers around the world, but they all feed into one global index that anyone can search, for free.</p><p>That “for free and public” part is the quietly radical bit. There’s a REST API at api.gleif.org that requires no key, no contract, and no sales call. You can look up any of the roughly three million active LEIs right now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q5xTleHyf9olrQl9qyGvoQ.png" /><figcaption>From crisis to standard: how the LEI came to exist.</figcaption></figure><h3>Now, KYB, and where the LEI fits</h3><p>KYB is Know Your Business. It’s the sibling of KYC (Know Your Customer). KYC is about verifying a person; KYB is about verifying an organisation before you let it into your system, take its money, or move money on its behalf.</p><p>A proper KYB check is trying to answer a few separate questions:</p><ol><li><strong>Does this business actually exist?</strong> Is it a real, registered legal entity?</li><li><strong>Is it in good standing?</strong> Active, or dissolved and squatting on a name?</li><li><strong>Who really owns it?</strong> The beneficial owners, the humans at the top, not just the shell in front.</li><li><strong>Is it on any list it shouldn’t be on?</strong> Sanctions, watchlists, and so on.</li><li><strong>Is the person signing up actually allowed to act for it?</strong></li></ol><p>Here’s the honest bit that most vendor blog posts won’t tell you: <strong>the LEI only cleanly answers the first two.</strong></p><p>An LEI is excellent proof that an entity exists, is registered, and is who it claims to be, and because of the parent-company data, it can show you the corporate structure sitting above it. That structure piece is genuinely valuable for untangling “who owns whom,” which is often the hardest part of business verification.</p><p>But an LEI won’t tell you whether the person filling in your signup form is authorised to represent the company. It won’t screen for sanctions. And, crucially, most small businesses don’t have one at all, because LEIs took hold mainly in the financial sector and in regulated transactions. If your customers are corner shops and two-person consultancies, LEI coverage falls off a cliff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*InARmanu64EIq-o5VoZG8w.png" /><figcaption>What an LEI actually covers. Necessary, but not the whole picture.</figcaption></figure><h3>So why bother with it at all?</h3><p>Because when an LEI <em>is</em> present, it’s one of the strongest single signals you can get, and it’s free.</p><p>It’s a globally unique key. That alone solves the matching nightmare that started this whole story. If two of your systems, or you and a partner bank, both hold an entity’s LEI, you’re provably talking about the same company. No fuzzy name-matching, no guessing whether “Ltd” and “Limited” are the same company.</p><p>It’s authoritative and maintained. The data behind an LEI is validated against official business registries and is supposed to be renewed annually. (In practice, renewal is patchy historically; around 40% of LEIs lapse, so always check the status field rather than assuming a code means “current.”)</p><p>And it’s the natural anchor for everything else. A good KYB flow doesn’t pick one tool; it layers them. The LEI is the perfect first step: cheap, instant, and definitive on existence. You start there, and then reach for the paid, heavier tools (registry aggregators, sanctions screening, beneficial-ownership providers) only for the parts the LEI can’t cover. Using an expensive per-check verification service for something the free GLEIF API already answered is just burning money.</p><h3>Where this is heading</h3><p>The interesting frontier is the verifiable LEI, or vLEI. Instead of you looking up a code in a database, the company carries a cryptographically signed credential that proves both the entity’s identity <em>and</em> that a specific person holds a specific role in it. That closes the “is this person authorised” gap that plain LEIs leave open, which is exactly the missing piece in the KYB list above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AwsU7kLV_Kbl_UykTZWI-w.png" /><figcaption>Where this is heading: organisations that carry their own verifiable proof.</figcaption></figure><p>It’s early, and the underlying tech is its own rabbit hole, but the direction is clear: organisational identity is moving from “look it up in a registry” toward “the company presents proof it holds itself.” If you’re designing verification systems now, it’s worth knowing that’s coming.</p><h3>The one-paragraph version</h3><p>An LEI is a free, globally unique passport number for a company. In KYB, it’s the best possible first step: it proves, instantly and authoritatively, that a business exists and is registered, and it reveals who owns it. It won’t screen sanctions, confirm the signup person’s authority, or cover most small businesses, so it’s a foundation, not the whole building. But it’s a foundation that costs nothing and settles the single hardest question in business verification: <em>is this real?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9dfd25da54b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From GitHub to a Live API in Under 15 Minutes: Deploying an Open-Source Repo on WSO2 Choreo]]></title>
            <link>https://medium.com/@mahimasanketh/from-github-to-a-live-api-in-under-15-minutes-deploying-an-open-source-repo-on-wso2-choreo-0a2b1bcc1b70?source=rss-f8694579e10f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a2b1bcc1b70</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Mahima Sanketh]]></dc:creator>
            <pubDate>Mon, 27 Jul 2026 08:00:07 GMT</pubDate>
            <atom:updated>2026-07-27T08:17:01.155Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fB18_p2_6avSbkOG28iKdQ.png" /><figcaption>Connect Source code → containerized build → live, managed API endpoint. The three stages Choreo automates.servers to choreo</figcaption></figure><p>I’m an engineering intern on the IAM team at WSO2, and last week I needed a quick way to test a custom <strong>Action / Extension</strong> flow in WSO2 Identity Server specifically, a step that verifies an organization’s <strong>LEI (Legal Entity Identifier)</strong> against the public GLEIF registry before letting the org finish onboarding.</p><p>To test that flow, WSO2 Identity Server needed to call <em>something </em>a real, public HTTPS endpoint. I didn’t want to spin up a server, manage a domain, or fight with TLS certs just for a test extension. So I wrote a small mock service, pushed it to GitHub, and used <strong>Choreo</strong> to turn it into a live endpoint. Repo-to-running-API took less than 15 minutes, no infra work was involved.</p><p>Here’s the exact walkthrough, in case you want to do the same with your own repo.</p><h3>What I was deploying</h3><p>The repo is a small <a href="https://fastify.dev/">Fastify</a> service with one job: receive a claim from WSO2 IS, look up the LEI against the GLEIF API, and return SUCCESS or FAILED so IS knows whether to allow the account to be created.</p><ul><li>Repo: <a href="https://github.com/Mahima-Sanketh-Git/wso2-is-test-gleif-extension">wso2-is-test-gleif-extension</a></li><li>Endpoint: POST /api/v1/lei-verification</li><li>Runs on port 3000</li><li>No auth, no database just enough to prove the extension flow works end to end</li></ul><p>You don’t need this exact use case to follow along any Node/Go/Python/Docker service with an HTTP endpoint works the same way.</p><h3>Step 1: Start from your Choreo project home</h3><p>Every Choreo project has a <strong>Component Listing</strong> this is where all your services, web apps, and scheduled tasks live. Mine already had a couple of older components, but the important part is the <strong>+ Create</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BAT_0V1Ven0RT4Yt_ViJ9Q.png" /><figcaption><em>The Component Listing: every service, web app, and scheduled task in the project, in one place.</em></figcaption></figure><h3>Step 2: Pick a component type</h3><p>Click <strong>Create</strong>, and Choreo asks what kind of component you’re building: <strong>Service</strong>, <strong>Web Application</strong>, <strong>Scheduled Task</strong>, or <strong>Database</strong>. Since I was exposing a REST endpoint, I chose <strong>Service</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hfosKzoE6jQJ01QU3TISwQ.png" /><figcaption><em>Choosing a component type: Service, Web Application, Scheduled Task, or Database.</em></figcaption></figure><h3>Step 3: Connect your repo</h3><p>This is the step that saves you the most time. Choreo gives you two ways to bring in source code:</p><ul><li><strong>Authorize with GitHub: </strong>installs the Choreo GitHub App on your account, which also unlocks <em>auto-build on push</em>.</li><li><strong>Use Public GitHub Repository: </strong>just paste the URL, no authorization needed. Faster if your repo is already public, but builds have to be triggered manually (there’s no webhook without the GitHub App installed).</li></ul><p>Since my repo was already public, I went with the second option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bT9lIQeDMfPscdMBb6j-2w.png" /><figcaption>Two ways in: authorize with GitHub for auto-builds, or just paste a public repo URL.</figcaption></figure><h3>Step 4: Point it at your repo and name it</h3><p>Paste the repository URL, give the component a display name, and let Choreo auto-generate a unique internal name. Description is optional — I skipped it for a quick test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OCfDTRpKHTtpO8FOgaJXOQ.png" /><figcaption>Pointing Choreo at the repo and naming the component before hitting Create and Deploy.</figcaption></figure><p>Click <strong>Create and Deploy</strong>. Choreo detects the language/build preset from your repo (NodeJS, in my case) and gets the component ready.</p><h3>Step 5: Build</h3><p>Once the component’s created, head into <strong>Build</strong>. This page shows exactly what Choreo picked up from the repo the source URL, the main branch, the build path, and the language version it auto-detected (Node 24.x for me). I left <strong>Unit Test</strong> off since this is just a mock, but kept the <strong>Container (Trivy) vulnerability scan</strong> on a free security check on every build.</p><p>From here, it’s just <strong>Build Latest</strong>. Every run shows up below with its commit hash, status, and timestamp mine went green (<strong>Success</strong>) in a couple of minutes without me writing a single line of CI config. Since I’d connected the repo via the public-URL option, every build here is tagged <strong>Manual</strong> I had to come back and click it again after each push. If you’d rather that happened on its own, there’s a <strong>Configure Auto Build</strong> button sitting right next to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V-XX1SSrcUvHbGoQqmXEJA.png" /><figcaption>The Build page: source, build config, and every run with its status and commit.</figcaption></figure><h3>Step 6: Deploy and promote it across environments</h3><p><strong>Deploy</strong> is where a successful build turns into an actual running service, laid out as three columns:</p><ul><li><strong>Set up: </strong>your latest build, sitting ready. Flip <strong>Auto Deploy on Build</strong> if you want new builds to roll out on their own, or just hit <strong>Deploy</strong>.</li><li><strong>Development: </strong>whatever build is currently running in Dev, with its own commit details and endpoint.</li><li><strong>Production: </strong>the environment that’s actually serving traffic.</li></ul><p>I deployed my latest build to Development first, confirmed it worked, then promoted that exact same build straight to Production no rebuild needed. A few seconds after clicking deploy, Production flips from <em>In-progress</em> to live, endpoint and all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p1Qbx-VsGgJ4NgR65pvTpw.png" /><figcaption>Deploy page: promoting a build from Set up, to Development, to Production.</figcaption></figure><h3>Step 7: Test it</h3><p>Under <strong>Test → Console</strong>, Choreo shows the endpoint it just deployed mine came back as a public HTTPS URL, ready to hit. Click <strong>Get Test Key</strong> to generate a short-lived token, then expand the endpoint and fire a request straight from the browser no Postman or curl needed for a quick sanity check.</p><p>I sent the same claims payload WSO2 IS would send, and got back actionStatus: SUCCESS for a valid LEI and FAILED for an invalid one — confirming the full chain, IS → Choreo → GLEIF API → back to IS, actually worked before wiring anything into IS for real.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SSQZtl5dgDfbtUNsB57jPw.png" /><figcaption>Test Console: grab a test key, hit the live endpoint, see the response.</figcaption></figure><h3>Step 8: Plug it back into whatever called it</h3><p>For me, that meant dropping the Choreo endpoint URL into a WSO2 IS Action/Extension config. From there, every request routed straight to the live endpoint no server of my own to manage.</p><h3>Try it yourself</h3><p>The repo is public fork it, connect it the same way, and you’ll have your own working GLEIF-verification endpoint in about the same time it took me:</p><p>👉 <a href="https://github.com/Mahima-Sanketh-Git/wso2-is-test-gleif-extension">github.com/Mahima-Sanketh-Git/wso2-is-test-gleif-extension</a></p><p>And if you want the full reference for every component type and configuration option Choreo supports, the official docs are the best place to go from here:</p><p>👉 <a href="https://wso2.com/choreo/docs/develop-components/develop-services/develop-a-service/">Choreo Docs — Develop a Service</a></p><p>That’s it from a repo on GitHub to a live, testable API endpoint, in less time than it takes to get a coffee.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a2b1bcc1b70" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Connected a Production Backend to WSO2 Choreo: A Real Developer Journey]]></title>
            <link>https://medium.com/@mahimasanketh/how-i-connected-a-production-backend-to-wso2-choreo-a-real-developer-journey-3e068cba6a24?source=rss-f8694579e10f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e068cba6a24</guid>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[choreo]]></category>
            <category><![CDATA[wso2-api-manager]]></category>
            <category><![CDATA[tripceylon]]></category>
            <dc:creator><![CDATA[Mahima Sanketh]]></dc:creator>
            <pubDate>Thu, 19 Mar 2026 19:48:03 GMT</pubDate>
            <atom:updated>2026-03-19T19:49:53.545Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DQRpUzCP5QcaZKlTT5V1iA.png" /><figcaption>Tripceylon X WSO2 Choreo</figcaption></figure><p><em>From 403 errors at 12am to a fully authenticated production API — here’s everything that actually happened.</em></p><h3>Introduction</h3><p>Building a travel tech platform comes with its own set of challenges. Infrastructure inconsistencies, authentication complexity, and the question of how to securely expose backend APIs without rebuilding everything from scratch.</p><p>This is the real story of integrating a production backend with an API gateway platform, setting up OAuth2 authentication, debugging repeated 403 errors, and connecting everything to a Next.js frontend using Axios.</p><p>No polished tutorial. Just the real journey — including every mistake.</p><p>🌴 <strong>What is this platform?</strong><br> A travel solution designed to help users discover authentic local experiences, accommodations, and itineraries.</p><h3>What We Had to Start With</h3><p>Our backend was already live — a production REST API hosted on a cloud server, sitting behind an API gateway.</p><p>The OpenAPI specification looked clean:</p><ul><li>Base URL defined via the gateway</li><li>Backend service hosted separately</li><li>Authentication using OAuth2</li><li>Gateway handled routing and security</li></ul><p>What we didn’t realize initially was that the gateway abstracts a lot of complexity. Without understanding how its portal, subscriptions, and authentication model work, debugging becomes confusing quickly.</p><h3>Step 1 — Understanding the Real Gateway URL</h3><p>The first surprise was that the API endpoint defined in the specification was not the exact one used in production.</p><p>Instead, the real endpoint included:</p><ul><li>An organization-specific identifier</li><li>Environment-specific routing</li><li>A region-specific domain</li></ul><p>This structure maps internally to the gateway’s configuration and base path.</p><p>Once identified, this becomes the actual public entry point for all API requests.</p><h3>Step 2 — The First Error: Invalid Credentials</h3><p>Our first API call returned:</p><pre>{<br>  &quot;error_message&quot;: &quot;Invalid Credentials&quot;,<br>  &quot;code&quot;: &quot;900901&quot;,<br>  &quot;error_description&quot;: &quot;Invalid Credentials. Make sure you have provided the correct security credentials&quot;<br>}</pre><p><strong>What this means:</strong></p><ul><li>The request successfully reached the gateway</li><li>But no valid access token was provided</li></ul><p>💡 <strong>Key insight:</strong></p><ul><li>900901 → Missing or invalid token</li><li>403 → Valid token but no subscription</li><li>404 → Incorrect endpoint</li></ul><p>Understanding these early prevents hours of unnecessary debugging.</p><h3>Step 3 — Obtaining OAuth2 Credentials</h3><p>The gateway uses an application-based OAuth2 model.</p><p>The process:</p><ol><li>Log into the developer portal</li><li>Create an application</li><li>Generate production keys</li><li>Retrieve:</li></ol><ul><li>Client ID</li><li>Client Secret</li></ul><p>5. Use the token endpoint provided by the platform</p><p>These credentials are used to request access tokens via the OAuth2 Client Credentials flow.</p><h3>Step 4 — The 403 Forbidden Issue</h3><p>After successfully obtaining a token, the next error appeared:</p><pre>403 Forbidden</pre><p>This indicated:</p><p>👉 The token was valid<br> 👉 But the application was not subscribed to the API</p><h3>Fix:</h3><ol><li>Navigate to the API catalog in the developer portal</li><li>Locate the API</li><li>Subscribe the application to the API</li><li>Choose an appropriate subscription tier</li><li>Confirm the subscription status is active</li><li>Regenerate the token</li></ol><p>⚠️ Important:</p><ul><li>Tokens do not automatically update subscription permissions</li><li>A new token must be generated after subscribing</li></ul><h3>Step 5 — Understanding Test Tokens vs Production Tokens</h3><p>The developer portal often provides a “generate token” option for quick testing.</p><p>Test TokenOAuth2 TokenSourcePortal UIOAuth flowExpiryShort-livedConfigurableUse caseTestingProductionRefreshManualAutomated</p><p>👉 Test tokens are useful for validation<br> 👉 OAuth tokens should be used in real applications</p><h3>Step 6 — Setting Up API Testing in Postman</h3><p>To standardize testing across the team:</p><ul><li>Use a collection-level configuration</li></ul><p>Store:</p><p>Base URL , Client ID, Client Secret</p><p>Configure OAuth2 with:</p><ul><li>Client Credentials grant type</li><li>Token endpoint provided by the platform</li><li>Credentials passed in the request body</li></ul><p>Test a simple health or status endpoint first.</p><p>A successful 200 OK confirms:</p><ul><li>Authentication works</li><li>Subscription is active</li><li>Gateway routing is correct</li></ul><h3>Step 7 — Integrating with Next.js Using Axios</h3><p>After validating everything in Postman, integration moves to the frontend.</p><h3>Architecture Overview</h3><ul><li>Frontend: Next.js</li><li>HTTP client: Axios</li><li>Authentication: OAuth2 token retrieval</li><li>Token handling: Cached and auto-refreshed</li></ul><h3>Axios Setup with Token Caching</h3><pre>import axios from &quot;axios&quot;;</pre><pre>let cachedToken = null;<br>let tokenExpiry = null;</pre><pre>const getToken = async () =&gt; {<br>  if (cachedToken &amp;&amp; tokenExpiry &amp;&amp; Date.now() &lt; tokenExpiry) {<br>    return cachedToken;<br>  }</pre><pre>  const credentials = btoa(<br>    `${process.env.CLIENT_ID}:${process.env.CLIENT_SECRET}`<br>  );</pre><pre>  const response = await axios.post(<br>    process.env.TOKEN_URL,<br>    &quot;grant_type=client_credentials&quot;,<br>    {<br>      headers: {<br>        Authorization: `Basic ${credentials}`,<br>        &quot;Content-Type&quot;: &quot;application/x-www-form-urlencoded&quot;,<br>      },<br>    }<br>  );</pre><pre>  cachedToken = response.data.access_token;<br>  tokenExpiry = Date.now() + (response.data.expires_in - 60) * 1000;</pre><pre>  return cachedToken;<br>};</pre><pre>const api = axios.create({<br>  baseURL: process.env.BASE_URL,<br>  headers: { &quot;Content-Type&quot;: &quot;application/json&quot; },<br>});</pre><pre>api.interceptors.request.use(async (config) =&gt; {<br>  const token = await getToken();<br>  config.headers.Authorization = `Bearer ${token}`;<br>  return config;<br>});</pre><pre>export default api;</pre><h3>Using the API in a Component</h3><pre>&quot;use client&quot;;</pre><pre>import { useEffect, useState } from &quot;react&quot;;<br>import api from &quot;@/lib/api&quot;;</pre><pre>export default function Page() {<br>  const [data, setData] = useState([]);</pre><pre>  useEffect(() =&gt; {<br>    const fetchData = async () =&gt; {<br>      const response = await api.get(&quot;/your-endpoint&quot;);<br>      setData(response.data);<br>    };</pre><pre>    fetchData();<br>  }, []);</pre><pre>  return (<br>    &lt;div&gt;<br>      {data.map((item) =&gt; (<br>        &lt;div key={item.id}&gt;{item.name}&lt;/div&gt;<br>      ))}<br>    &lt;/div&gt;<br>  );<br>}</pre><h3>Key Lessons From This Journey</h3><p><strong>1. Understand error codes early</strong></p><ul><li>Token issues and subscription issues are different problems with different fixes.</li></ul><p><strong>2. Gateway URL ≠ backend URL</strong></p><ul><li>The gateway abstracts routing and may use environment-specific endpoints.</li></ul><p><strong>3. Authentication is only part of the equation</strong></p><ul><li>Subscription is a separate required step.</li></ul><p><strong>4. Token caching is essential</strong></p><ul><li>Avoid requesting a token for every API call.</li></ul><p><strong>5. Environment variables must be protected</strong></p><ul><li>Never commit secrets to version control.</li></ul><p><strong>6. Centralized API configuration simplifies development</strong></p><ul><li>Collection-level auth in Postman mirrors real-world architecture.</li></ul><p><strong>7. Always test a basic endpoint first</strong></p><ul><li>A health check confirms the full pipeline before integrating real features.</li></ul><h3>Final Architecture</h3><pre>Frontend (Next.js)<br>        ↓<br>Axios Client (Token Caching + Interceptors)<br>        ↓<br>API Gateway (OAuth2 + Subscription Enforcement)<br>        ↓<br>Backend Service (Hosted on cloud infrastructure)</pre><h3>Conclusion</h3><p>API gateway platforms like WSO2 Choreo provide powerful abstractions for managing APIs, but they introduce additional layers that must be properly understood.</p><p>Most issues encountered are not coding problems, but configuration-related:</p><ul><li>Missing subscriptions</li><li>Incorrect endpoints</li><li>Expired or missing tokens</li><li>Misconfigured OAuth flows</li></ul><p>Once the architecture is understood, the system becomes predictable and scalable.</p><h3>Written by</h3><p>Mahima Sanketh<br>@Tripceylon</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e068cba6a24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Create Notifications in Flutter for Android and iOS]]></title>
            <link>https://medium.com/@mahimasanketh/how-to-create-notifications-in-flutter-for-android-and-ios-35ddc08d0f0d?source=rss-f8694579e10f------2</link>
            <guid isPermaLink="false">https://medium.com/p/35ddc08d0f0d</guid>
            <category><![CDATA[flutter-notification]]></category>
            <category><![CDATA[notifications]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Mahima Sanketh]]></dc:creator>
            <pubDate>Tue, 22 Apr 2025 15:44:57 GMT</pubDate>
            <atom:updated>2025-04-22T15:44:57.266Z</atom:updated>
            <content:encoded><![CDATA[<p>Flutter is an excellent framework for building cross-platform mobile applications. However, when it comes to handling platform-specific features like notifications, things can get a bit tricky. This guide will walk you through the process of setting up and displaying notifications in your Flutter app for both Android and iOS using the flutter_local_notifications package.</p><h3>Step 1: Add Dependencies</h3><p>First, you need to add the flutter_local_notifications package to your pubspec.yaml file:</p><pre>yaml</pre><pre>Copy code</pre><pre>dependencies:<br>  flutter:<br>    sdk: flutter<br>  flutter_local_notifications: ^12.0.3 # Use the latest version</pre><p>Run flutter pub get to install the new dependency.</p><h3>Step 2: Configure Android and iOS</h3><h3>Android Configuration</h3><p>In your Android project’s AndroidManifest.xml file, add the necessary permissions and configure the notification settings:</p><pre>xml</pre><pre>Copy code</pre><pre>&lt;uses-permission android:name=&quot;android.permission.RECEIVE_BOOT_COMPLETED&quot;/&gt;<br>&lt;uses-permission android:name=&quot;android.permission.VIBRATE&quot;/&gt;<br>&lt;application&gt;<br>    &lt;!-- Add this inside the &lt;application&gt; tag --&gt;<br>    &lt;receiver android:name=&quot;com.dexterous.flutterlocalnotifications.receivers.ActionBroadcastReceiver&quot; android:exported=&quot;true&quot;/&gt;<br>    &lt;receiver android:name=&quot;com.dexterous.flutterlocalnotifications.receivers.DismissedReceiver&quot; android:exported=&quot;true&quot;/&gt;<br>    &lt;receiver android:name=&quot;com.dexterous.flutterlocalnotifications.receivers.NotificationReceiver&quot; android:exported=&quot;true&quot;/&gt;<br>    &lt;receiver android:name=&quot;com.dexterous.flutterlocalnotifications.receivers.ReplyReceiver&quot; android:exported=&quot;true&quot;/&gt;<br>&lt;/application&gt;</pre><h3>iOS Configuration</h3><p>For iOS, you need to configure the notification settings in your Info.plist file:</p><pre>xml</pre><pre>Copy code</pre><pre>&lt;key&gt;UIBackgroundModes&lt;/key&gt;<br>&lt;array&gt;<br>    &lt;string&gt;fetch&lt;/string&gt;<br>    &lt;string&gt;remote-notification&lt;/string&gt;<br>&lt;/array&gt;<br>&lt;key&gt;NSUserNotificationAlertStyle&lt;/key&gt;<br>&lt;string&gt;alert&lt;/string&gt;</pre><h3>Step 3: Initialize flutter_local_notifications</h3><p>In your Dart code, import the package and initialize it:</p><pre>dart</pre><pre>Copy code</pre><pre>import &#39;package:flutter_local_notifications/flutter_local_notifications.dart&#39;;</pre><pre>final FlutterLocalNotificationsPlugin flutterLocalNotificationsPlugin = FlutterLocalNotificationsPlugin();</pre><pre>void main() {<br>  runApp(MyApp());<br>  initializeNotifications();<br>}</pre><pre>void initializeNotifications() async {<br>  const AndroidInitializationSettings initializationSettingsAndroid = AndroidInitializationSettings(&#39;@mipmap/ic_launcher&#39;);</pre><pre>  final IOSInitializationSettings initializationSettingsIOS = IOSInitializationSettings(<br>      onDidReceiveLocalNotification: onDidReceiveLocalNotification);</pre><pre>  final InitializationSettings initializationSettings = InitializationSettings(<br>      android: initializationSettingsAndroid,<br>      iOS: initializationSettingsIOS);</pre><pre>  await flutterLocalNotificationsPlugin.initialize(initializationSettings,<br>      onSelectNotification: selectNotification);<br>}</pre><pre>Future onDidReceiveLocalNotification(int id, String title, String body, String payload) async {<br>  // handle the notification tapped logic here<br>}</pre><pre>Future selectNotification(String payload) async {<br>  // handle the notification tapped logic here<br>}</pre><h3>Step 4: Show a Notification</h3><p>You can now show a notification using the show method. Create a function to handle showing the notification:</p><pre>dart</pre><pre>Copy code</pre><pre>Future&lt;void&gt; showNotification() async {<br>  const AndroidNotificationDetails androidPlatformChannelSpecifics = AndroidNotificationDetails(<br>      &#39;your channel id&#39;, &#39;your channel name&#39;, &#39;your channel description&#39;,<br>      importance: Importance.max,<br>      priority: Priority.high,<br>      ticker: &#39;ticker&#39;);</pre><pre>  const IOSNotificationDetails iOSPlatformChannelSpecifics = IOSNotificationDetails();</pre><pre>  const NotificationDetails platformChannelSpecifics = NotificationDetails(<br>      android: androidPlatformChannelSpecifics, iOS: iOSPlatformChannelSpecifics);</pre><pre>  await flutterLocalNotificationsPlugin.show(<br>      0, &#39;New Notification&#39;, &#39;This is the notification content&#39;, platformChannelSpecifics,<br>      payload: &#39;item id 2&#39;);<br>}</pre><p>You can call this function, for example, from a button press:</p><pre>dart</pre><pre>Copy code</pre><pre>ElevatedButton(<br>  onPressed: () {<br>    showNotification();<br>  },<br>  child: Text(&#39;Show Notification&#39;),<br>)</pre><h3>Step 5: Request Permissions (iOS)</h3><p>For iOS, you need to request notification permissions:</p><pre>dart</pre><pre>Copy code</pre><pre>void initializeNotifications() async {<br>  const AndroidInitializationSettings initializationSettingsAndroid = AndroidInitializationSettings(&#39;@mipmap/ic_launcher&#39;);</pre><pre>  final IOSInitializationSettings initializationSettingsIOS = IOSInitializationSettings(<br>      onDidReceiveLocalNotification: onDidReceiveLocalNotification,<br>      requestSoundPermission: false,<br>      requestBadgePermission: false,<br>      requestAlertPermission: true,<br>  );</pre><pre>  final InitializationSettings initializationSettings = InitializationSettings(<br>      android: initializationSettingsAndroid,<br>      iOS: initializationSettingsIOS);</pre><pre>  await flutterLocalNotificationsPlugin.initialize(initializationSettings,<br>      onSelectNotification: selectNotification);</pre><pre>  // Request iOS notification permissions<br>  await flutterLocalNotificationsPlugin<br>      .resolvePlatformSpecificImplementation&lt;IOSFlutterLocalNotificationsPlugin&gt;()<br>      ?.requestPermissions(<br>        alert: true,<br>        badge: true,<br>        sound: true,<br>      );<br>}</pre><h3>Conclusion</h3><p>This guide should help you set up and show notifications in your Flutter app for both Android and iOS. You can customize the notification details further by exploring the flutter_local_notifications documentation and configuring it according to your needs. Notifications are a powerful way to keep your users engaged and informed, so make sure to implement them effectively in your app.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35ddc08d0f0d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Manage My SaaS Product’s APIs Without Losing My Mind]]></title>
            <link>https://medium.com/@mahimasanketh/how-i-manage-my-saas-products-apis-without-losing-my-mind-4700eb1a561e?source=rss-f8694579e10f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4700eb1a561e</guid>
            <category><![CDATA[api-management-tool]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[api-development]]></category>
            <category><![CDATA[api-management]]></category>
            <category><![CDATA[api-gateway]]></category>
            <dc:creator><![CDATA[Mahima Sanketh]]></dc:creator>
            <pubDate>Thu, 20 Mar 2025 09:28:53 GMT</pubDate>
            <atom:updated>2025-03-20T09:28:53.843Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*CBEu57XCiVK6hmvY3l8asw.jpeg" /><figcaption>API system illustration</figcaption></figure><h3>Introduction: The Chaos of API Management 🌀</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*0TPQwZrfoAGBaSnSNTI9NA.jpeg" /><figcaption>a woman developer frustrated with computer error</figcaption></figure><p>A few months ago, I found myself staring at a wall of API errors, rate limits, and unexpected bills that made me question my life choices. Running a SaaS means juggling multiple APIs — payment gateways, AI models, authentication services, and more. Managing them manually? A nightmare.</p><p>At first, I thought, <em>How hard can it be?</em> Just set up a few API keys, track usage in a spreadsheet, and monitor performance when things break, right? <strong>Wrong.</strong></p><h3>The Pain Points: What Went Wrong? ❌</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*v0HGmXT96GOmPeAgnym88g.jpeg" /><figcaption>404 error illustration</figcaption></figure><p>Here’s what I struggled with before I found a proper solution:</p><ul><li><strong>Unpredictable Costs:</strong> APIs like OpenAI, Stripe, and Firebase don’t warn you before they drain your wallet.</li><li><strong>Rate Limits &amp; Downtime:</strong> Random service failures and hitting API limits at critical moments.</li><li><strong>Lack of Insights:</strong> No clear way to track which API calls were slowing down my app.</li><li><strong>Security Risks:</strong> Manually handling API keys and credentials felt like a disaster waiting to happen.</li></ul><p>I needed something that didn’t just <strong>proxy requests</strong> but actually <strong>helped me understand and optimize API usage</strong> without requiring me to spend hours in logs or dashboards.</p><h3>The Hunt for an API Management Tool 🔍</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*A7Qu5dK7HvpHqcoZF_cu4A.jpeg" /><figcaption>Popular API managers</figcaption></figure><p>Like any good developer, I went down a rabbit hole, comparing platforms that claimed to solve my problems. I checked out:</p><ul><li><strong>Moesif</strong> — Great analytics, but pricey for a solo dev.</li><li><strong>Apigee (Google Cloud)</strong> — Powerful but way too complex for my needs.</li><li><strong>Postman</strong> — Good for testing, but not for real-time monitoring.</li><li><strong>Datadog</strong> — Overkill for my use case.</li><li><strong>Kong Konnect</strong> — Enterprise-focused, not startup-friendly.</li></ul><p>Every solution I found either:<br> ✅ Was too expensive<br> ✅ Was too complicated<br> ✅ Didn’t focus on <strong>API cost optimization</strong>, just performance</p><p>I needed something that fit my workflow — <strong>lightweight, insightful, and cost-effective</strong>.</p><h3>The Unexpected Solution That Worked for Me 💡</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-QG59twlM3eSGF36mLs9w.jpeg" /><figcaption>simple and clean web dashboard</figcaption></figure><p>I eventually landed on a tool that wasn’t a household name but ticked all the right boxes — <a href="https://jetpero.com/"><strong>Jetpero</strong></a>. It wasn’t just another API proxy or monitoring tool; it was built with <strong>cost-conscious developers and businesses in mind</strong>.</p><p>Here’s what stood out to me:</p><p>✔️ <strong>Instant Setup</strong> — Just add an API key, and it starts tracking.<br> ✔️ <strong>Cost Insights</strong> — It literally told me where I was <em>wasting money</em> on API calls.<br> ✔️ <strong>Custom Dashboards</strong> — Pre-built insights for OpenAI, Stripe, Firebase, and other common APIs.<br> ✔️ <strong>Real-Time Alerts</strong> — Warns me <em>before</em> I hit rate limits.<br> ✔️ <strong>AI-Powered Optimization</strong> — Helps predict future API costs based on usage patterns.</p><p>This wasn’t just <strong>another API tool</strong> — it actually <strong>helped me reduce my API costs</strong> while keeping my SaaS running smoothly.</p><h3>What I Learned from Automating My API Management 📌</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*LJHPumdbu_SqZWOSztVxGQ.jpeg" /><figcaption>definition of API management</figcaption></figure><p>After using <a href="https://jetpero.com/">Jetpero</a>, I changed the way I approach API management. Here are <strong>some takeaways</strong> that might help you if you’re running a SaaS:</p><p>1️⃣ <strong>Don’t Track APIs Manually</strong> — Spreadsheets and logs won’t cut it. You need a real-time dashboard.</p><p>2️⃣ <strong>Set Up Alerts Early</strong> — Rate limits and API failures can <strong>break your product</strong> if you don’t have instant notifications.</p><p>3️⃣ <strong>Optimize Before It’s Too Late</strong> — If you’re using APIs for AI, payments, or authentication, <strong>you need to track costs proactively</strong>.</p><p>4️⃣ <strong>Choose a Tool That Fits You</strong> — You don’t need an enterprise-grade API gateway. A simple, <strong>developer-friendly</strong> tool can save you time and money.</p><h3>Final Thoughts: Simplify, Automate, and Optimize 🚀</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*mVdcEF02VUszIu3CeCg4BA.jpeg" /><figcaption>happy developer</figcaption></figure><p>Managing APIs shouldn’t be <strong>a full-time job</strong>. Whether you’re a solo founder, a startup, or a growing business, automating API monitoring and cost tracking is <strong>essential</strong>.</p><p>I wish I had started using an API management tool earlier — it would have saved me <strong>countless debugging hours and unexpected API costs</strong>.</p><p>If you’re still managing APIs manually, consider making a switch. <strong>Your future self will thank you.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4700eb1a561e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft Unveils Majorana 1: The Future of Quantum Processors]]></title>
            <link>https://medium.com/@mahimasanketh/microsoft-unveils-majorana-1-the-future-of-quantum-processors-6d916b438a43?source=rss-f8694579e10f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d916b438a43</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[microsoft-quantum]]></category>
            <category><![CDATA[quantum-physics]]></category>
            <category><![CDATA[quantum-computing]]></category>
            <category><![CDATA[majorana-1]]></category>
            <dc:creator><![CDATA[Mahima Sanketh]]></dc:creator>
            <pubDate>Wed, 05 Mar 2025 15:36:43 GMT</pubDate>
            <atom:updated>2025-03-05T15:36:43.498Z</atom:updated>
            <content:encoded><![CDATA[<p>Quantum computing has long been hailed as the next frontier in technological innovation. In a groundbreaking announcement, <strong>Microsoft</strong> has introduced its latest advancement in this field — the <strong>Majorana 1 Quantum Processor</strong>. This revolutionary processor marks a pivotal step toward practical quantum computing, leveraging cutting-edge <strong>topological qubit technology</strong>.</p><h3>What is the Majorana 1 Quantum Processor?</h3><p>The <strong>Majorana 1</strong> processor is built on Microsoft’s unique <strong>Topological Core</strong> architecture. Unlike conventional quantum processors, which use fragile qubits that are highly prone to errors, Majorana 1 uses <strong>topological qubits</strong> — a more stable and error-resistant type of qubit.</p><p>Topological qubits leverage <strong>Majorana particles</strong>, which are quasiparticles that act as their own antiparticles. This unique property helps create qubits that are far more robust against environmental noise, one of the biggest challenges in quantum computing today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*xtoh-O0H__GWLzC0jf3RQQ.jpeg" /><figcaption>Majorana Quantum Chip</figcaption></figure><h3>How Topological Qubits Work</h3><p>Traditional qubits rely on extremely delicate superpositions that can be easily disturbed by temperature, radiation, or electromagnetic fields. However, <strong>topological qubits</strong> use quantum states that are spread out across space, making them much harder to disrupt.</p><p>These qubits are protected by the <strong>topological properties of matter</strong>, which means the data encoded within them remains stable even when the system undergoes small perturbations.</p><h3>Benefits of Topological Qubits:</h3><ul><li>Lower error rates</li><li>Longer coherence times</li><li>Higher scalability for future quantum systems</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*ZCR6qjOj7uOENepzm2mp-Q.jpeg" /><figcaption>Bits vs Quibits</figcaption></figure><h3>What Makes Majorana 1 Different?</h3><p>The <strong>Topological Core Architecture</strong> of Majorana 1 is a game-changer. Instead of simply scaling up the number of qubits like other companies, Microsoft is focused on making <strong>each qubit more reliable and efficient</strong>.</p><p>Key Features of Majorana 1:</p><ul><li>Topological qubits for higher stability</li><li>Scalable architecture</li><li>Reduced error rates</li><li>Groundbreaking use of <strong>Majorana fermions</strong></li></ul><p>According to Microsoft, this approach could drastically accelerate the timeline for achieving <strong>quantum advantage</strong> — the point at which quantum computers outperform classical computers in solving certain problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*Qc6HsU5l7oZsVH14VGNoXA.jpeg" /><figcaption>schematic of the Topological Core Architecture</figcaption></figure><h3>Why This Matters for the Future</h3><p>Quantum computers promise to revolutionize industries such as:</p><ul><li>Cryptography</li><li>Drug discovery</li><li>Climate modeling</li><li>Materials science</li><li>Financial simulations</li></ul><p>With Majorana 1, Microsoft is pushing the industry one step closer to practical, large-scale quantum computing — a milestone that could unlock solutions to problems previously thought impossible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*pyxpHUpgNObIJANv_a44rQ.jpeg" /><figcaption>quantum-computing-infographics</figcaption></figure><h3>What Experts Are Saying</h3><p>According to <strong>Satya Nadella</strong>, CEO of Microsoft:</p><blockquote><em>“Our breakthrough with Majorana 1 sets the foundation for the most scalable, fault-tolerant quantum computers ever built. This is the future of computing.”</em></blockquote><p>However, many scientists believe that significant breakthroughs are still <strong>years away</strong>. While Majorana 1 represents a critical step, the road to practical quantum computing remains long.</p><h3>Conclusion</h3><p>Microsoft’s <strong>Majorana 1 Quantum Processor</strong> could redefine the trajectory of quantum computing. By focusing on <strong>topological qubits</strong> rather than brute-force scaling, Microsoft is betting on a more sustainable and error-resistant future.</p><p>As the race to quantum advantage heats up, Majorana 1 positions Microsoft as a frontrunner in the quantum revolution.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d916b438a43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life After TikTok: How to Save Your Videos Before It’s Too Late]]></title>
            <link>https://medium.com/@mahimasanketh/life-after-tiktok-how-to-save-your-videos-before-its-too-late-b89c1eab76ef?source=rss-f8694579e10f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b89c1eab76ef</guid>
            <category><![CDATA[usa]]></category>
            <category><![CDATA[tik-tok]]></category>
            <category><![CDATA[banned]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[tiktok-app]]></category>
            <dc:creator><![CDATA[Mahima Sanketh]]></dc:creator>
            <pubDate>Sun, 19 Jan 2025 05:47:14 GMT</pubDate>
            <atom:updated>2025-01-19T05:47:14.578Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*UCitT98BQstYEEt0bwhrmg.jpeg" /><figcaption>Tik Tok Banned in USA</figcaption></figure><h3><strong>Introduction</strong></h3><p>TikTok has become one of the most popular social media platforms in the world, boasting over a billion active users. From viral dance challenges to educational content and everything in between, it’s no wonder that millions of people spend hours scrolling through the app daily.</p><p>But what happens if TikTok is banned in your country? Whether it’s due to privacy concerns or geopolitical tensions, the possibility of a TikTok ban has many creators and users worried. If you rely on TikTok for entertainment, connection, or even income, a ban could feel like the end of an era.</p><p>Don’t panic just yet! In this guide, we’ll break down what a TikTok ban could mean, how you can safeguard your content, and what steps you can take to stay ahead if the app disappears.</p><h3>Why TikTok Might Get Banned</h3><h4>Government Privacy Concerns</h4><p>TikTok’s parent company, ByteDance, has faced intense scrutiny over how it handles user data. Some governments believe TikTok collects more data than necessary, raising concerns about where that data might end up. Allegations about user data being shared with foreign governments have fueled debates about banning the app.</p><h4>Security Risks and Data Breaches</h4><p>Many cybersecurity experts argue that apps like TikTok pose risks to personal and national security. Whether it’s fears of unauthorized data access or potential breaches, these concerns have added fuel to the fire of banning discussions.</p><h4>Political and Economic Factors</h4><p>Beyond privacy and security, political tensions and trade disputes have also played a role. TikTok’s success as a Chinese-owned app in a competitive social media market has created friction, particularly in countries like the U.S. and India.</p><h3>Impact of a TikTok Ban</h3><h4>Creators and Their Livelihoods</h4><p>For content creators, TikTok isn’t just fun — it’s a source of income. Influencers who have built massive followings on TikTok often collaborate with brands and earn from sponsorships. If TikTok were banned, creators could lose access to their audience overnight, jeopardizing their income streams.</p><h4>Businesses Using TikTok Marketing</h4><p>Many small businesses and entrepreneurs use TikTok to promote their products and services. A ban could leave these businesses scrambling to find new ways to reach their target audience.</p><h4>Shift to Other Platforms</h4><p>In the event of a ban, creators and users will likely migrate to other platforms like Instagram Reels, YouTube Shorts, and Snapchat Spotlight. These platforms already offer similar features, but transitioning may take time and effort.</p><h3>How to Keep Your TikTok Videos Safe</h3><h4>Backing Up Your Videos</h4><p>To avoid losing your hard work, it’s essential to back up your TikTok content:</p><ol><li>Open the TikTok app and go to your profile.</li><li>Select a video, tap the share icon, and choose the “Save video” option.</li><li>Repeat this process for all your videos.</li></ol><h3>Exporting Content to Other Platforms</h3><p>Don’t let your creative efforts go to waste. Start reposting your videos to Instagram Reels, YouTube Shorts, or other platforms. These apps offer robust features to help you stay connected with your audience.</p><h3>Tools to Save TikTok Content</h3><p>Several tools, like SnapTik and TikSave, allow you to download TikTok videos in bulk, even after the app is banned. These tools can save your videos without the TikTok watermark, making them easier to repurpose</p><h3>Exploring Alternatives to TikTok</h3><h4>Instagram Reels</h4><p>Instagram Reels has quickly become a go-to platform for short-form videos. With its massive user base and integration into the Instagram app, it’s a great alternative for TikTok creators.</p><h4>YouTube Shorts</h4><p>YouTube Shorts is another rising competitor. It offers the advantage of YouTube’s monetization options, allowing creators to earn money through ad revenue.</p><h3>Emerging Platforms</h3><p>New apps like Triller and Clapper are also gaining traction as potential TikTok alternatives. These platforms offer similar features and are worth exploring if you’re looking to diversify.</p><h3>Tips for Creators to Prepare for a Ban</h3><h4>Build an Audience on Multiple Platforms</h4><p>Don’t put all your eggs in one basket! Start building a presence on other platforms like Instagram, YouTube, and Twitter to maintain your audience, even if TikTok goes away.</p><h4>Save and Repurpose Your Content</h4><p>Repurposing your existing TikTok videos can save time and effort. You can tweak them to fit the formats of other platforms like Reels or Shorts.</p><h4>Stay Engaged with Your Community</h4><p>Your followers are loyal to you, not just the platform. Use email newsletters, Discord servers, or other tools to stay connected with your community.</p><h3>Conclusion</h3><p>The potential banning of TikTok may sound alarming, but it doesn’t have to spell disaster. By taking proactive steps to back up your content, explore alternative platforms, and diversify your online presence, you can stay ahead of the curve. TikTok may be a cultural phenomenon, but your creativity and connection with your audience are what truly matter.</p><h3>FAQs</h3><h4>How likely is a TikTok ban in my country?</h4><p>The likelihood depends on your country’s specific concerns about data privacy and security.</p><h4>Will I lose my TikTok followers if the app is banned?</h4><p>Yes, but you can encourage followers to follow you on other platforms to stay connected.</p><h4>Can I still monetize my content without TikTok?</h4><p>Absolutely! Platforms like YouTube and Instagram offer excellent monetization opportunities.</p><h4>Are there tools to save all my TikTok videos in bulk?</h4><p>Yes, tools like SnapTik and TikSave make it easy to download your content.</p><h4>What’s the best alternative to TikTok for creators?</h4><p>Instagram Reels and YouTube Shorts are currently the most popular alternatives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b89c1eab76ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Apple’s September 9th Event: A Sneak Peek at the iPhone 16]]></title>
            <link>https://medium.com/@mahimasanketh/apples-september-9th-event-a-sneak-peek-at-the-iphone-16-de906464c316?source=rss-f8694579e10f------2</link>
            <guid isPermaLink="false">https://medium.com/p/de906464c316</guid>
            <category><![CDATA[events]]></category>
            <category><![CDATA[iphone]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[iphone-16]]></category>
            <dc:creator><![CDATA[Mahima Sanketh]]></dc:creator>
            <pubDate>Thu, 05 Sep 2024 13:56:20 GMT</pubDate>
            <atom:updated>2024-09-05T13:56:20.218Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5gcGpAdd5YM50NVFWAAIBQ.png" /></figure><p>Get ready for a tech-filled extravaganza! Apple’s annual September event is just around the corner, and the rumors are swirling about what we can expect. Let’s dive into the iPhone 16 leaks and see what might be in store:</p><p><strong>Design and Display:</strong></p><ul><li><strong>Sleek and Modern:</strong> Expect a refined look with curved edges and a slightly larger display on the iPhone 16 Pro Max.</li><li><strong>Dynamic Island:</strong> The Dynamic Island, that pill-shaped cutout at the top, is likely to stick around, offering a more immersive experience.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/299/1*G7Q36PKRk1cS-CjFaZ1FqA.jpeg" /></figure><p><strong>Camera Upgrades:</strong></p><ul><li><strong>Ultrawide Upgrade:</strong> The iPhone 16 Pro might get a 48MP ultrawide camera, matching the main camera for even better spatial video capture.</li><li><strong>Low-Light Magic:</strong> Expect even more impressive low-light photography and night mode.</li><li><strong>Action Button:</strong> The iPhone 16 Pro and Pro Max could introduce a customizable action button for added convenience.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*jkc9ZDmUBcYt_pDrmpdIEw.jpeg" /></figure><p><strong>Performance and Battery:</strong></p><ul><li><strong>A17 Bionic Power:</strong> The iPhone 16 series is rumored to be powered by the A17 Bionic chip, promising lightning-fast performance and improved battery life.</li><li><strong>Longer Battery Life:</strong> Expect to enjoy more screen time thanks to advancements in battery technology.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*-uDyBC6Sm6e1MTpyGt1b7A.jpeg" /></figure><p><strong>Other Exciting Features:</strong></p><ul><li><strong>USB-C Adoption:</strong> The iPhone 16 series might finally ditch Lightning for USB-C, aligning with the growing trend of universal charging.</li><li><strong>New Colors:</strong> Apple might surprise us with a fresh palette of colors for the iPhone 16 lineup.</li></ul><p><strong>Stay Tuned for the Official Reveal</strong></p><p>These are just rumors, so take them with a pinch of salt. The official event on September 9th will reveal the final details of the iPhone 16 series and other potential announcements. Get ready for a tech-packed event!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de906464c316" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is CrowdStrike? An In-Depth Look at Cutting-Edge Cybersecurity]]></title>
            <link>https://medium.com/@mahimasanketh/what-is-crowdstrike-an-in-depth-look-at-cutting-edge-cybersecurity-a2a66729c7c0?source=rss-f8694579e10f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2a66729c7c0</guid>
            <category><![CDATA[crowdstrike]]></category>
            <category><![CDATA[trends]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Mahima Sanketh]]></dc:creator>
            <pubDate>Fri, 19 Jul 2024 17:14:50 GMT</pubDate>
            <atom:updated>2024-07-19T17:14:50.667Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*vpD82q4LnJZjoq76XbUhcA.jpeg" /><figcaption>CrowdStrike Front Image ( credit — Ace Cloud Hosting )</figcaption></figure><p>In a world where cyber threats constantly evolve, robust cybersecurity measures are essential. CrowdStrike has emerged as a leader in this field, offering advanced solutions to protect against sophisticated attacks. But what exactly is CrowdStrike? In this article, we’ll delve into the details of CrowdStrike, its key features, and why it’s a crucial tool for modern cybersecurity.</p><p><strong>What is CrowdStrike?</strong></p><p>CrowdStrike is a cloud-native cybersecurity company that specializes in endpoint protection, threat intelligence, and cyberattack response services. Founded in 2011, CrowdStrike has quickly gained a reputation for its innovative approach to cybersecurity. Its flagship product, CrowdStrike Falcon, leverages artificial intelligence (AI) and machine learning to provide real-time protection against a wide range of threats.</p><p><strong>Key Features of CrowdStrike</strong></p><ol><li><strong>Endpoint Protection</strong></li></ol><p>CrowdStrike Falcon offers comprehensive endpoint protection by detecting, preventing, and responding to threats in real-time. Its lightweight agent runs on endpoints, continuously monitoring activities and identifying suspicious behavior.</p><p><strong>2. Threat Intelligence</strong></p><p>CrowdStrike provides detailed threat intelligence to help organizations understand and defend against potential attacks. This includes insights into adversaries, their tactics, techniques, and procedures (TTPs), and the latest threat trends.</p><p><strong>3. Cloud-Native Architecture</strong></p><p>The cloud-native design of CrowdStrike Falcon allows for rapid deployment and scalability. Updates and threat intelligence are delivered in real-time from the cloud, ensuring that systems are always protected against the latest threats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*nS1tdh0a8b8pLoQIrEs91Q.png" /></figure><p><strong>4. AI and Machine Learning</strong></p><p>CrowdStrike leverages AI and machine learning to analyze vast amounts of data and identify patterns that indicate potential threats. This advanced approach enables proactive threat detection and response.</p><p><strong>5. Incident Response</strong></p><p>CrowdStrike provides robust incident response capabilities, allowing organizations to quickly investigate and mitigate security incidents. This includes tools for forensic analysis, threat hunting, and remediation.</p><p><strong>Why Choose CrowdStrike?</strong></p><ol><li><strong>Proactive Defense</strong></li></ol><p>Unlike traditional antivirus solutions that rely on signature-based detection, CrowdStrike uses behavioral analysis and AI to detect threats proactively. This means it can identify and stop unknown threats before they cause damage.</p><p><strong>2. Comprehensive Coverage</strong></p><p>CrowdStrike Falcon protects against a wide range of threats, including malware, ransomware, and advanced persistent threats (APTs). Its holistic approach ensures that all endpoints are secured.</p><p><strong>3. Ease of Use</strong></p><p>The lightweight agent and cloud-native design make CrowdStrike easy to deploy and manage. Organizations can scale their protection as needed without complex infrastructure changes.</p><p><strong>4. Real-Time Threat Intelligence</strong></p><p>CrowdStrike’s threat intelligence provides organizations with up-to-date information on the latest threats. This enables them to stay ahead of adversaries and make informed security decisions.</p><p><strong>Real-World Applications</strong></p><p>CrowdStrike has been adopted by organizations across various industries, including finance, healthcare, and government. For example, a major financial institution implemented CrowdStrike Falcon to protect its endpoints, significantly reducing security incidents and improving overall protection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*BRWzMkmjfJx-Wr_ke266kw.png" /><figcaption>Credit — CrowdStrike</figcaption></figure><p><strong>Conclusion</strong></p><p>CrowdStrike is at the forefront of modern cybersecurity, offering advanced solutions that go beyond traditional antivirus software. With its AI-driven approach, cloud-native architecture, and comprehensive threat intelligence, CrowdStrike Falcon provides robust protection against today’s most sophisticated threats. As cyber threats continue evolving, a powerful tool like CrowdStrike is essential for safeguarding your organization’s digital assets.</p><p>Thanks — <a href="https://medium.com/u/8f244b667845">Simplenotion</a> x <a href="https://medium.com/u/f8694579e10f">Mahima Sanketh</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2a66729c7c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>