01 / guides
Topic guides
Authentication, authorization, federation, provisioning and audit, plus OAuth security, mobile and social login. Each guide answers the practical question first.
Browse the guidesOAuth · OpenID Connect · SAML · SCIM · JWT
An independent reference library for developers and architects who build sign-in, federation and API access. Plain explanations of the standards, current security advice, and free tools that run entirely in your browser.
01 / guides
Authentication, authorization, federation, provisioning and audit, plus OAuth security, mobile and social login. Each guide answers the practical question first.
Browse the guides02 / tools
Decode JWTs and SAML messages, generate PKCE pairs, build authorize URLs and write security headers. All client-side.
See all tools03 / platforms
What API gateways, federation servers, policy engines and identity governance systems do, and how to choose, without vendor spin.
Compare categoriesRFC 6749
Delegated authorization. A client gets a scoped access token to call an API on a user's behalf, without ever seeing the password.
OAuth security guideOIDC Core 1.0
Identity on top of OAuth 2.0. The ID token is a signed JWT that says who signed in, when, and how.
From OpenID to OIDCOASIS 2005
XML assertions for browser single sign-on. Still the workhorse of enterprise SSO into SaaS.
Federation guideRFC 7643/7644
A REST schema and protocol for creating, updating and removing user accounts across systems.
Provisioning guideRFC 7519
A compact, URL-safe token format: a header, a set of claims and a signature, joined by dots.
Decode a JWTXACML 3.0
Policy-based authorization. Decisions come from attributes of the user, resource, action and context.
Authorization guideDecode a JWT's header and claims, check expiry, spot risky algorithms and verify HS256 signatures locally.
Create a code_verifier and its S256 code_challenge, plus random state and nonce values, with WebCrypto.
Decode POST and Redirect binding messages, pretty-print the XML and pull out issuer, subject, conditions and attributes.
Build an OAuth 2.0 or OpenID Connect authorize URL parameter by parameter, with warnings for insecure combinations.
Generate HSTS, CSP, Referrer-Policy and nosniff headers for nginx, Apache, IIS, Jetty and static hosts.
How the 2014 POODLE attack broke SSLv3, why RFC 7568 and RFC 8996 later retired SSLv3, TLS 1.0 and 1.1, and which TLS settings to use for identity and API servers.
A line-by-line guide to AD FS claim rules that query LDAP attribute stores: conditions, issue versus add, store, types, query format, param and escaping rules.
How to add an LDAP attribute store to AD FS, connect it to AD LDS or another directory, and use it in claim rules for attributes AD does not hold.
Why OAuth 2.0's state parameter exists, the CSRF attack it stops, how to generate and check it, and how state, PKCE and nonce divide the work under RFC 9700.
How service provider initiated sign-in works, why Windows Identity Foundation only covered WS-Federation, and the options for SAML 2.0 and OIDC on ASP.NET Core.
A practical curriculum for teaching API security to developers spread across offices and countries: modules, hands-on labs, formats and how to measure if it worked.
Spec editors, security researchers and identity engineers discuss drafts, incidents and fixes on X every day. These searches open the latest posts on x.com in your browser.
Pick a tip or write your own. Counted the way X counts: links take 23 characters.
0 / 280Post on X
Twobo Technologies is not affiliated with X Corp. Links open x.com; nothing on this page connects to your account.
Neither. It is an independent educational site with guides and free developer tools on identity and API security. It sells nothing, resells nothing and has no vendor partnerships, so product pages describe categories and products neutrally.
No. The JWT decoder, PKCE generator, SAML decoder, URL builder and header builder run as JavaScript in your browser. Nothing you paste is uploaded, logged or stored on a server. You can load a tool page, go offline, and it keeps working.
Treat any live token as a credential. Our decoder runs locally, but the safer habit is to paste expired or test tokens, and to revoke a production token if it ever ends up somewhere it should not be, such as a chat or a ticket.
OAuth 2.0 (RFC 6749) is an authorization framework: it lets a client get an access token to call an API. OpenID Connect is an identity layer on top of OAuth 2.0 that adds the ID token, a signed JWT that tells the client who the user is and how they signed in.
Not yet. As of November 2026, OAuth 2.1 is still an IETF Internet-Draft (draft-ietf-oauth-v2-1). Its main rules, such as PKCE for every authorization code flow and no implicit or password grants, already appear in RFC 9700, the OAuth 2.0 Security Best Current Practice published in January 2025.
Yes, where it already works. SAML 2.0 remains the most common protocol for enterprise single sign-on into SaaS applications. For new consumer, mobile and API work, OpenID Connect and OAuth 2.0 are usually the better fit.