IAM
Welcome, champion! 🔥
You've mastered 0 of 83 lessons. Start your first lesson free — no signup needed.
About this course
Everyone logs in dozens of times a day, and few people can say what happens between typing a password and getting access. Identity and access management, or IAM, is the set of processes and protocols that decide who a user is and what they are allowed to do. This online IAM course on Abekus teaches it from first principles: the identity lifecycle, authentication factors and passkeys, authorisation models, SAML, OAuth 2.0, OpenID Connect and JWTs, privileged access management and zero trust, in short reading-card lessons each followed by an MCQ quiz.
Who this IAM course is for
It is written for engineering students, developers and junior security or IT staff who use logins every day but have never studied identity and access management. You should know roughly how a web request and response work; no earlier security training is needed. The course opens with one worked case, a login with a password and a one-time code traced step by step, and then names the ideas behind it. By the end you can explain how users are identified, authenticated and authorised, read an OAuth or OpenID Connect flow or a SAML assertion, pick the right grant, MFA method and access model for a case, and spot common identity weaknesses.
The course is vendor-neutral and built on the published standards: the OAuth 2.0 RFCs and the security best current practice in RFC 9700, OpenID Connect Core, the JWT RFCs, SAML 2.0, SCIM 2.0, WebAuthn and FIDO2, NIST SP 800-63B-4 for passwords and authenticators, and NIST SP 800-207 for zero trust. Cloud identity products appear only as one-line examples of a concept. It leaves out admin-console screens of any identity product, the AWS IAM policy language as a topic of its own, cryptographic internals beyond what token validation needs, Kerberos and Active Directory internals, and writing a full identity provider.
How the lessons work
Each lesson is a short set of reading cards on one idea, often with a raw HTTP request or redirect, a decoded JWT, a short SAML fragment or a small policy in JSON, followed by a quiz of multiple-choice questions. Lessons go from basics up: who gets in and the access principles, then joiner, mover and leaver processes and directories, passwords, multi-factor and phishing-resistant authentication, access control models and role design, single sign-on and SAML, OAuth roles, grants and security, OpenID Connect and JWT validation, privileged access, zero trust and governance, and finally comparisons and worked cases. You move at your own pace.
MCQ practice vs video courses for IAM
Video courses on Udemy, Coursera or YouTube are a good choice if you want to watch someone configure a particular identity provider. This course is built for a different job: a short explanation followed straight away by questions about real messages and decisions, such as which grant a mobile app should use, which claim in an ID token is wrong, whether a response should be 401 or 403, or which authenticator resists phishing. The protocols are precise and their names are easy to confuse, and answering questions is a quick way to find the gaps. Many learners use both: a video for a first walkthrough, and questions to make the details stick.
Common IAM mistakes
The course corrects these directly:
- Calling OAuth 2.0 an authentication protocol. OAuth is delegated authorisation; OpenID Connect adds authentication on top.
- Using the implicit grant for a single-page app. Current guidance is the authorisation code grant with PKCE.
- Assuming a JWT payload is encrypted. A signed JWT is only base64url-encoded, and anyone who holds it can read it.
- Requiring complex passwords that change every 90 days. NIST SP 800-63B-4 rules out composition rules and periodic changes, and relies on length and screening against breached passwords.
- Returning 403 for a user who is not logged in. 401 means unauthenticated; 403 means authenticated but not permitted.
- Saying NIST has banned SMS codes. SMS is a restricted authenticator, not a prohibited one.
- Leaving accounts active after someone leaves. Orphaned and dormant accounts are a standing risk.
Best way to learn IAM
Trace real flows. Watch the redirects during a single sign-on in your browser's developer tools, decode a token to see the claims inside, and ask of every system you use who can access what and who would notice if that were wrong. The last part of the course works this way: it compares SAML with OpenID Connect, OAuth with OpenID Connect and RBAC with ABAC, asks how to choose a grant type and an MFA method, and walks through sign-in with Google using OpenID Connect, employee single sign-on to a SaaS app with SAML, a mobile banking login with device binding, microservice API calls with client credentials and admin access through a PAM vault.