Sitemap
Hesanda Nimneth Liyanage

Hesanda Nimneth Liyanage

Undergradute at University of Colombo School of Computing. Java Enthusiast. Linkedin - https://www.linkedin.com/in/hesanda-liyanage/

My understanding on Identity Server

2 min readAug 19, 2026

--

Press enter or click to view image in full size

What is IAM, quickly

IAM (Identity and Access Management) is just the system that checks two things every time someone tries to use an app: who are you, and what are you allowed to do. Every login screen you’ve ever seen is IAM doing its job. Most companies don’t build this themselves anymore — they use a dedicated IAM product for it.

Where you’d use something like this

  • A company with multiple internal apps wants employees to log in once and access all of them, instead of separate logins for each one.
  • A customer-facing app needs signup, login, password reset, and social login (Google/Facebook) without building all that from scratch.
  • Securing APIs and microservices so they can trust each other without each one handling auth on its own.
  • Any place that needs proper access control — who can view what, who can edit what — with an audit trail behind it.

So what is WSO2 Identity Server

WSO2 Identity Server (WSO2 IS) is WSO2’s IAM product, and it’s been around for over 15 years, so it’s pretty battle-tested. It’s open source, and it’s used by banks, telcos, and governments, not just small startups.

Get Hesanda Nimneth Liyanage’s stories in your inbox

Join Medium for free to get updates from this writer.

At its core, it does the standard IAM stuff:

  • Authentication — verifying who someone is (password, OTP, social login, biometrics, whatever you configure)
  • Authorization — deciding what they can access once they’re in
  • Single sign-on (SSO) — log in once, get into every connected app without logging in again
  • User management — creating, updating, disabling accounts, all from one place

How it’s built, simply

It’s built on WSO2’s Carbon platform, which basically means everything is broken into separate, swappable components — one part handles SAML, one handles OAuth, one handles user stores, and so on. That makes it easy to extend or customize without touching the whole system.

It talks in standard protocols — OAuth2, OpenID Connect, SAML2, SCIM — so it plays nicely with basically any app or tool out there, no proprietary lock-in.

It also doesn’t force you to move your existing users into it. If you’ve already got users in Active Directory or LDAP, WSO2 IS just connects to that through built-in connectors and sits as a layer on top.

One feature worth mentioning is adaptive authentication — it can ask for extra verification only when something looks unusual (new device, different location), instead of always demanding MFA from everyone on every login.

Wrapping up

WSO2 Identity Server is basically the layer that handles login, access control, and single sign-on for your apps, so you don’t have to build and secure that yourself. It’s standards-based, connects to whatever user store you already have, and has been proven at real enterprise scale for a long time.

Docs are at is.docs.wso2.com if you want to dig deeper.

--

--

Hesanda Nimneth Liyanage
Hesanda Nimneth Liyanage

Written by Hesanda Nimneth Liyanage

Undergradute at University of Colombo School of Computing. Java Enthusiast. Linkedin - https://www.linkedin.com/in/hesanda-liyanage/