WSO2 Identity Platform (@wso2iamplatform) header
WSO2 Identity Platform (@wso2iamplatform) profile picture

Asgardeo is an IDaaS that helps developers implement secure and frictionless access to their applications. #Asgardeo by @WSO2

Joined December 2020
Photo by WSO2 Identity Platform (@wso2iamplatform)Photo by WSO2 Identity Platform (@wso2iamplatform)Photo by WSO2 Identity Platform (@wso2iamplatform)Photo by WSO2 Identity Platform (@wso2iamplatform)Photo by WSO2 Identity Platform (@wso2iamplatform)Photo by WSO2 Identity Platform (@wso2iamplatform)Photo by WSO2 Identity Platform (@wso2iamplatform)Photo by WSO2 Identity Platform (@wso2iamplatform)Photo by WSO2 Identity Platform (@wso2iamplatform)Photo by WSO2 Identity Platform (@wso2iamplatform)
Your passkey is phishing-resistant. Your recovery email isn't. Passkeys, magic links and one-time codes all take the password field out of your React app. Users stop inventing secrets. You stop maintaining password reset flows. So where does the risk go? Into recovery An attacker doesn't necessarily need to defeat the passkey. They may simply go after the fallback. If you're adding passwordless login to a React application, you're choosing between passkeys, magic links and OTP, and the trade-offs each one brings. The identity provider verifies the user, but the method you pick and the fallback behind it still decide how secure your login really is. In this guide, we cover: ⚡ What passwordless means for a React app, and why React shouldn't be the one verifying the user ⚡ How passkeys and WebAuthn work, and why a passkey won't sign in to the wrong site ⚡ How magic links work, and why the first click might come from an email scanner, not the user ⚡ When to use email or SMS OTP, and why SMS is the weakest option ⚡ Why passwordless isn't the same as MFA: an email code alone is still one factor ⚡ Why you should plan account recovery before you choose a method Your login is only as strong as its weakest fallback. Read the guide: wso2.com/identity-platform/l…
1
2
4
135
WSO2 Identity Platform retweeted
ThunderID has joined LF Decentralized Trust! 🎉 We’re excited to take our mission of open source IAM for humans, agents, and machines to a new level. Building agent identity, post-quantum crypto, or wallet interop? Come build with us.
Congrats to #ThunderID on joining LF Decentralized Trust as an incubating project. #opensource #IAM where #AI #agents get their own identity. Working on agent identity, post-quantum cryptography, wallet interop, or trust registries? Check it out: lfdecentralizedtrust.org/blo…
1
14
5
14
286
WSO2 Identity Platform retweeted
Today, WSO2 is contributing ThunderID to LF Decentralized Trust. It's an open source IAM for humans, AI agents, and machines, now under neutral governance. We’ll keep investing, and nothing changes for our customers. Read the story: lfdecentralizedtrust.org/blo…
2
6
254
Anyone can read your token. Even an attacker. Take a signed JSON Web Token (JWT), split it at the dots, decode the payload, and you can see what's inside. No secret key needed. No special tools. So why do applications trust JWTs? Because signed JWTs aren't designed to hide information. Their signatures allow applications to verify that the contents haven't been tampered with. But even a properly signed and validated JWT can become a security risk if an attacker gets hold of it. If you've built authentication into a React application, you've probably worked with access tokens, ID tokens, and the question of where to store them. In this guide, we cover: ⚡ What's inside a JWT, and why encoding isn't encryption ⚡ How digital signatures work, and why decoding a token isn't the same as validating it ⚡ How storing access tokens in localStorage exposes them to XSS attacks ⚡ The trade-offs between sessionStorage, memory, HttpOnly cookies, and a Backend for Frontend (BFF) ⚡ What happens when tokens expire, refresh requests overlap, or users log out Authentication SDKs handle much of the token lifecycle, but understanding how those tokens are handled helps you make informed decisions about your application's security. Read the guide: wso2.com/identity-platform/l…
1
1
77
Your React app can’t keep a secret. Not even one. Anything shipped to the browser can be inspected. Your JavaScript, your API requests, even the tokens your app handles. So how does your React app securely log users in? That's where Authorization Code Flow with PKCE comes in. If you've ever added login to a React app using an authentication SDK, chances are you've used this flow without giving it much thought. But the next time someone asks why your login is safe, “the SDK handles it” isn’t a great answer. This guide pulls back the curtain on what really happens when a user clicks Sign in: ⚡ What OAuth 2.0 does, what OpenID Connect adds, and why your app needs both ⚡ Why a stolen authorization code is useless without the code verifier ⚡ What the /authorize and /token requests actually send, parameter by parameter ⚡ How to watch the whole flow happen in your own React app ⚡ Why a valid signature isn’t the end of token validation Your SDK can abstract away the code. It shouldn't abstract away your understanding. Read the guide: wso2.com/identity-platform/l…
2
6
213
As a React developer, it’s becoming more and more important to understand everything it takes to secure user login and implement access control. Getting login working is the easy part. Pick a library, add a sign-in button, wire up a callback. The hard part starts right after ⚡ Where should authentication state live? ⚡ Should your React app ever handle tokens directly? ⚡ If it does, where should those tokens be stored? ⚡ When the frontend says a user is an admin, who gets the final say? This guide steps away from SDKs and code samples to focus on the architecture underneath: the flow you choose, how you handle tokens, and where you draw the trust boundary. You don’t need to become an IAM expert, but you should make these calls on purpose, before you npm install your way into an architecture you never chose. Read the guide: wso2.com/identity-platform/l…
5
5
103
WSO2 Identity Platform retweeted
Stronger security doesn't have to mean a worse user experience. WSO2 Ambassador Prabakaran Thodithot Sembiyan dives deep into getting MFA right from best practices and adaptive auth, to the right auth at the right time. Watch here: youtube.com/watch?v=MRDk_8UU…
2
3
277
WSO2 Identity Platform retweeted
Great to see @ayshsandu , Director/Architect at WSO2, featured on the @AgenticAIFdn blog in her role as an AAIF Ambassador for South Asia. In her article, Ayesha explores the latest MCP authorization specification, explaining how the hardened authorization flow works and why it matters for building secure AI agents and agentic systems. Read it here: aaif.io/blog/the-anatomy-of-…
The MCP authorization spec just shipped a security-hardening pass, and it's worth understanding what changed and why. @ayshsandu walks the full flow against the 2026-07-28 spec: discovery, client identity via CIMD, audience binding with the resource parameter, and the new firm requirement for issuer validation on authorization responses. That last one matters. Without it, the IdP mix-up attack is the mirror image of audience confusion, and both have the same root: nobody checked who they were actually talking to. The post also covers why token passthrough is a structural failure, not just bad practice, and where OAuth hands off to the agent layer on step-up. aaif.io/blog/the-anatomy-of-…
1
2
3
510
WSO2 Identity Platform can simplify login and user management for React apps, and that's exactly what we talked about at our booth at @ReactNexus . Great meeting so many React developers and hearing how identity actually shows up in your projects. Thanks to everyone who stopped by to share ideas, ask questions, and dig into what's possible.
1
1
169
One of the highlights from @ReactNexus : @omal_vindula on rethinking access control in React apps. Most apps bolt it on with role checks scattered across components. Omal showed a cleaner pattern, built on WSO2 Identity Platform.
1
1
280
React Nexus @ReactNexus is on right now, and our team is here. Come find us to see what's new in WSO2 Identity Platform for React developers: the latest updates, what's coming next, and some good swag to take home.
2
5
273
You logged into your React app. Now what? Once a user is in, who decides what they can touch?Most apps bolt this on with role checks sprinkled through components. There's a cleaner way to think about access control, and in his talk @omal_vindula unpacks how with @wso2iamplatform #wso2 #wso2IAM
2
153
WSO2 Identity Platform retweeted
You don't build an open source IAM stack alone, you build it with a community. Great to be at Open Source Summit India showing what we've started building with ThunderID. The conversations were the best part. #OSSummit #ThunderID #IAM
1
2
76
WSO2 Identity Platform retweeted
Background/Ambient agents act when nobody's watching. So who approves what they do? @ayshsandu broke it down at MCP Dev Summit Bengaluru: CIBA for backchannel approval, just-in-time delegation, and related security patterns. #MCPDevSummit #ThunderID
1
3
91
WSO2 Identity Platform retweeted
Win 5 FREE tickets to React Nexus! ✅ Try the ThunderID React Quickstart - tinyurl.com/peva2utf ✅ Write a blog post or create a short video ✅ Submit this form - forms.gle/fDPvsCBHVUQLm2G59 @ReactNexus
7
2
11
618
WSO2 Identity Platform retweeted
We're at Open Source Summit India!👋 Building the next generation of open-source IAM stack. Stop by our table, see what we're working on, share your feedback, and ⭐ the repo if it resonates with you. github.com/thunder-id/thunde… #OSSummit #IAM #ThunderID
12
1
13
244
WSO2 Identity Platform retweeted
What's next for Identity and Access Management in a world of humans and AI agents. If you're attending #OSSummit India, don't miss Thivaharan Kalyanasundaram from the ThunderID team talking about Identity and Access Management for the Decade Ahead. #ThunderID @IAM
2
2
101
WSO2 Identity Platform retweeted
A secure AI agent shouldn't just know what to do, it should know who is asking. @DPS_Dilshan and @hasini_sama from the ThunderID team are sharing how to secure MCP servers with identity-aware authorization and human controls at #MCPDevSummit Mumbai @AgenticAIFdn today.
3
3
79
WSO2 Identity Platform retweeted
If you're attending #MCPDevSummit Mumbai @AgenticAIFdn, join @ayshsandu from the ThunderID team to talk about why #MCP hosts need their own identity, delegation model, and audit trails.
2
3
83
WSO2 Identity Platform retweeted
ThunderID is here. Open source IAM built for the next decade: AI agents as first-class identities, post-quantum-safe by design, decentralized identity integration from the start. Come be part of it. thunderid.dev/blog/introduci…
3
2
67