<\/div>\n

Merhaba,<\/p>\n

Bu i\u00e7eri\u011fimizde kanaatim odur ki Asp.NET Core a\u00e7\u0131s\u0131ndan .NET 8 ile gelen en g\u00fczel \u00f6zelliklerden birini, Identity API Endpoints<\/em> \u00f6zelli\u011fini inceleyece\u011fiz. Bu \u00f6zellik sayesinde uygulamalar\u0131m\u0131zdaki temel kullan\u0131c\u0131 i\u015flemlerini ger\u00e7ekle\u015ftirdi\u011fimiz Identity mekanizmas\u0131<\/a>n\u0131n art\u0131k daha pratik ve etkin bir \u015fekilde kullan\u0131labildi\u011fini ve \u00f6zellikle API dostu bir alternatif y\u00f6ntemin olabilece\u011fini g\u00f6zlemliyor olaca\u011f\u0131z. O halde buyurun ba\u015flayal\u0131m…<\/p>\n

Asp.NET Core Identity Nedir?<\/h3>\n
Asp.NET Core Identity, geli\u015ftirdi\u011fimiz uygulamalarda kullan\u0131c\u0131 yetkilendirme, kimlik do\u011frulama ve rol y\u00f6netimi sa\u011flayan bir framework’t\u00fcr. Bu framework sayesinde kullan\u0131c\u0131 kaydetme, giri\u015f yapma, rol atama, \u015fifre s\u0131f\u0131rlama ve Google, Facebook gibi external identity provider’larla entegrayon vs. gibi temel kimlik y\u00f6netimi i\u015flemlerini kolayl\u0131kla ger\u00e7ekle\u015ftirebilmekteyiz.<\/p>\n
Identity mekanizmas\u0131n\u0131n \u00e7ekirde\u011fi Data model<\/em>, Stores<\/em> ve Managers<\/em> olmak \u00fczere \u00fc\u00e7 ana soyutlamaya dayanmaktad\u0131r.<\/p>\n
\n
Data model<\/em><\/strong>
\nIdentity mekanizmas\u0131nda temel t\u00fcrlerini tarif eden modellerdir. Bu modeller, IdentityUser<\/code> ve IdentityRole<\/code> interface’leri \u00fczerinden implementasyonlarla sa\u011flan\u0131r.\n<\/li>\n
Stores<\/em><\/strong> \nVeri modellerini fiziksel olarak depolamak ve sorgulamak i\u00e7in kullan\u0131lan katmand\u0131r. IUserStore<\/code> ve IRoleStore<\/code> gibi interface’ler i\u00e7ermektedir.\n<\/li>\n
Managers<\/em><\/strong> \nKullan\u0131c\u0131 y\u00f6netimi i\u00e7in Stores \u00fcst\u00fcnde bir service katman\u0131 sa\u011flayan s\u0131n\u0131flard\u0131r. Bu servisler; UserManager<\/code>, RoleManager<\/code> ve SignInManager<\/code>‘d\u0131r.\n<\/li>\n<\/ul>\nBu g\u00fcne kadar Asp.NET Core mimarisinde mevcut olan Identity mekanizmas\u0131na dair tam teferruatl\u0131 bilgi edinmek i\u00e7in Asp.NET Core Identity \u2013 Yaz\u0131 Dizisi<\/a>ni takip etmenizi \u00f6neririm.<\/em><\/p><\/blockquote>\n Neden Identity API Endpoint’e \u0130htiyac\u0131m\u0131z Var?<\/h3>\nIdentity mekanizmas\u0131n\u0131n data modelleri \u00fczerinden kullan\u0131c\u0131 ile ilgili gerekli modellemeyi h\u0131zl\u0131ca ger\u00e7ekle\u015ftirebiliyor ve y\u00f6netici(managers) s\u0131n\u0131flar\u0131 sayesinde de kullan\u0131c\u0131 i\u015flemlerini rahatl\u0131kla yapabiliyoruz. Ancak bu kolayl\u0131\u011f\u0131n yan\u0131nda; kullan\u0131c\u0131 ekleme, listeleme, oturum a\u00e7ma, \u015fifre yenileme, iki a\u015famal\u0131 do\u011frulama vs. gibi i\u015flemlerin ger\u00e7ekle\u015ftirilebilmesi i\u00e7in de kullan\u0131c\u0131 aray\u00fcz\u00fcn\u00fcn tasarlanmas\u0131 ve bu tasar\u0131mlar\u0131n kodlanmas\u0131 gerekmektedir. Her ne kadar bu tasar\u0131mlar\u0131n h\u0131zl\u0131 bir \u015fekilde halledilebilmesi i\u00e7in Microsoft taraf\u0131ndan belli ba\u015fl\u0131 UI k\u00fct\u00fcphaneleri olu\u015fturulup, hizmetimize sunulmu\u015f olsa da(Microsoft.AspNetCore.Identity.UI<\/a><\/span>) bunlar\u0131n \u00f6zelle\u015ftirilebilmesi i\u00e7in de ayr\u0131 bir maliyet durumu s\u00f6z konusu olabilmektedir. T\u00fcm bunlar\u0131n d\u0131\u015f\u0131nda uygulaman\u0131n frontend k\u0131sm\u0131 bir SPA teknolojisine sahipse i\u015fte bu taktirde bu k\u00fct\u00fcphanelerde bir anlam ifade etmemekte ve el mahkum t\u00fcm \u00e7al\u0131\u015fmalar\u0131 manuel bir \u015fekilde ger\u00e7ekle\u015ftirmek mecburiyetindeyiz. Hal b\u00f6yleyken identity API endpoint sayesinde, API’ler i\u00e7in de identity mekanizmas\u0131n\u0131n nimetlerini olduk\u00e7a h\u0131zl\u0131 ve basit bir \u015fekilde kullan\u0131labilir hale getirebilmekteyiz.<\/p>\n Hele hele, SPA’ler de token authentication’\u0131n kullan\u0131ld\u0131\u011f\u0131 senaryolarda s\u0131kl\u0131kla ihtiya\u00e7 duyulan access token de\u011ferini alabilmek bir endpoint’e istek g\u00f6ndermek gibi olduk\u00e7a basit bir hale getirilmi\u015f vaziyettedir. Evet, identity API endpoint \u00f6zelli\u011fini kulland\u0131\u011f\u0131m\u0131z taktirde username ve password bilgileri e\u015fli\u011finde a\u015fa\u011f\u0131daki gibi bir iste\u011fin yap\u0131lmas\u0131 g\u00f6rseldeki gibi bir JSON yan\u0131t\u0131n\u0131n h\u0131zl\u0131ca al\u0131nmas\u0131n\u0131 sa\u011flayacakt\u0131r.<\/p>\n \n\r\n$url = "https:\/\/localhost:7196\/myapp\/login"\r\n$headers = @{\r\n "Content-Type" = "application\/json"\r\n}\r\n\r\n$body = @{\r\n email = "gyildizmail@gmail.com"\r\n password = "1q2w3e4r'S"\r\n} | ConvertTo-Json\r\n\r\n$response = Invoke-WebRequest -Uri $url -Method Post -Headers $headers -Body $body\r\n\r\n# \u0130stek sonucunu g\u00f6r\u00fcnt\u00fcle\r\n$response.content\r\n<\/pre>\n<\/div>\n<\/a><\/p>\n Identity API’lar\u0131n Kullan\u0131m\u0131<\/h3>\nIdentity API Endpoint mekanizmas\u0131n\u0131 kullanabilmek i\u00e7in \u00f6ncelikle IdentityDbContext<\/code> s\u0131n\u0131f\u0131ndan t\u00fcreyen DbContext<\/code> s\u0131n\u0131f\u0131n\u0131n a\u015fa\u011f\u0131daki gibi tasarlanmas\u0131 gerekmektedir. <\/p>\n\n\r\n public class AppDbContext : IdentityDbContext<AppUser>\r\n {\r\n public AppDbContext(DbContextOptions options) : base(options)\r\n {\r\n }\r\n }\r\n<\/pre>\n<\/div>\n\n\r\n public class AppUser : IdentityUser\r\n {\r\n }\r\n<\/pre>\n<\/div>\nArd\u0131ndan bu context s\u0131n\u0131f\u0131n\u0131n uygulamaya a\u015fa\u011f\u0131daki gibi yap\u0131land\u0131r\u0131lmas\u0131 gerekmektedir.<\/p>\n\n\r\nvar builder = WebApplication.CreateBuilder(args);\r\n\r\n.\r\n.\r\n.\r\n\r\nbuilder.Services.AddDbContext<AppDbContext>(options => options.UseSqlServer("..."));\r\n\r\nvar app = builder.Build();\r\n<\/pre>\n<\/div>\nVe son olarak da a\u015fa\u011f\u0131daki talimatlar e\u015fli\u011finde migration olu\u015fturulup, hedef veritaban\u0131na migrate edilmelidir.<\/p>\n\n\r\ndotnet ef migrations add mig_1\r\ndotnet ef database update\r\n<\/pre>\n<\/div>\nEvet, \u015fimdi identity’i kullanabilmek i\u00e7in gerekli altyap\u0131 haz\u0131r diyebiliriz.<\/p>\n Bu a\u015famadan sonra AddIdentityApiEndpoints<\/code> metodu e\u015fli\u011finde identity servisleri uygulamaya ekleyebiliriz. Bunun i\u00e7in a\u015fa\u011f\u0131daki gibi yap\u0131land\u0131rma bulunal\u0131m;<\/p>\n \n\r\nbuilder.Services.AddIdentityApiEndpoints<AppUser>()\r\n .AddEntityFrameworkStores<AppDbContext>();\r\n<\/pre>\n<\/div>\nBu yap\u0131land\u0131rma neticesinde; bearer ve cookie authentication yap\u0131land\u0131r\u0131lmakta, temel kullan\u0131c\u0131 i\u015flemlerinden sorumlu olan UserManager<\/code> ile birlikte SignInManager<\/code> ve IEmailSender<\/code> gibi servisler IoC container’a eklenmektedir.<\/p>\n Ve \u015fimdide de t\u00fcm identity API’leri uygulamaya ekleyebilmek i\u00e7in MapIdentityApi<\/code> middleware’ini a\u015fa\u011f\u0131daki gibi \u00e7a\u011f\u0131ral\u0131m;<\/p>\n \n\r\nvar app = builder.Build();\r\n.\r\n.\r\n.\r\napp.MapIdentityApi<AppUser>();\r\n\r\napp.Run();\r\n<\/pre>\n<\/div>\nUygulamay\u0131 bu vaziyette derleyip aya\u011fa kald\u0131r\u0131rsak e\u011fer \u00f6zellikle swagger \u00fczerinde a\u015fa\u011f\u0131daki g\u00f6rselde oldu\u011fu gibi identity API endpoints \u00f6zelli\u011finin getirisi olan t\u00fcm endpoint’leri g\u00f6rmekteyiz.<\/a>Dikkat ederseniz identity API endpoints \u00f6zelli\u011fi ile kullan\u0131c\u0131 kayd\u0131(register) ve giri\u015fi(login) gibi temel d\u00fczey kullan\u0131c\u0131 i\u015flemlerinin d\u0131\u015f\u0131nda; refresh token, \u015fifremi unuttum(forgotPassword) ve hatta \u00e7ift fakt\u00f6rl\u00fc do\u011frulama(2FA) gibi t\u00fcm davran\u0131\u015flara kar\u015f\u0131l\u0131k gelen API’ler de hali haz\u0131rda eklenmi\u015f vaziyettedir. E\u011fer ki bu API’lerin kapsam\u0131n\u0131 farkl\u0131 bir path ile ba\u015flatmak isterseniz a\u015fa\u011f\u0131daki gibi MapGroup<\/code> metoduyla \u00e7al\u0131\u015fma yapman\u0131z gerekmektedir;<\/p>\n \n\r\napp.MapGroup("\/myapp").MapIdentityApi<AppUser>();\r\n<\/pre>\n<\/div>\n<\/a> \nUnutmamak laz\u0131md\u0131r ki; identity API endpoints de, IdentityServer<\/a> veya OpenIddict<\/a> k\u00fct\u00fcphanelerinin yerini almak ama\u00e7lanmam\u0131\u015ft\u0131r! Bilakis sade ve sadece kullan\u0131ld\u0131\u011f\u0131 uygulaman\u0131n kullan\u0131c\u0131 y\u00f6netimi ama\u00e7lanm\u0131\u015ft\u0131r. Ayr\u0131ca machine-to-machine ileti\u015fimden ziyade etkile\u015fime girebilecek olan ger\u00e7ek kullan\u0131c\u0131lar taraf\u0131ndan kullan\u0131lmak \u00fczere tasarlanm\u0131\u015ft\u0131r. Yani anlayaca\u011f\u0131n\u0131z basit bir backend taraf\u0131ndan beslenen SPA senaryolar\u0131ndaki kullan\u0131c\u0131 ve rol i\u015flemleri i\u00e7in identity API endpoint kolay bir se\u00e7imdir diyebiliriz.<\/p>\n Kullan\u0131c\u0131 User & Password Kriterlerini \u00d6zelle\u015ftirme<\/h3>\nIdentity API Endpoints \u00f6zelli\u011fi ile gelen hali haz\u0131rdaki user ve password kriterlerine AddIdentityApiEndpoints<\/code> metodu \u00fczerinden a\u015fa\u011f\u0131daki gibi m\u00fcdahalede bulunulabilmektedir.<\/p>\n \n\r\nbuilder.Services.AddIdentityApiEndpoints<AppUser>(options =>\r\n{\r\n options.User... \/\/\ud83d\udc48User'la ilgili \u00f6zelle\u015ftirme\r\n options.Password... \/\/\ud83d\udc48Password'le ilgili \u00f6zelle\u015ftirme\r\n})\r\n<\/pre>\n<\/div>\nNihai olarak; \nIdentity API Endpoints \u00f6zelli\u011fi sayesinde uygulamalar\u0131m\u0131zda identity mekanizmas\u0131n\u0131 olduk\u00e7a pratik ve etkili bir \u015fekilde kullanabildi\u011fimizi ve bir\u00e7ok backend i\u015fleminden de \u00e7al\u0131\u015fmalar\u0131m\u0131z\u0131 ar\u0131nd\u0131rabildi\u011fimizi tecr\u00fcbe etmi\u015f bulunuyor ve kod maliyeti ile birlikte zamansal a\u00e7\u0131dan da inan\u0131lmaz bir avantaj\u0131n s\u00f6z konusu oldu\u011funu g\u00f6zlemlemi\u015f oluyoruz. \u0130htiya\u00e7 noktalar\u0131nda kullanmay\u0131 heyecanla bekliyor olaca\u011f\u0131m \ud83d\ude42<\/p>\n \u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle… \nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere… \n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\n","protected":false},"excerpt":{"rendered":" Merhaba, Bu i\u00e7eri\u011fimizde kanaatim odur ki Asp.NET Core a\u00e7\u0131s\u0131ndan .NET 8 ile gelen en g\u00fczel \u00f6zelliklerden birini, Identity API Endpoints \u00f6zelli\u011fini inceleyece\u011fiz. Bu \u00f6zellik sayesinde uygulamalar\u0131m\u0131zdaki temel kullan\u0131c\u0131 i\u015flemlerini ger\u00e7ekle\u015ftirdi\u011fimiz Identity mekanizmas\u0131n\u0131n art\u0131k daha...<\/p>\n","protected":false},"author":1,"featured_media":26539,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4912,3102],"tags":[4915,4985,4984],"class_list":["post-26775","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-net-8","category-asp-net-core","tag-net-8","tag-net-8-identity-api-endpoints","tag-identity-api-endpoints"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26775","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/comments?post=26775"}],"version-history":[{"count":9,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26775\/revisions"}],"predecessor-version":[{"id":26787,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/26775\/revisions\/26787"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/26539"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=26775"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=26775"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=26775"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}