{"id":65,"date":"2026-10-22T17:15:00","date_gmt":"2026-10-22T17:15:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/22\/jwt-logout-token-revocation\/"},"modified":"2026-10-22T17:15:00","modified_gmt":"2026-10-22T17:15:00","slug":"jwt-logout-token-revocation","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/22\/jwt-logout-token-revocation\/","title":{"rendered":"JWT ile Logout Problemi: Stateless Token Nas\u0131l \u0130ptal Edilir?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">JWT&#8217;nin en \u00e7ok sevilen \u00f6zelli\u011fi stateless olmas\u0131d\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Token imzal\u0131d\u0131r. \u0130\u00e7inde kullan\u0131c\u0131 kimli\u011fi, rolleri ve son kullanma tarihi vard\u0131r. Sunucu imzay\u0131 do\u011frular ve iste\u011fi kabul eder. Veritaban\u0131na veya session store&#8217;a gitmeye gerek yoktur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sonra \u015fu gereksinim gelir:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">Kullan\u0131c\u0131 \u00e7\u0131k\u0131\u015f yapt\u0131\u011f\u0131nda token ge\u00e7ersiz olmal\u0131.<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Veya daha kritik olan\u0131:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">Hesab\u0131 ele ge\u00e7irilen kullan\u0131c\u0131n\u0131n b\u00fct\u00fcn oturumlar\u0131 an\u0131nda kapat\u0131lmal\u0131.<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Ve stateless olman\u0131n bedeli ortaya \u00e7\u0131kar.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Token kendini iptal edemez<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bir JWT, imzas\u0131 ge\u00e7erli oldu\u011fu ve s\u00fcresi dolmad\u0131\u011f\u0131 s\u00fcrece ge\u00e7erlidir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Frontend taraf\u0131nda logout genellikle token&#8217;\u0131 local storage&#8217;dan silmektir. Bu kullan\u0131c\u0131n\u0131n taray\u0131c\u0131s\u0131nda oturumu kapat\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama token&#8217;\u0131n kendisi h\u00e2l\u00e2 ge\u00e7erlidir. Bir \u015fekilde kopyaland\u0131ysa, \u00f6rne\u011fin bir XSS a\u00e7\u0131\u011f\u0131yla veya log&#8217;a yaz\u0131ld\u0131ysa, s\u00fcresi dolana kadar kullan\u0131labilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Access token&#8217;\u0131n \u00f6mr\u00fc 24 saat ise, iptal edilmi\u015f bir oturum 24 saat boyunca \u00e7al\u0131\u015fmaya devam edebilir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">K\u0131sa \u00f6m\u00fcr<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">En temel \u00f6nlem access token&#8217;\u0131n \u00f6mr\u00fcn\u00fc k\u0131sa tutmakt\u0131r.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>access token:  5-15 dakika\nrefresh token: g\u00fcnler veya haftalar<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Access token \u00e7al\u0131nsa bile kullan\u0131labilece\u011fi s\u00fcre s\u0131n\u0131rl\u0131d\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kullan\u0131c\u0131 deneyimi bozulmas\u0131n diye uzun \u00f6m\u00fcrl\u00fc bir refresh token ile yeni access token al\u0131n\u0131r. Refresh token ise stateless de\u011fildir. Sunucuda saklan\u0131r ve iptal edilebilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu sayede kontrol noktas\u0131 her istekte de\u011fil, her refresh i\u015fleminde devreye girer. Logout oldu\u011funda refresh token iptal edilir ve en ge\u00e7 birka\u00e7 dakika i\u00e7inde oturum ger\u00e7ekten sona erer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bence JWT kullanan \u00e7o\u011fu sistem i\u00e7in do\u011fru denge bu.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Refresh token rotation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Refresh token uzun \u00f6m\u00fcrl\u00fc oldu\u011fu i\u00e7in \u00e7al\u0131nmas\u0131 daha tehlikelidir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rotation yakla\u015f\u0131m\u0131nda her refresh i\u015fleminde yeni bir refresh token verilir ve eskisi ge\u00e7ersiz hale gelir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>POST \/auth\/refresh\nrefresh_token: R1\n\n\u2192 access_token: A2\n\u2192 refresh_token: R2   (R1 art\u0131k ge\u00e7ersiz)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Burada g\u00fczel bir g\u00fcvenlik \u00f6zelli\u011fi var. E\u011fer R1 tekrar kullan\u0131l\u0131rsa, bu ya bir sald\u0131rgan\u0131n ya da ger\u00e7ek kullan\u0131c\u0131n\u0131n elinde eski bir token oldu\u011fu anlam\u0131na gelir. \u0130kisinden biri token&#8217;\u0131 \u00e7alm\u0131\u015ft\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">OAuth g\u00fcvenlik \u00f6nerileri bu durumda o token ailesinin tamam\u0131n\u0131n iptal edilmesini \u00f6neriyor. Kullan\u0131c\u0131 tekrar giri\u015f yapmak zorunda kal\u0131r ama sald\u0131rgan\u0131n eri\u015fimi de kesilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Uygulamada dikkat edilmesi gereken nokta, mobil uygulamalar\u0131n a\u011f problemleri nedeniyle ayn\u0131 refresh iste\u011fini iki kez g\u00f6nderebilmesidir. \u00c7ok k\u0131sa bir tolerans s\u00fcresi tan\u0131mlamak gereksiz logout&#8217;lar\u0131 \u00f6nler.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">An\u0131nda iptal gerekiyorsa<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Baz\u0131 durumlarda birka\u00e7 dakika bile \u00e7ok uzundur. Kullan\u0131c\u0131n\u0131n yetkileri kald\u0131r\u0131ld\u0131ysa veya hesap kapat\u0131ld\u0131ysa eri\u015fim hemen bitmeli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bunun i\u00e7in access token&#8217;\u0131n <code>jti<\/code> de\u011feri bir denylist&#8217;e eklenebilir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SET revoked:jti:9f1c... 1 EX 600<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">TTL, token&#8217;\u0131n kalan \u00f6mr\u00fc kadar tutulur. S\u00fcresi dolan token zaten ge\u00e7ersiz olaca\u011f\u0131 i\u00e7in listede kalmas\u0131na gerek yoktur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Alternatif olarak kullan\u0131c\u0131 baz\u0131nda bir &#8220;token version&#8221; veya &#8220;tokens valid after&#8221; zaman\u0131 tutulabilir. Bu zamandan \u00f6nce \u00fcretilmi\u015f b\u00fct\u00fcn token&#8217;lar reddedilir. Tek bir de\u011ferle kullan\u0131c\u0131n\u0131n b\u00fct\u00fcn oturumlar\u0131 kapat\u0131labilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Her iki y\u00f6ntem de her istekte bir kontrol gerektirir. Yani JWT&#8217;nin stateless avantaj\u0131n\u0131n bir k\u0131sm\u0131ndan vazge\u00e7ilmi\u015f olur. Redis&#8217;te tek bir key kontrol\u00fc genellikle kabul edilebilir bir maliyettir. Ama bu noktada \u015fu soruyu sormak da gerekiyor: zaten her istekte state kontrol ediyorsak, klasik bir session neden kullanm\u0131yoruz?<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Belki session yeterlidir<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Tek bir web uygulamas\u0131 ve onun backend&#8217;i varsa, HttpOnly ve Secure flag&#8217;li bir session cookie \u00e7o\u011fu zaman JWT&#8217;den daha basit ve daha g\u00fcvenlidir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130ptal an\u0131nda ger\u00e7ekle\u015fir. Token JavaScript taraf\u0131ndan okunamaz. Token boyutu nedeniyle header&#8217;lar \u015fi\u015fmez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">JWT&#8217;nin ger\u00e7ek avantaj\u0131, token&#8217;\u0131 \u00fcreten ile do\u011frulayan taraflar\u0131n farkl\u0131 oldu\u011fu durumlarda ortaya \u00e7\u0131kar. Bir kimlik sa\u011flay\u0131c\u0131n\u0131n \u00fcretti\u011fi token&#8217;\u0131 bir\u00e7ok ba\u011f\u0131ms\u0131z servisin do\u011frulamas\u0131 gibi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">JWT bir session mekanizmas\u0131 olarak de\u011fil, servisler aras\u0131nda ta\u015f\u0131nabilir ve do\u011frulanabilir bir kimlik beyan\u0131 olarak d\u00fc\u015f\u00fcn\u00fcld\u00fc\u011f\u00fcnde daha do\u011fru yerine oturuyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Logout problemi de genellikle, JWT bir session&#8217;\u0131n yerine kullan\u0131lmaya \u00e7al\u0131\u015f\u0131ld\u0131\u011f\u0131nda ortaya \u00e7\u0131k\u0131yor.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Kullan\u0131c\u0131 \u00e7\u0131k\u0131\u015f yapt\u0131 ama token h\u00e2l\u00e2 ge\u00e7erli. JWT&#8217;nin stateless yap\u0131s\u0131 iptal gerekti\u011finde nas\u0131l y\u00f6netilir? K\u0131sa \u00f6m\u00fcrl\u00fc access token, refresh rotation ve denylist.<\/p>\n","protected":false},"author":1,"featured_media":64,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-65","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-api-tasarimi"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/65","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=65"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/65\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/64"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=65"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=65"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=65"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}