Free & open · no paywall, ever

IntegrAuth Academy

Identity, security and practical AI — free, from zero. Byte-sized lessons, real diagrams, hands-on labs, zero fluff. Two programs, each with its own exam and certificate.

20 tracks 241 lessons 242 hands-on labs 230+ diagrams 100% free

English is hard? Your browser can translate this page into Tamil, Telugu, Kannada, Malayalam or Hindi. Tech words stay in English so you learn the real names.

How?
  • Chrome on phone: ⋮ menu → Translate
  • Chrome on computer: right-click → Translate to …
  • Edge: the translate icon in the address bar
Identity & API Security Track 11 · Customer Identity (CIAM)
0/166 lessons read
CUSTOMER IDENTITY · LESSON 10

The big picture

In this track, the people who sign in are your customers. There are millions, and you cannot remove them. One idea runs through everything: friction against trust. Ask for too much and you lose the customer. Ask for too little and you lose trust.

The story you just lived

Maya starts as a stranger at your signup form (signup). The form is a door with one short line and one honest check that her email or phone is hers.

Then she forgets her password (recovery). Attackers love this side door, so the way back in must be as strong as the way in.

Next she taps "continue with your social account" (social login). Same email does not mean same person. Account linking is safe only with a verified email and fresh proof of the old account.

You learn who she is little by little, with progressive profiling and honest consent. Each yes is as easy to withdraw as to give.

Her account is worth stealing, so you build layers against account takeover. A passkey ends credential stuffing for that account. Then you move the whole customer base with lazy migration so nobody notices (user migration).

Sam's company buys your product for forty people. So you build B2B identity: organizations, invites, org-scoped roles and tenants with their own SSO. Numbers change and phones get lost, so you plan the whole life of the account (new number, new phone, leaving). Last, in wallets & verifiable credentials, Maya carries signed proofs (verifiable credentials). She shows each service only what it needs. That is selective disclosure.

Strangerjust arrivedSignup & verifyone honest checkAccountrecover · link safely· defendProfile & consentlearned over timeTrustedperson → wholeorganizationsfriction ↓ — ask less as trust growstrust ↑ — earn it, then guard it: every side door as strong as the front
Figure — The customer's journey on one page. A stranger enters through a light, verified signup. She gets an account that you defend and let her recover. You learn about her honestly over time. At the end, one person grows into whole organizations. Left to right, you ask for less. Top to bottom, you earn trust and then guard it. These are the two forces this track balances.

Two views of the same product

You are a customer of many apps. Read each lesson from both sides.

LessonWhat Maya feelsWhat you build
Signup"Quick. I am in."A short form and one real check
Recovery"I can get back in, fast."A side door as strong as login, with alerts
Social login"One tap."Link only after a verified email and a re-login
Consent"I decide, and I can say no."Separate, recorded choices that are easy to withdraw
Takeover"I am safe, and nobody nags me."Layers, with friction only where the risk is
Migration"Nothing changed."Bulk import, lazy migration, a trickle and a rollback
Teams"My boss added me in a click."Tenants, invites and org roles
Wallets"I show only what is needed."Verify the signature, keep no copy
Why it matters

Now you can hold both halves in a product review. Growth says "remove that field". Security says "not without a check".

Where these ideas go next

Takeover defense gets smarter with risk-based, adaptive challenges. The recovery side door meets its nastiest attacker in SIM swap. Keeping one customer's world apart from another's is the job of multi-tenancy.

Ready to test yourself? The cheat sheet & pop quiz is one page on.