<\/div>\n

Merhaba,<\/p>\n

IdentityServer4 Yaz\u0131 Serisi<\/a>nin bu sonuncu makalesinde IdentityServer4 ile yapt\u0131\u011f\u0131m\u0131z ve in-memory’de tuttu\u011fumuz t\u00fcm client, scope, user vs. gibi konfig\u00fcrasyonlar\u0131 Entity Framework ile fiziksel veritaban\u0131na ta\u015f\u0131may\u0131 inceliyor olaca\u011f\u0131z.<\/p>\n

Neden konfig\u00fcrasyon de\u011ferlerini fiziksel veritaban\u0131nda tutmal\u0131y\u0131z?<\/strong>
\nIn-memory’de tutulan de\u011ferler, olas\u0131 restart durumlar\u0131nda s\u0131f\u0131rlan\u0131rlar. Dolay\u0131s\u0131yla run time’da ger\u00e7ekle\u015ftirilen t\u00fcm konfig\u00fcrasyonlar bu \u015fekilde kal\u0131c\u0131l\u0131k \u00f6zelli\u011fini yitireceklerinden dolay\u0131 fiziksel veritabanlar\u0131na kaydedilerek garanti alt\u0131na al\u0131nmal\u0131d\u0131rlar.<\/p>\n

Ayr\u0131ca depolama i\u015flemi in-memory’de yap\u0131ld\u0131\u011f\u0131 s\u00fcrece sisteme yeni bir client eklendi\u011fi zaman sistemin yeniden ba\u015flat\u0131lmas\u0131 gerekir. B\u00f6yle bir durumda client tan\u0131mlamalar\u0131n\u0131n fiziksel veritaban\u0131ndan beslenmesi uygulama a\u00e7\u0131s\u0131ndan da daha tercih edilir olacakt\u0131r.<\/p>\n

