<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>JWT on API Coding</title>
    <link>https://apicoding.com/tags/jwt/</link>
    <description>Recent content in JWT on API Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 06 Oct 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicoding.com/tags/jwt/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>API Authentication: JWT, OAuth2, and API Keys Each Have a Job</title>
      <link>https://apicoding.com/2025/10/06/api-authentication-jwt-oauth2-and-api-keys-each-have-a-job/</link>
      <pubDate>Mon, 06 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://apicoding.com/2025/10/06/api-authentication-jwt-oauth2-and-api-keys-each-have-a-job/</guid>
      <description>&lt;p&gt;API authentication is the area where implementation decisions have the most direct security consequences and where the choice of mechanism is most frequently driven by familiarity rather than fit. Teams that have used JWTs extensively reach for JWTs. Teams that have configured OAuth2 once and survived it reach for OAuth2. Teams that want something simple reach for API keys. Each choice reflects a different problem being solved, and using the wrong mechanism for the problem introduces either unnecessary complexity or genuine security gaps.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