Haz\u0131r Context’ler<\/h4>\n
IdentityServer4 veritaban\u0131 i\u015flemlerini ger\u00e7ekle\u015ftirebilmek i\u00e7in ConfigurationDbContext<\/em> ve PersistedGrantDbContext<\/em> olmak \u00fczere iki farkl\u0131 context nesnesi sunmaktad\u0131r. Bu context’lerin ne oldu\u011funu s\u0131ras\u0131yla a\u00e7\u0131klarsak e\u011fer;<\/p>\n
\n
ConfigurationDbContext<\/strong>
\nBu context ile; client, scope, user vs. konfig\u00fcrasyonlar\u0131n hepsini veritaban\u0131nda tutabiliriz.\n<\/li>\n
PersistedGrantDbContext<\/strong>
\nBu context ile ise ConfigurationDbContext’in i\u015flevselli\u011fiyle birlikte token ve authorize code vs. gibi de\u011ferleri veritaban\u0131nda depolayabilmekteyiz.\n<\/li>\n<\/ul>\n
PersistedGrantDbContext sayesinde uygulama restart edildi\u011finde \u00fcretilen refresh token de\u011feri kaybolmayacak yahut her iki context sayesinde de restart edilmeden sisteme yeni bir client, user vs. ekleyebilece\u011fiz.<\/p>\n
Y\u00fcklenecek K\u00fct\u00fcphaneler<\/h4>\n
IdentityServer4’te Entity Framework ile i\u015flem yapabilmek i\u00e7in Auth Server uygulamas\u0131na IdentityServer4.EntityFramework<\/a> framework’\u00fcn\u00fcn y\u00fcklenmesi gerekmektedir. Ayriyetten SQL Server’a ba\u011flant\u0131 sa\u011flayabilmek i\u00e7inde Microsoft.EntityFrameworkCore.SqlServer<\/a> k\u00fct\u00fcphanesinin y\u00fcklenmesi gerekmektedir.
\n $\"IdentityServer4$ <\/a><\/p>\n
Konfig\u00fcrasyonlar<\/h4>\n
Startup.cs Konfig\u00fcrasyonu<\/strong>
\nYukar\u0131da tan\u0131t\u0131lan context’ler y\u00fcklemi\u015f oldu\u011fumuz bu IdentityServer4.EntityFramework k\u00fct\u00fcphanesi i\u00e7erisinde bulunmaktad\u0131r. Dolay\u0131s\u0131yla bu paket i\u00e7erisindeki context’lere eri\u015febilmek ve migration’lar\u0131 devreye sokabilmek i\u00e7in ‘Startup.cs’ dosyas\u0131nda a\u015fa\u011f\u0131daki gibi ilgili assembly ad\u0131 \u00fczerinden konfig\u00fcrasyon yapmam\u0131z gerekmektedir.<\/p>\n
\r\n public class Startup\r\n {\r\n public void ConfigureServices(IServiceCollection services)\r\n {\r\n\r\n services.AddIdentityServer()\r\n .AddConfigurationStore(options =>\r\n {\r\n options.ConfigureDbContext = builder =>\r\n builder.UseSqlServer("Server=.;Database=AuthServerDB;Trusted_Connection=True;",\r\n sqlOptions => sqlOptions.MigrationsAssembly(typeof(Startup).GetTypeInfo().Assembly.GetName().Name));\r\n })\r\n .AddOperationalStore(options =>\r\n {\r\n options.ConfigureDbContext = builder =>\r\n builder.UseSqlServer("Server=.;Database=AuthServerDB;Trusted_Connection=True;",\r\n sqlOptions => sqlOptions.MigrationsAssembly(typeof(Startup).GetTypeInfo().Assembly.GetName().Name));\r\n })\r\n .AddDeveloperSigningCredential();\r\n .\r\n .\r\n .\r\n }\r\n .\r\n .\r\n .\r\n }\r\n<\/pre>\n
Yukar\u0131daki kod blo\u011funu incelerseniz e\u011fer; 7.<\/em><\/strong> sat\u0131rdaki ‘AddConfigurationStore’ fonksiyonu ile ‘ConfigurationDbContext’in konfig\u00fcrasyonu, 13.<\/em><\/strong> sat\u0131rdaki ‘AddOperationalStore’ fonksiyonu ile ise ‘PersistedGrantDbContext’ konfig\u00fcrasyonu yap\u0131lmaktad\u0131r.<\/p>\n
Seed Data Konfig\u00fcrasyonu<\/strong>
\n‘Config.cs’ dosyas\u0131 i\u00e7erisinde mevcudiyette olu\u015fturmu\u015f oldu\u011fumuz konfig\u00fcrasyonlar\u0131 veritaban\u0131na ge\u00e7irebilmek yahut farkl\u0131 client, scope vs. gibi varsay\u0131lan de\u011ferlerle veritaban\u0131n\u0131 aya\u011fa kald\u0131rabilmek i\u00e7in a\u015fa\u011f\u0131daki gibi Seed Data’y\u0131 temsil eden bir s\u0131n\u0131f olu\u015fturabiliriz.<\/p>\n
\r\n public static class SeedData\r\n {\r\n public static void Seed(ConfigurationDbContext context)\r\n {\r\n if (!context.Clients.Any())\r\n foreach (var client in Config.GetClients())\r\n context.Clients.Add(client.ToEntity());\r\n\r\n if (!context.ApiResources.Any())\r\n foreach (var apiResource in Config.GetApiResources())\r\n context.ApiResources.Add(apiResource.ToEntity());\r\n\r\n if (!context.ApiScopes.Any())\r\n foreach (var scope in Config.GetApiScopes())\r\n context.ApiScopes.Add(scope.ToEntity());\r\n\r\n if (!context.IdentityResources.Any())\r\n foreach (var identityResource in Config.GetIdentityResources())\r\n context.IdentityResources.Add(identityResource.ToEntity());\r\n\r\n context.SaveChanges();\r\n }\r\n }\r\n<\/pre>\n
Ard\u0131ndan bu s\u0131n\u0131f\u0131 a\u015fa\u011f\u0131daki gibi ‘Program.cs’ dosyas\u0131nda dependency injection ile talep edilen context nesnesi ile kullanabiliriz.<\/p>\n
\r\n public class Program\r\n {\r\n public static void Main(string[] args)\r\n {\r\n var host = CreateHostBuilder(args).Build();\r\n using var serviceScope = host.Services.CreateScope();\r\n var services = serviceScope.ServiceProvider;\r\n var context = services.GetRequiredService<ConfigurationDbContext>();\r\n SeedData.Seed(context);\r\n host.Run();\r\n }\r\n\r\n public static IHostBuilder CreateHostBuilder(string[] args) =>\r\n Host.CreateDefaultBuilder(args)\r\n .ConfigureWebHostDefaults(webBuilder =>\r\n {\r\n webBuilder.UseStartup<Startup>();\r\n });\r\n }\r\n<\/pre>\n
Yukar\u0131daki kod blo\u011funu incelerseniz e\u011fer; 5<\/em><\/strong> ile 10.<\/em><\/strong> sat\u0131r aras\u0131nda IoC container’\u0131nda bulunan context nesnesi elde edilmekte ve ilgili seed data bu context \u00fczerinden y\u00fcklenmektedir.<\/p>\n
Migration Basma ve Veritaban\u0131n\u0131 Olu\u015fturma<\/strong>
\n $\"\"$ <\/a>
\n $\"IdentityServer4$ <\/a><\/p>\n
Evet… B\u00f6ylece bundan sonraki t\u00fcm s\u00fcre\u00e7 veritaban\u0131 ile entegre bir \u015fekilde \u00e7al\u0131\u015facakt\u0131r.<\/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, IdentityServer4 Yaz\u0131 Serisinin bu sonuncu makalesinde IdentityServer4 ile yapt\u0131\u011f\u0131m\u0131z ve in-memory’de tuttu\u011fumuz t\u00fcm client, scope, user vs. gibi konfig\u00fcrasyonlar\u0131 Entity Framework ile fiziksel veritaban\u0131na ta\u015f\u0131may\u0131 inceliyor olaca\u011f\u0131z. Neden konfig\u00fcrasyon de\u011ferlerini fiziksel veritaban\u0131nda tutmal\u0131y\u0131z?...<\/p>\n","protected":false},"author":1,"featured_media":18168,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3826],"tags":[4116,4114,4115,4112,3827,4113,4118,4117],"class_list":["post-20725","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-identityserver4","tag-configurationdbcontext","tag-entity-framework-id4","tag-entity-framework-identityserver4","tag-id4","tag-identityserver4","tag-identityserver4-entity-framework","tag-identityserver4-entityframework","tag-persistedgrantdbcontext"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/20725","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=20725"}],"version-history":[{"count":19,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/20725\/revisions"}],"predecessor-version":[{"id":20748,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/20725\/revisions\/20748"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/18168"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=20725"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=20725"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=20725"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}