{"id":43890,"date":"2026-08-06T21:11:42","date_gmt":"2026-08-06T18:11:42","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/"},"modified":"2026-08-06T21:11:42","modified_gmt":"2026-08-06T18:11:42","slug":"zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/","title":{"rendered":"ZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu"},"content":{"rendered":"

ZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu<\/h2>\n

Modern uygulamalar i\u00e7in g\u00fcvenli, esnek ve \u00f6l\u00e7eklenebilir kimlik ve eri\u015fim y\u00f6netimi (IAM) \u00e7\u00f6z\u00fcmleri arayan geli\u015ftiriciler ve kurumlar i\u00e7in ZITADEL, g\u00fc\u00e7l\u00fc bir a\u00e7\u0131k kaynak alternatifi sunar. Bu makale, ZITADEL’i s\u0131f\u0131rdan da\u011f\u0131tma s\u00fcre\u00e7lerini, temel yap\u0131land\u0131rmalar\u0131 ve sundu\u011fu avantajlar\u0131 detayland\u0131rarak, dijital kimliklerinizi g\u00fcvenle y\u00f6netmenize yard\u0131mc\u0131 olmay\u0131 ama\u00e7lamaktad\u0131r.<\/p>\n

Neden ZITADEL’i Tercih Etmelisiniz? Kimlik Y\u00f6netiminde \u00c7\u0131\u011f\u0131r A\u00e7an \u00c7\u00f6z\u00fcm<\/h2>\n

G\u00fcn\u00fcm\u00fcz dijital d\u00fcnyas\u0131nda, kullan\u0131c\u0131 kimliklerinin ve eri\u015fimlerinin g\u00fcvenli bir \u015fekilde y\u00f6netilmesi, her t\u00fcrl\u00fc uygulama ve hizmet i\u00e7in kritik bir \u00f6neme sahiptir. Geleneksel kimlik ve eri\u015fim y\u00f6netimi (IAM) \u00e7\u00f6z\u00fcmleri genellikle karma\u015f\u0131k kurulum s\u00fcre\u00e7leri, y\u00fcksek maliyetler ve \u00f6l\u00e7eklenebilirlik sorunlar\u0131 ile bo\u011fu\u015fur. \u0130\u015fte bu noktada ZITADEL, bulut yerlisi (cloud-native) mimarisi ve a\u00e7\u0131k kaynak felsefesiyle modern bir alternatif olarak \u00f6ne \u00e7\u0131k\u0131yor. Peki, ZITADEL’i rakiplerinden ay\u0131ran ve onu tercih edilebilir k\u0131lan temel \u00f6zellikler nelerdir?<\/p>\n

ZITADEL, OpenID Connect (OIDC) ve OAuth 2.0 gibi end\u00fcstri standartlar\u0131n\u0131 temel alan, mikroservis tabanl\u0131, \u00e7ok kirac\u0131l\u0131 (multi-tenancy) bir platformdur. Bu sayede, tek bir ZITADEL kurulumu \u00fczerinden birden fazla kurulu\u015fun (organization) veya projenin kimlik y\u00f6netimini izole bir \u015fekilde ger\u00e7ekle\u015ftirebilirsiniz. Bu \u00f6zellik, \u00f6zellikle SaaS (Hizmet Olarak Yaz\u0131l\u0131m) sa\u011flay\u0131c\u0131lar\u0131 veya farkl\u0131 departmanlara sahip b\u00fcy\u00fck \u015firketler i\u00e7in b\u00fcy\u00fck bir avantaj sunar. Her m\u00fc\u015fteriye veya departmana kendi \u00f6zel kimlik alan\u0131n\u0131 (identity realm) tahsis edebilir, b\u00f6ylece veri ayr\u0131\u015ft\u0131rmas\u0131n\u0131 ve g\u00fcvenlik politikalar\u0131n\u0131 kolayca uygulayabilirsiniz.<\/p>\n

ZITADEL’in sundu\u011fu temel \u00f6zellikler aras\u0131nda Tek Oturum A\u00e7ma (Single Sign-On – SSO), \u00c7ok Fakt\u00f6rl\u00fc Kimlik Do\u011frulama (Multi-Factor Authentication – MFA), Rol Tabanl\u0131 Eri\u015fim Kontrol\u00fc (Role-Based Access Control – RBAC) ve API g\u00fcvenli\u011fi yer al\u0131r. SSO, kullan\u0131c\u0131lar\u0131n tek bir kimlik do\u011frulama ile birden fazla uygulamaya eri\u015fmesini sa\u011flayarak kullan\u0131c\u0131 deneyimini iyile\u015ftirir ve parola yorgunlu\u011funu azalt\u0131r. MFA, kimlik do\u011frulama s\u00fcrecine ek bir g\u00fcvenlik katman\u0131 ekleyerek hesap g\u00fcvenli\u011fini \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131r\u0131r. RBAC ise kullan\u0131c\u0131lar\u0131n yetkilerini roller \u00fczerinden tan\u0131mlayarak eri\u015fim politikalar\u0131n\u0131n y\u00f6netimini basitle\u015ftirir. Ayr\u0131ca, ZITADEL, API’lerinizin g\u00fcvenli\u011fini sa\u011flamak i\u00e7in OAuth 2.0 tabanl\u0131 yetkilendirme ak\u0131\u015flar\u0131n\u0131 destekleyerek modern mikroservis mimarilerinde kritik bir rol oynar.<\/p>\n

Bir e-ticaret platformu i\u015fletti\u011finizi d\u00fc\u015f\u00fcn\u00fcn. M\u00fc\u015fterilerinizin h\u0131zl\u0131 ve g\u00fcvenli bir \u015fekilde oturum a\u00e7mas\u0131n\u0131, sipari\u015f vermesini ve hesap bilgilerini y\u00f6netmesini istersiniz. ZITADEL ile m\u00fc\u015fterilerinize sorunsuz bir SSO deneyimi sunabilir, hassas i\u015flemler i\u00e7in MFA gereksinimleri tan\u0131mlayabilir ve farkl\u0131 m\u00fc\u015fteri segmentlerine (\u00f6rne\u011fin, VIP m\u00fc\u015fteriler) \u00f6zel roller atayarak ki\u015fiselle\u015ftirilmi\u015f hizmetler sunabilirsiniz. Ayn\u0131 zamanda, platformunuzun arka u\u00e7 API’lerinin yaln\u0131zca yetkili uygulamalar veya servisler taraf\u0131ndan eri\u015filebilir olmas\u0131n\u0131 sa\u011flayarak veri g\u00fcvenli\u011finizi en \u00fcst d\u00fczeye \u00e7\u0131kar\u0131rs\u0131n\u0131z. ZITADEL’in a\u00e7\u0131k kaynak yap\u0131s\u0131, esneklik, topluluk deste\u011fi ve kendi veri egemenli\u011finizi koruma yetene\u011fi gibi ek avantajlar sunarak, kimlik y\u00f6netimi ihtiya\u00e7lar\u0131n\u0131z i\u00e7in g\u00fc\u00e7l\u00fc ve gelece\u011fe d\u00f6n\u00fck bir \u00e7\u00f6z\u00fcm haline gelir.<\/p>\n

ZITADEL Da\u011f\u0131t\u0131m\u0131na Haz\u0131rl\u0131k: Gereksinimler ve \u00d6n Ko\u015fullar Nelerdir?<\/h2>\n

ZITADEL’i ba\u015far\u0131l\u0131 bir \u015fekilde da\u011f\u0131tmak i\u00e7in do\u011fru bir haz\u0131rl\u0131k s\u00fcreci \u015fartt\u0131r. Platformun esnek yap\u0131s\u0131, bulut tabanl\u0131 (SaaS) bir hizmet olarak kullan\u0131labilece\u011fi gibi, kendi altyap\u0131n\u0131zda (self-hosted) da bar\u0131nd\u0131r\u0131labilece\u011fi anlam\u0131na gelir. Bu makalede, \u00f6zellikle kendi kendine bar\u0131nd\u0131rma (self-hosted) senaryosuna odaklanaca\u011f\u0131z, \u00e7\u00fcnk\u00fc bu y\u00f6ntem size veri egemenli\u011fi ve tam kontrol sa\u011flar. Kendi altyap\u0131n\u0131zda ZITADEL da\u011f\u0131t\u0131m\u0131 i\u00e7in belirli donan\u0131m, yaz\u0131l\u0131m ve a\u011f gereksinimlerini kar\u015f\u0131laman\u0131z gerekmektedir.<\/p>\n

\u00d6ncelikle, ZITADEL bulut yerlisi (cloud-native) bir uygulama oldu\u011fu i\u00e7in Kubernetes ortam\u0131nda da\u011f\u0131t\u0131m en yayg\u0131n ve \u00f6nerilen y\u00f6ntemdir. Bu, uygulaman\u0131n \u00f6l\u00e7eklenebilirli\u011fini, y\u00fcksek eri\u015filebilirli\u011fini ve y\u00f6netim kolayl\u0131\u011f\u0131n\u0131 garanti eder. Dolay\u0131s\u0131yla, bir Kubernetes k\u00fcmesi (cluster) haz\u0131r olmal\u0131d\u0131r. E\u011fer Kubernetes’e a\u015fina de\u011filseniz veya daha basit bir geli\u015ftirme ortam\u0131 ar\u0131yorsan\u0131z, Docker ve Docker Compose kullanarak yerel bir kurulum da m\u00fcmk\u00fcnd\u00fcr, ancak bu \u00fcretim ortamlar\u0131 i\u00e7in genellikle \u00f6nerilmez. Kubernetes k\u00fcmenizin yeterli i\u015flemci (CPU), bellek (RAM) ve depolama (storage) kaynaklar\u0131na sahip oldu\u011fundan emin olun. ZITADEL’in performansl\u0131 \u00e7al\u0131\u015fabilmesi i\u00e7in h\u0131zl\u0131 bir depolama \u00e7\u00f6z\u00fcm\u00fc, \u00f6zellikle veritaban\u0131 i\u00e7in kritik \u00f6neme sahiptir.<\/p>\n

ZITADEL, verilerini depolamak i\u00e7in PostgreSQL veritaban\u0131n\u0131 kullan\u0131r. Bu nedenle, bir PostgreSQL sunucusu veya Kubernetes i\u00e7inde da\u011f\u0131t\u0131lm\u0131\u015f bir PostgreSQL operat\u00f6r\u00fc (\u00f6rne\u011fin, Crunchy Data PostgreSQL Operator) haz\u0131r olmal\u0131d\u0131r. Veritaban\u0131n\u0131n y\u00fcksek eri\u015filebilirli\u011fi ve yedekleme stratejileri, veri kayb\u0131n\u0131 \u00f6nlemek ve hizmet kesintilerini minimize etmek i\u00e7in \u00f6nceden planlanmal\u0131d\u0131r. Ayr\u0131ca, ZITADEL’in d\u0131\u015far\u0131dan eri\u015filebilir olmas\u0131 i\u00e7in bir alan ad\u0131 (domain name) ve bu alan ad\u0131na i\u015faret eden DNS kay\u0131tlar\u0131 (A kayd\u0131 veya CNAME) gereklidir. G\u00fcvenli ileti\u015fim i\u00e7in bu alan ad\u0131na ait ge\u00e7erli bir TLS\/SSL sertifikas\u0131 (\u00f6rne\u011fin, Let’s Encrypt ile al\u0131nan) da zorunludur. Sertifikalar\u0131 y\u00f6netmek i\u00e7in Kubernetes i\u00e7inde Cert-Manager gibi bir ara\u00e7 kullanmak i\u015finizi kolayla\u015ft\u0131racakt\u0131r.<\/p>\n

A\u011f yap\u0131land\u0131rmas\u0131 da \u00f6nemli bir ad\u0131md\u0131r. ZITADEL’e gelen trafik i\u00e7in bir y\u00fck dengeleyici (load balancer) veya giri\u015f denetleyicisi (ingress controller) (\u00f6rne\u011fin, NGINX Ingress Controller) kurulmu\u015f ve yap\u0131land\u0131r\u0131lm\u0131\u015f olmal\u0131d\u0131r. Bu, trafi\u011fi do\u011fru ZITADEL servislerine y\u00f6nlendirir ve TLS sonland\u0131rmas\u0131n\u0131 y\u00f6netir. G\u00fcvenlik a\u00e7\u0131s\u0131ndan, a\u011f segmentasyonu, g\u00fcvenlik duvar\u0131 (firewall) kurallar\u0131 ve en az ayr\u0131cal\u0131k (least privilege) prensibiyle eri\u015fim y\u00f6netimi gibi \u00f6nlemler al\u0131nmal\u0131d\u0131r. T\u00fcm bu \u00f6n ko\u015fullar\u0131 yerine getirmek, ZITADEL da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n sa\u011flam ve g\u00fcvenli bir temele oturmas\u0131n\u0131 sa\u011flayacakt\u0131r. \u00d6rne\u011fin, orta \u00f6l\u00e7ekli bir yaz\u0131l\u0131m \u015firketinin \u015firket i\u00e7i uygulamalar\u0131 i\u00e7in ZITADEL kurma karar\u0131 ald\u0131\u011f\u0131n\u0131 varsayal\u0131m. Bu \u015firket, mevcut Kubernetes k\u00fcmesini kullanarak ZITADEL’i da\u011f\u0131tabilir, dahili bir PostgreSQL veritaban\u0131 servisi kurabilir ve \u015firket i\u00e7i DNS kay\u0131tlar\u0131n\u0131 g\u00fcncelleyerek ZITADEL’in dahili a\u011fdan eri\u015filebilirli\u011fini sa\u011flayabilir. G\u00fcvenlik ekibi, TLS sertifikalar\u0131n\u0131 ve a\u011f eri\u015fim kurallar\u0131n\u0131 denetleyerek da\u011f\u0131t\u0131m\u0131n kurumsal g\u00fcvenlik standartlar\u0131na uygun oldu\u011fundan emin olmal\u0131d\u0131r.<\/p>\n

ZITADEL’i Kubernetes \u00dczerinde Ad\u0131m Ad\u0131m Da\u011f\u0131tma S\u00fcreci Nas\u0131l \u0130\u015fler?<\/h2>\n

ZITADEL’i Kubernetes \u00fczerinde da\u011f\u0131tmak, Helm Charts’\u0131n sa\u011flad\u0131\u011f\u0131 kolayl\u0131k sayesinde olduk\u00e7a basittir. Helm, Kubernetes uygulamalar\u0131n\u0131 y\u00f6netmek i\u00e7in bir paket y\u00f6neticisidir ve ZITADEL i\u00e7in \u00f6nceden haz\u0131rlanm\u0131\u015f bir Helm chart bulunmaktad\u0131r. Bu b\u00f6l\u00fcm, ZITADEL’i Kubernetes k\u00fcmenize nas\u0131l da\u011f\u0131taca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m a\u00e7\u0131klayacakt\u0131r.<\/p>\n

Veritaban\u0131 Kurulumu (PostgreSQL)<\/h3>\n

ZITADEL’in \u00e7al\u0131\u015fmas\u0131 i\u00e7in bir PostgreSQL veritaban\u0131na ihtiyac\u0131 vard\u0131r. K\u00fcmenizde zaten bir PostgreSQL \u00f6rne\u011fi varsa onu kullanabilir veya Helm kullanarak yeni bir tane da\u011f\u0131tabilirsiniz. G\u00fcvenlik ve veri kal\u0131c\u0131l\u0131\u011f\u0131 i\u00e7in harici, y\u00f6netilen bir PostgreSQL hizmeti (\u00f6rne\u011fin, AWS RDS, Azure Database for PostgreSQL) kullanmak genellikle \u00fcretim ortamlar\u0131 i\u00e7in daha iyi bir se\u00e7enektir. E\u011fer k\u00fcme i\u00e7inde da\u011f\u0131tacaksan\u0131z, Bitnami’nin PostgreSQL Helm chart’\u0131n\u0131 kullanabilirsiniz:<\/p>\n

\n
helm repo add bitnami https:\/\/charts.bitnami.com\/bitnami\nhelm install my-postgresql bitnami\/postgresql \\\n  --set auth.database=zitadel \\\n  --set auth.username=zitadel_user \\\n  --set auth.password=your_strong_password \\\n  --set primary.persistence.enabled=true \\\n  --set primary.persistence.size=50Gi<\/code><\/pre>\n<\/div>\n
Bu komut, my-postgresql<\/code> ad\u0131nda bir PostgreSQL \u00f6rne\u011fini zitadel<\/code> veritaban\u0131 ve belirtilen kullan\u0131c\u0131\/\u015fifre ile kurar. Kal\u0131c\u0131l\u0131k (persistence) etkinle\u015ftirilir ve 50GB depolama alan\u0131 ayr\u0131l\u0131r.<\/p>\n
ZITADEL Helm Chart’\u0131n\u0131 Ekleme ve Yap\u0131land\u0131rma<\/h3>\n
ZITADEL’in kendi Helm deposunu eklemeniz ve ard\u0131ndan yap\u0131land\u0131rma dosyas\u0131n\u0131 (values.yaml<\/code>) \u00f6zelle\u015ftirmeniz gerekir. values.yaml<\/code> dosyas\u0131, ZITADEL’in da\u011f\u0131t\u0131m\u0131n\u0131 ve davran\u0131\u015f\u0131n\u0131 kontrol eden t\u00fcm ayarlar\u0131 i\u00e7erir.<\/p>\n
\n
helm repo add zitadel https:\/\/charts.zitadel.com\/\nhelm repo update<\/code><\/pre>\n<\/div>\n
\u015eimdi, \u00f6rnek bir values.yaml<\/code> dosyas\u0131 olu\u015ftural\u0131m. Bu dosya, veritaban\u0131 ba\u011flant\u0131 bilgilerini, alan ad\u0131n\u0131z\u0131, TLS ayarlar\u0131n\u0131 ve ilk y\u00f6netici kullan\u0131c\u0131s\u0131n\u0131n e-posta adresini i\u00e7erecektir. Alan ad\u0131n\u0131z\u0131n (your.domain.com<\/code>) ve TLS sertifikalar\u0131n\u0131z\u0131n (Cert-Manager ile otomatik olarak veya manuel olarak) do\u011fru \u015fekilde yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131ndan emin olun.<\/p>\n
\n
# values.yaml\nzitadel:\n  masterkey: \"your-32-byte-master-key-here-for-encryption\" # 32 karakterlik rastgele bir anahtar\n  externalDomain: \"zitadel.yourdomain.com\"\n  externalPort: 443\n  externalSecure: true\n  firstInstance:\n    # \u0130lk y\u00f6netici kullan\u0131c\u0131s\u0131 i\u00e7in e-posta\n    initUser: \"admin@yourdomain.com\" \n    # \u0130lk kurulu\u015f (organization) ad\u0131\n    defaultOrg: \"MyCompany\" \n\ndatabase:\n  # E\u011fer k\u00fcme i\u00e7inde kurduysan\u0131z:\n  host: \"my-postgresql\" # PostgreSQL servisi ad\u0131\n  port: 5432\n  user: \"zitadel_user\"\n  password: \"your_strong_password\"\n  database: \"zitadel\"\n  # E\u011fer harici bir DB kullan\u0131yorsan\u0131z, ilgili host, port, user, password ve database bilgilerini girin.\n\ningress:\n  enabled: true\n  className: \"nginx\" # Kulland\u0131\u011f\u0131n\u0131z ingress controller s\u0131n\u0131f\u0131\n  annotations:\n    kubernetes.io\/ingress.class: \"nginx\"\n    cert-manager.io\/cluster-issuer: \"letsencrypt-prod\" # Cert-Manager kullan\u0131yorsan\u0131z\n  host: \"zitadel.yourdomain.com\"\n  tls:\n    - hosts:\n        - \"zitadel.yourdomain.com\"\n      secretName: \"zitadel-tls\" # Cert-Manager taraf\u0131ndan olu\u015fturulacak veya manuel olu\u015fturulan secret<\/code><\/pre>\n<\/div>\n
masterkey<\/code> alan\u0131na rastgele, g\u00fc\u00e7l\u00fc bir 32 baytl\u0131k anahtar girmeniz kritik \u00f6neme sahiptir. Bu anahtar, hassas verilerin \u015fifrelenmesi i\u00e7in kullan\u0131l\u0131r. Bir anahtar olu\u015fturmak i\u00e7in openssl rand -base64 32<\/code> gibi bir komut kullanabilirsiniz.<\/p>\n
ZITADEL’i Da\u011f\u0131tma<\/h3>\n
values.yaml<\/code> dosyan\u0131z\u0131 kaydettikten sonra, ZITADEL’i Helm ile da\u011f\u0131tabilirsiniz:<\/p>\n
\n
helm install zitadel zitadel\/zitadel -f values.yaml<\/code><\/pre>\n<\/div>\n
Da\u011f\u0131t\u0131m\u0131n tamamlanmas\u0131 birka\u00e7 dakika s\u00fcrebilir. Pod’lar\u0131n durumunu kontrol etmek i\u00e7in:<\/p>\n
\n
kubectl get pods -l app.kubernetes.io\/name=zitadel<\/code><\/pre>\n<\/div>\n
T\u00fcm pod’lar “Running” durumuna ge\u00e7ti\u011finde, ZITADEL kontrol paneline eri\u015fmeye haz\u0131r olacaks\u0131n\u0131z. Taray\u0131c\u0131n\u0131zdan https:\/\/zitadel.yourdomain.com<\/code> adresine gidin. \u0130lk eri\u015fimde, values.yaml<\/code> dosyas\u0131nda belirtti\u011finiz initUser<\/code> e-posta adresi i\u00e7in bir parola belirlemeniz istenecektir. Bu ad\u0131m, ilk y\u00f6netici hesab\u0131n\u0131z\u0131 olu\u015fturman\u0131z\u0131 sa\u011flar.<\/p>\n
Ba\u015far\u0131l\u0131 bir kurulumun ard\u0131ndan, ZITADEL’in y\u00f6netici kontrol paneline eri\u015ferek kurulu\u015funuzu, projelerinizi, uygulamalar\u0131n\u0131z\u0131 ve kullan\u0131c\u0131lar\u0131n\u0131z\u0131 y\u00f6netmeye ba\u015flayabilirsiniz. ZITADEL’in kullan\u0131c\u0131 dostu aray\u00fcz\u00fc sayesinde, kimlik ve eri\u015fim y\u00f6netimi s\u00fcre\u00e7lerinizi kolayca yap\u0131land\u0131rabilirsiniz.<\/p>\n
Docker Compose ile H\u0131zl\u0131 Ba\u015flang\u0131\u00e7: Geli\u015ftirme Ortam\u0131 \u0130\u00e7in ZITADEL Kurulumu<\/h3>\n
\u00dcretim ortamlar\u0131 i\u00e7in Kubernetes \u00f6nerilse de, geli\u015ftirme veya test ama\u00e7l\u0131 h\u0131zl\u0131 bir ba\u015flang\u0131\u00e7 i\u00e7in Docker Compose m\u00fckemmel bir se\u00e7enektir. Docker Compose, \u00e7ok kapsay\u0131c\u0131l\u0131 (multi-container) Docker uygulamalar\u0131n\u0131 tan\u0131mlama ve \u00e7al\u0131\u015ft\u0131rma arac\u0131d\u0131r. ZITADEL’i Docker Compose ile kurmak, yerel makinenizde veya k\u00fc\u00e7\u00fck bir sanal sunucuda kolayca bir ZITADEL \u00f6rne\u011fi \u00e7al\u0131\u015ft\u0131rman\u0131za olanak tan\u0131r.<\/p>\n
A\u015fa\u011f\u0131daki docker-compose.yaml<\/code> dosyas\u0131, ZITADEL ve ba\u011f\u0131ml\u0131 oldu\u011fu PostgreSQL veritaban\u0131n\u0131 tek bir komutla ba\u015flatmak i\u00e7in gerekli servisleri tan\u0131mlar. Bu kurulum, \u00fcretim ortamlar\u0131 i\u00e7in uygun de\u011fildir \u00e7\u00fcnk\u00fc y\u00fcksek eri\u015filebilirlik, \u00f6l\u00e7eklenebilirlik ve kal\u0131c\u0131 depolama (persistent storage) gibi kritik \u00f6zelliklerden yoksundur. Ancak, yerel geli\u015ftirme veya \u00f6zellik testleri i\u00e7in idealdir.<\/p>\n
\n
version: '3.8'\n\nservices:\n  zitadel:\n    image: ghcr.io\/zitadel\/zitadel:latest\n    container_name: zitadel\n    ports:\n      - \"8080:8080\"\n      - \"8081:8081\"\n    environment:\n      ZITADEL_MASTERKEY: \"your-32-byte-master-key-here-for-encryption\" # \u00d6nemli: G\u00fc\u00e7l\u00fc bir anahtar kullan\u0131n!\n      ZITADEL_DATABASE_HOST: \"postgres\"\n      ZITADEL_DATABASE_PORT: \"5432\"\n      ZITADEL_DATABASE_USER: \"zitadel_user\"\n      ZITADEL_DATABASE_PASSWORD: \"your_strong_password\"\n      ZITADEL_DATABASE_DATABASE: \"zitadel\"\n      ZITADEL_FIRSTINSTANCE_INITUSER_EMAIL: \"admin@example.com\"\n      ZITADEL_FIRSTINSTANCE_DEFAULTORG_NAME: \"DevCompany\"\n    depends_on:\n      - postgres\n    volumes:\n      - zitadel_data:\/app\/data # ZITADEL verileri i\u00e7in kal\u0131c\u0131 depolama\n    restart: always\n\n  postgres:\n    image: postgres:15-alpine\n    container_name: postgres\n    environment:\n      POSTGRES_DB: \"zitadel\"\n      POSTGRES_USER: \"zitadel_user\"\n      POSTGRES_PASSWORD: \"your_strong_password\"\n    volumes:\n      - postgres_data:\/var\/lib\/postgresql\/data # PostgreSQL verileri i\u00e7in kal\u0131c\u0131 depolama\n    restart: always\n\nvolumes:\n  zitadel_data:\n  postgres_data:<\/code><\/pre>\n<\/div>\n
Bu dosyay\u0131 bir metin d\u00fczenleyiciyle docker-compose.yaml<\/code> ad\u0131yla kaydedin. ZITADEL_MASTERKEY<\/code> ve veritaban\u0131 \u015fifrelerini g\u00fcvenli ve karma\u015f\u0131k de\u011ferlerle de\u011fi\u015ftirdi\u011finizden emin olun. \u00d6zellikle ZITADEL_MASTERKEY<\/code>, ZITADEL’in i\u00e7 verilerini \u015fifrelemek i\u00e7in kullan\u0131lan kritik bir anahtard\u0131r. Bu anahtar\u0131 g\u00fcvende tutmal\u0131 ve kaybetmemelisiniz.<\/p>\n
Dosyay\u0131 kaydettikten sonra, terminalinizi dosyan\u0131n bulundu\u011fu dizine getirin ve a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n
\n
docker compose up -d<\/code><\/pre>\n<\/div>\n
Bu komut, ZITADEL ve PostgreSQL servislerini arka planda ba\u015flatacakt\u0131r. Servislerin durumunu kontrol etmek i\u00e7in:<\/p>\n
\n
docker compose ps<\/code><\/pre>\n<\/div>\n
Her iki servisin de “running” durumunda oldu\u011funu g\u00f6rmelisiniz. ZITADEL’in y\u00f6netici aray\u00fcz\u00fcne eri\u015fmek i\u00e7in taray\u0131c\u0131n\u0131zda http:\/\/localhost:8080<\/code> adresine gidin. \u0130lk eri\u015fimde, docker-compose.yaml<\/code> dosyas\u0131nda belirtti\u011finiz admin@example.com<\/code> e-posta adresi i\u00e7in bir parola belirlemeniz istenecektir. Bu parola ile y\u00f6netici konsoluna giri\u015f yapabilirsiniz.<\/p>\n
Bu kurulum, geli\u015ftirme ve test ortamlar\u0131 i\u00e7in h\u0131zl\u0131 ve kullan\u0131\u015fl\u0131 olsa da, \u00fcretim ortamlar\u0131nda kullan\u0131lmas\u0131 tavsiye edilmez. \u00dcretim i\u00e7in Kubernetes da\u011f\u0131t\u0131m\u0131, y\u00fcksek eri\u015filebilirlik, otomatik \u00f6l\u00e7eklendirme, geli\u015fmi\u015f g\u00fcvenlik ve izleme yetenekleri sunar.<\/p>\n
ZITADEL Yap\u0131land\u0131rmas\u0131 ve \u0130lk Kullan\u0131m: Uygulamalar\u0131n\u0131z\u0131 Nas\u0131l Entegre Edersiniz?<\/h2>\n
ZITADEL’i ba\u015far\u0131yla da\u011f\u0131tt\u0131ktan sonra, s\u0131ra onu kullanmaya ve uygulamalar\u0131n\u0131z\u0131 entegre etmeye gelir. ZITADEL’in y\u00f6netici konsolu, kimlik ve eri\u015fim y\u00f6netimi s\u00fcre\u00e7lerinizi kolayca yap\u0131land\u0131rman\u0131z\u0131 sa\u011flayan sezgisel bir aray\u00fcz sunar. \u0130lk ad\u0131m, kurulu\u015funuzun ve projelerinizin yap\u0131s\u0131n\u0131 olu\u015fturmakt\u0131r.<\/p>\n
Kurulu\u015f (Organization) ve Proje (Project) Olu\u015fturma<\/h3>\n
ZITADEL, \u00e7ok kirac\u0131l\u0131 (multi-tenancy) bir platform oldu\u011fu i\u00e7in t\u00fcm kaynaklar bir “Kurulu\u015f” (Organization) alt\u0131nda gruplan\u0131r. Her kurulu\u015f, kendi kullan\u0131c\u0131lar\u0131na, uygulamalar\u0131na ve kimlik sa\u011flay\u0131c\u0131lar\u0131na sahip olabilir. Kurulu\u015flar alt\u0131nda ise “Proje” (Project) kavram\u0131 bulunur. Bir proje, belirli bir uygulama setini veya i\u015f birimini temsil eder. \u00d6rne\u011fin, bir \u015firket “Ana Kurulu\u015f” alt\u0131nda “Web Uygulamalar\u0131”, “Mobil Uygulamalar” ve “API Hizmetleri” gibi projeler olu\u015fturabilir.<\/p>\n
    \n
  1. Y\u00f6netici konsoluna giri\u015f yap\u0131n.<\/li>\n
  2. Sol men\u00fcden “Organizations” (Kurulu\u015flar) se\u00e7ene\u011fine t\u0131klay\u0131n.<\/li>\n
  3. Yeni bir kurulu\u015f olu\u015fturun veya mevcut kurulu\u015funuzu se\u00e7in.<\/li>\n
  4. Se\u00e7ti\u011finiz kurulu\u015f alt\u0131nda, “Projects” (Projeler) b\u00f6l\u00fcm\u00fcne gidin ve “New Project” (Yeni Proje) butonuna t\u0131klayarak uygulaman\u0131z i\u00e7in bir proje olu\u015fturun.<\/li>\n<\/ol>\n
    Uygulama (Application) Kayd\u0131: OIDC ve OAuth 2.0 \u0130stemcileri<\/h3>\n
    Uygulamalar\u0131n\u0131z\u0131n ZITADEL ile kimlik do\u011frulama ve yetkilendirme yapabilmesi i\u00e7in ZITADEL’de bir “Uygulama” (Application) olarak kaydedilmesi gerekir. ZITADEL, OpenID Connect (OIDC) ve OAuth 2.0 standartlar\u0131n\u0131 destekler. En yayg\u0131n uygulama t\u00fcrleri \u015funlard\u0131r:<\/p>\n
      \n
    • Web Uygulamas\u0131 (Web Application)<\/strong>: Sunucu taraf\u0131nda \u00e7al\u0131\u015fan ve bir taray\u0131c\u0131 arac\u0131l\u0131\u011f\u0131yla eri\u015filen uygulamalar (\u00f6rne\u011fin, React, Angular, Vue.js ile yaz\u0131lm\u0131\u015f tek sayfa uygulamalar\u0131 veya geleneksel sunucu taraf\u0131 uygulamalar\u0131). Genellikle “Authorization Code Flow with PKCE” kullan\u0131l\u0131r.<\/li>\n
    • Native Uygulama (Native Application)<\/strong>: Mobil veya masa\u00fcst\u00fc uygulamalar\u0131. Yine “Authorization Code Flow with PKCE” tercih edilir.<\/li>\n
    • API<\/strong>: Ba\u015fka servisler veya uygulamalar taraf\u0131ndan t\u00fcketilen API’ler i\u00e7in yetkilendirme.<\/li>\n
    • Machine-to-Machine (M2M) Uygulama<\/strong>: Kullan\u0131c\u0131 etkile\u015fimi olmayan servisler aras\u0131 ileti\u015fim i\u00e7in “Client Credentials Flow” kullan\u0131l\u0131r.<\/li>\n<\/ul>\n
      Bir web uygulamas\u0131 i\u00e7in kay\u0131t ad\u0131mlar\u0131:<\/p>\n
        \n
      1. Projenizin i\u00e7inde “Applications” (Uygulamalar) b\u00f6l\u00fcm\u00fcne gidin.<\/li>\n
      2. “New Application” (Yeni Uygulama) butonuna t\u0131klay\u0131n.<\/li>\n
      3. Uygulaman\u0131za bir ad verin (\u00f6rne\u011fin, “MyWebApp”).<\/li>\n
      4. Uygulama t\u00fcr\u00fc olarak “Web Application” veya “Native Application” se\u00e7in.<\/li>\n
      5. Kimlik do\u011frulama y\u00f6ntemi olarak “OpenID Connect” se\u00e7ene\u011fini belirleyin.<\/li>\n
      6. Y\u00f6nlendirme URI’lerini (Redirect URIs) ve \u00c7\u0131k\u0131\u015f Sonras\u0131 Y\u00f6nlendirme URI’lerini (Post Logout Redirect URIs) girin. \u00d6rne\u011fin, http:\/\/localhost:3000\/callback<\/code> ve http:\/\/localhost:3000\/logout<\/code>.<\/li>\n
      7. Uygulaman\u0131z kaydedildikten sonra, size bir “Client ID” (\u0130stemci Kimli\u011fi) ve “Client Secret” (\u0130stemci Gizli Anahtar\u0131) verilecektir (Client Secret sadece belirli ak\u0131\u015flarda gereklidir ve dikkatlice saklanmal\u0131d\u0131r). Bu bilgiler, uygulaman\u0131z\u0131n ZITADEL ile ileti\u015fim kurmas\u0131 i\u00e7in kullan\u0131lacakt\u0131r.<\/li>\n<\/ol>\n
        Uygulaman\u0131z\u0131n bu kimlik bilgileriyle ZITADEL’e nas\u0131l ba\u011flanaca\u011f\u0131n\u0131 g\u00f6steren basit bir OIDC yap\u0131land\u0131rma \u00f6rne\u011fi:<\/p>\n
        \n
        \/\/ \u00d6rnek bir Node.js\/Express uygulamas\u0131nda OIDC yap\u0131land\u0131rmas\u0131\nconst { Issuer } = require('openid-client');\n\nasync function configureOIDC() {\n  const issuer = await Issuer.discover('https:\/\/zitadel.yourdomain.com'); \/\/ ZITADEL endpoint'iniz\n  const client = new issuer.Client({\n    client_id: 'YOUR_CLIENT_ID', \/\/ ZITADEL'den ald\u0131\u011f\u0131n\u0131z Client ID\n    client_secret: 'YOUR_CLIENT_SECRET', \/\/ ZITADEL'den ald\u0131\u011f\u0131n\u0131z Client Secret (Web App i\u00e7in gerekli olabilir)\n    redirect_uris: ['http:\/\/localhost:3000\/callback'],\n    response_types: ['code'],\n  });\n\n  \/\/ Bu client objesini uygulaman\u0131zda kimlik do\u011frulama i\u00e7in kullanabilirsiniz.\n  console.log('OIDC Client yap\u0131land\u0131r\u0131ld\u0131:', client.metadata);\n}\n\nconfigureOIDC();<\/code><\/pre>\n<\/div>\n
        Kullan\u0131c\u0131 ve Rol Y\u00f6netimi<\/h3>\n
        ZITADEL, kullan\u0131c\u0131lar\u0131 ve onlar\u0131n rollerini merkezi bir yerden y\u00f6netmenizi sa\u011flar. Kullan\u0131c\u0131lar\u0131 manuel olarak olu\u015fturabilir, harici kimlik sa\u011flay\u0131c\u0131lar\u0131ndan (\u00f6rne\u011fin, Google, GitHub, SAML) senkronize edebilir veya API arac\u0131l\u0131\u011f\u0131yla entegre edebilirsiniz. Rol tabanl\u0131 eri\u015fim kontrol\u00fc (RBAC) ile kullan\u0131c\u0131lara belirli projeler veya kurulu\u015flar i\u00e7inde yetkiler atayabilirsiniz.<\/p>\n
        Vaka analizi olarak, bir SaaS sa\u011flay\u0131c\u0131s\u0131n\u0131n ZITADEL’i kullanarak m\u00fc\u015fterilerine \u00f6zel kirac\u0131lar (organizations) sundu\u011funu d\u00fc\u015f\u00fcnelim. Her yeni m\u00fc\u015fteri kaydoldu\u011funda, ZITADEL’de otomatik olarak yeni bir kurulu\u015f olu\u015fturulur ve m\u00fc\u015fteri y\u00f6neticisine bu kurulu\u015f i\u00e7inde “Kurulu\u015f Sahibi” (Organization Owner) rol\u00fc atan\u0131r. Bu sayede, her m\u00fc\u015fteri kendi kullan\u0131c\u0131lar\u0131n\u0131, uygulamalar\u0131n\u0131 ve kimlik sa\u011flay\u0131c\u0131lar\u0131n\u0131 izole bir \u015fekilde y\u00f6netebilirken, SaaS sa\u011flay\u0131c\u0131s\u0131 t\u00fcm m\u00fc\u015fteri kirac\u0131lar\u0131n\u0131 merkezi bir ZITADEL \u00f6rne\u011fi \u00fczerinden denetleyebilir. Bu, hem g\u00fcvenlik hem de y\u00f6netim kolayl\u0131\u011f\u0131 a\u00e7\u0131s\u0131ndan b\u00fcy\u00fck avantajlar sunar.<\/p>\n
        G\u00fcvenlik ve \u00d6l\u00e7eklenebilirlik: ZITADEL Da\u011f\u0131t\u0131m\u0131n\u0131z\u0131 Nas\u0131l Optimize Edersiniz?<\/h2>\n
        Bir kimlik ve eri\u015fim y\u00f6netimi platformu olarak ZITADEL’in g\u00fcvenli\u011fi ve \u00f6l\u00e7eklenebilirli\u011fi, da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n ba\u015far\u0131s\u0131 i\u00e7in hayati \u00f6neme sahiptir. Hassas kullan\u0131c\u0131 verilerini bar\u0131nd\u0131rd\u0131\u011f\u0131 ve kritik eri\u015fim kararlar\u0131 verdi\u011fi i\u00e7in, ZITADEL da\u011f\u0131t\u0131m\u0131n\u0131z\u0131 en y\u00fcksek g\u00fcvenlik standartlar\u0131na g\u00f6re optimize etmeli ve gelecekteki b\u00fcy\u00fcme ihtiya\u00e7lar\u0131n\u0131 kar\u015f\u0131layacak \u015fekilde \u00f6l\u00e7eklenebilir k\u0131lmal\u0131s\u0131n\u0131z.<\/p>\n
        Y\u00fcksek Eri\u015filebilirlik (High Availability) ve Felaket Kurtarma<\/h3>\n
        ZITADEL’in s\u00fcrekli \u00e7al\u0131\u015f\u0131r durumda olmas\u0131, uygulamalar\u0131n\u0131z\u0131n ve kullan\u0131c\u0131lar\u0131n\u0131z\u0131n kesintisiz eri\u015fimi i\u00e7in elzemdir. Kubernetes ortam\u0131nda y\u00fcksek eri\u015filebilirlik sa\u011flamak i\u00e7in ZITADEL pod’lar\u0131n\u0131 birden fazla d\u00fc\u011f\u00fcmde (node) ve tercihen farkl\u0131 kullan\u0131labilirlik b\u00f6lgelerinde (availability zones) da\u011f\u0131tmal\u0131s\u0131n\u0131z. Helm chart’\u0131 kullanarak ZITADEL replikalar\u0131n\u0131 art\u0131rabilir ve Kubernetes’in otomatik hata kurtarma \u00f6zelliklerinden yararlanabilirsiniz.<\/p>\n
        Veritaban\u0131 (PostgreSQL) i\u00e7in de y\u00fcksek eri\u015filebilirlik yap\u0131land\u0131rmas\u0131 kritik \u00f6neme sahiptir. Y\u00f6netilen bir veritaban\u0131 hizmeti (AWS RDS, Azure PostgreSQL) kullan\u0131yorsan\u0131z, sa\u011flay\u0131c\u0131n\u0131n sundu\u011fu \u00e7oklu AZ da\u011f\u0131t\u0131m\u0131 ve otomatik yedekleme \u00f6zelliklerini etkinle\u015ftirin. Kendi kendinize bar\u0131nd\u0131rd\u0131\u011f\u0131n\u0131z PostgreSQL i\u00e7in, veritaban\u0131 replikasyonu (\u00f6rne\u011fin, ak\u0131\u015f replikasyonu) ve otomatik failover mekanizmalar\u0131 kurmal\u0131s\u0131n\u0131z. Felaket kurtarma stratejisi olarak, d\u00fczenli veritaban\u0131 yedeklemeleri almal\u0131 ve bu yedeklemeleri farkl\u0131 co\u011frafi konumlarda saklamal\u0131s\u0131n\u0131z. Yedeklemelerinizi periyodik olarak geri y\u00fckleme testlerinden ge\u00e7irerek kurtarma s\u00fcrecinin i\u015flerli\u011fini do\u011frulamak da \u00f6nemlidir.<\/p>\n
        G\u00fcnl\u00fckleme (Logging) ve \u0130zleme (Monitoring)<\/h3>\n
        ZITADEL’in davran\u0131\u015f\u0131n\u0131, performans\u0131n\u0131 ve g\u00fcvenlik olaylar\u0131n\u0131 izlemek i\u00e7in kapsaml\u0131 g\u00fcnl\u00fckleme ve izleme sistemleri entegre etmelisiniz. ZITADEL, t\u00fcm \u00f6nemli olaylar\u0131 (kimlik do\u011frulama giri\u015fimleri, kullan\u0131c\u0131 olu\u015fturma, yetkilendirme kararlar\u0131 vb.) g\u00fcnl\u00fckler. Bu g\u00fcnl\u00fckleri merkezi bir g\u00fcnl\u00fck y\u00f6netim sistemine (\u00f6rne\u011fin, ELK Stack – Elasticsearch, Logstash, Kibana veya Grafana Loki) aktarmak, g\u00fcvenlik denetimleri ve sorun giderme i\u00e7in hayati \u00f6neme sahiptir.<\/p>\n
        Performans izlemesi i\u00e7in Prometheus ve Grafana kombinasyonu idealdir. ZITADEL, Prometheus uyumlu metrikleri d\u0131\u015fa aktarabilir. Prometheus ile ZITADEL metriklerini toplayabilir, Grafana ile bu metrikleri g\u00f6rselle\u015ftiren panolar olu\u015fturabilirsiniz. CPU kullan\u0131m\u0131, bellek t\u00fcketimi, veritaban\u0131 ba\u011flant\u0131lar\u0131, kimlik do\u011frulama gecikmeleri gibi metrikleri izleyerek olas\u0131 performans sorunlar\u0131n\u0131 \u00f6nceden tespit edebilir ve proaktif \u00f6nlemler alabilirsiniz.<\/p>\n
        \n
        # \u00d6rnek Prometheus scrape yap\u0131land\u0131rmas\u0131 (prometheus.yaml)\n- job_name: 'zitadel'\n  static_configs:\n    - targets: ['zitadel-service:8080'] # ZITADEL servisinizin adresi ve metrik portu\n  metrics_path: '\/metrics' # ZITADEL'in metrik endpoint'i<\/code><\/pre>\n<\/div>\n
        G\u00fcvenlik Denetimleri ve G\u00fcncelleme Y\u00f6netimi<\/h3>\n
        ZITADEL’i d\u00fczenli olarak en son s\u00fcr\u00fcme g\u00fcncellemek, g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131 kapatmak ve yeni \u00f6zelliklerden yararlanmak i\u00e7in kritik \u00f6neme sahiptir. Helm kullanarak g\u00fcncellemeleri kolayca uygulayabilirsiniz. G\u00fcncelleme \u00f6ncesinde test ortam\u0131nda denemeler yapmak ve veritaban\u0131 yedeklemesi almak iyi bir pratiktir. Ayr\u0131ca, ZITADEL’in g\u00fcvenlik yap\u0131land\u0131rmalar\u0131n\u0131 periyodik olarak g\u00f6zden ge\u00e7irmeli, g\u00fc\u00e7l\u00fc parola politikalar\u0131 uygulamal\u0131, MFA’y\u0131 zorunlu k\u0131lmal\u0131 ve en az ayr\u0131cal\u0131k (least privilege) prensibiyle eri\u015fim yetkilerini y\u00f6netmelisiniz. Penetrasyon testleri ve g\u00fcvenlik denetimleri, potansiyel zay\u0131fl\u0131klar\u0131 belirlemenize yard\u0131mc\u0131 olabilir.<\/p>\n
        \u00d6l\u00e7eklendirme Stratejileri<\/h3>\n
        ZITADEL, Kubernetes \u00fczerinde da\u011f\u0131t\u0131ld\u0131\u011f\u0131 i\u00e7in yatay pod otomatik \u00f6l\u00e7eklendirme (Horizontal Pod Autoscaler – HPA) kullanarak talebe g\u00f6re otomatik olarak \u00f6l\u00e7eklenebilir. CPU veya bellek kullan\u0131m\u0131 gibi metrikleri temel alarak ZITADEL pod’lar\u0131n\u0131n say\u0131s\u0131n\u0131 dinamik olarak art\u0131r\u0131p azaltabilirsiniz. Veritaban\u0131 taraf\u0131nda ise, PostgreSQL okuma replikalar\u0131 (read replicas) ekleyerek okuma yo\u011funlu\u011funu da\u011f\u0131tabilir ve ana veritaban\u0131n\u0131n y\u00fck\u00fcn\u00fc azaltabilirsiniz. B\u00fcy\u00fck \u00f6l\u00e7ekli da\u011f\u0131t\u0131mlarda, veritaban\u0131 sharding gibi daha ileri d\u00fczey \u00f6l\u00e7eklendirme teknikleri de de\u011ferlendirilebilir.<\/p>\n
        Son olarak, ZITADEL da\u011f\u0131t\u0131m\u0131n\u0131z\u0131 bir WAF (Web Application Firewall) veya DDoS koruma hizmeti (\u00f6rne\u011fin, Cloudflare, Akamai) arkas\u0131na yerle\u015ftirmek, k\u00f6t\u00fc niyetli trafik ve sald\u0131r\u0131lara kar\u015f\u0131 ek bir koruma katman\u0131 sa\u011flayacakt\u0131r. Bu optimizasyonlar, ZITADEL da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n hem g\u00fcvenli hem de performansl\u0131 bir \u015fekilde \u00e7al\u0131\u015fmas\u0131n\u0131 garanti alt\u0131na alacakt\u0131r.<\/p>\n
        \u0130leri D\u00fczey ZITADEL Kullan\u0131m\u0131 ve Entegrasyon \u0130pu\u00e7lar\u0131<\/h2>\n
        ZITADEL’in temel kurulumu ve yap\u0131land\u0131rmas\u0131yla yetinmeyip, platformun sundu\u011fu geli\u015fmi\u015f \u00f6zellikleri ve entegrasyon yeteneklerini kullanarak kimlik y\u00f6netimi altyap\u0131n\u0131z\u0131 daha da g\u00fc\u00e7lendirebilirsiniz. Bu b\u00f6l\u00fcmde, deneyimli kullan\u0131c\u0131lar i\u00e7in ZITADEL’in daha derinlemesine kullan\u0131m\u0131na y\u00f6nelik ipu\u00e7lar\u0131 ve p\u00fcf noktalar\u0131 ele al\u0131nmaktad\u0131r.<\/p>\n
        \u00d6zel Marka (Custom Branding) ve Tema Ayarlar\u0131<\/h3>\n
        ZITADEL’in kullan\u0131c\u0131 aray\u00fcz\u00fcn\u00fc (login sayfas\u0131, kay\u0131t sayfas\u0131 vb.) kendi \u015firketinizin markas\u0131na ve kurumsal kimli\u011fine uygun hale getirebilirsiniz. Y\u00f6netici konsolu \u00fczerinden logolar\u0131, renk paletlerini ve metinleri \u00f6zelle\u015ftirebilirsiniz. Bu, kullan\u0131c\u0131lar\u0131n\u0131za daha tutarl\u0131 ve profesyonel bir deneyim sunar. \u00d6rne\u011fin, bir \u00fcniversite ZITADEL’i \u00f6\u011frencileri ve personeli i\u00e7in kullan\u0131rken, kendi kurumunun renklerini, logosunu ve slogan\u0131n\u0131 giri\u015f sayfas\u0131na yans\u0131tarak aidiyet hissini art\u0131rabilir.<\/p>\n
        Kullan\u0131c\u0131 Senkronizasyonu ve Harici Kimlik Sa\u011flay\u0131c\u0131lar\u0131<\/h3>\n
        Mevcut bir kullan\u0131c\u0131 dizininiz (\u00f6rne\u011fin, LDAP, Active Directory) varsa, ZITADEL’i bu dizinlerle senkronize ederek kullan\u0131c\u0131 ge\u00e7i\u015fini kolayla\u015ft\u0131rabilirsiniz. ZITADEL, harici kimlik sa\u011flay\u0131c\u0131lar\u0131n\u0131 (External Identity Providers) destekler. Google, GitHub, Microsoft, Apple gibi sosyal giri\u015f se\u00e7eneklerinin yan\u0131 s\u0131ra, SAML veya OIDC uyumlu di\u011fer kurumsal kimlik sa\u011flay\u0131c\u0131lar\u0131n\u0131 da entegre edebilirsiniz. Bu, kullan\u0131c\u0131lar\u0131n\u0131za esneklik sunarken, y\u00f6neticilere de merkezi bir kimlik y\u00f6netimi sa\u011flar. \u00d6rne\u011fin, bir \u015firketin \u00e7al\u0131\u015fanlar\u0131 i\u00e7in mevcut Active Directory’yi ZITADEL’e ba\u011flayarak, kullan\u0131c\u0131lar\u0131n \u015firket kimlik bilgileriyle ZITADEL destekli uygulamalara eri\u015fmesini sa\u011flayabiliriz.<\/p>\n
        \n
        \/\/ ZITADEL API ile harici IDP ekleme \u00f6rne\u011fi (pseudo kod)\n\/\/ Bu i\u015flem genellikle ZITADEL y\u00f6netici konsolu \u00fczerinden yap\u0131l\u0131r.\n\/\/ Ancak API ile otomatize edilebilir.\nPOST \/management\/v1\/orgs\/{orgId}\/idps\/oidc\nContent-Type: application\/json\n\n{\n  \"name\": \"Google\",\n  \"client_id\": \"YOUR_GOOGLE_CLIENT_ID\",\n  \"client_secret\": \"YOUR_GOOGLE_CLIENT_SECRET\",\n  \"issuer\": \"https:\/\/accounts.google.com\",\n  \"scopes\": [\"openid\", \"email\", \"profile\"],\n  \"is_auto_creation\": true, \/\/ Kullan\u0131c\u0131 otomatik olu\u015fturulsun mu?\n  \"is_auto_update\": true \/\/ Kullan\u0131c\u0131 bilgileri otomatik g\u00fcncellensin mi?\n}<\/code><\/pre>\n<\/div>\n
        WebAuthn (Passkeys) Deste\u011fi<\/h3>\n
        Parolas\u0131z kimlik do\u011frulaman\u0131n gelece\u011fi olarak g\u00f6r\u00fclen WebAuthn (Passkeys) deste\u011fi, ZITADEL’in \u00f6nemli bir g\u00fcvenlik \u00f6zelli\u011fidir. Kullan\u0131c\u0131lar\u0131n\u0131z\u0131n fiziksel g\u00fcvenlik anahtarlar\u0131, parmak izi okuyucular veya y\u00fcz tan\u0131ma gibi y\u00f6ntemlerle kimlik do\u011frulamas\u0131 yapmas\u0131na olanak tan\u0131r. Bu, hem g\u00fcvenlik seviyesini art\u0131r\u0131r hem de kullan\u0131c\u0131 deneyimini iyile\u015ftirir. ZITADEL konsolundan WebAuthn sa\u011flay\u0131c\u0131s\u0131n\u0131 etkinle\u015ftirerek bu \u00f6zelli\u011fi kullan\u0131ma a\u00e7abilirsiniz.<\/p>\n
        API Gateway Entegrasyonlar\u0131<\/h3>\n
        Mikroservis mimarilerinde ZITADEL’i bir API Gateway (\u00f6rne\u011fin, Kong, Apigee, AWS API Gateway) ile entegre etmek, API g\u00fcvenli\u011fini merkezile\u015ftirmenin etkili bir yoludur. API Gateway, gelen isteklerdeki JWT (JSON Web Token) veya OAuth belirte\u00e7lerini ZITADEL ile do\u011frulayabilir ve yaln\u0131zca ge\u00e7erli belirte\u00e7lere sahip isteklerin arka u\u00e7 servislerine ula\u015fmas\u0131na izin verebilir. Bu, her mikroservisin kendi kimlik do\u011frulama ve yetkilendirme mant\u0131\u011f\u0131n\u0131 uygulamas\u0131na gerek kalmadan, tutarl\u0131 bir g\u00fcvenlik katman\u0131 sa\u011flar.<\/p>\n
        CI\/CD S\u00fcre\u00e7lerine Entegrasyon<\/h3>\n
        ZITADEL’in yap\u0131land\u0131rmas\u0131n\u0131 ve da\u011f\u0131t\u0131m\u0131n\u0131 CI\/CD (S\u00fcrekli Entegrasyon\/S\u00fcrekli Da\u011f\u0131t\u0131m) boru hatlar\u0131n\u0131za entegre etmek, operasyonel verimlili\u011fi art\u0131r\u0131r. Helm chart’lar\u0131 kullanarak ZITADEL g\u00fcncellemelerini otomatikle\u015ftirebilir, ZITADEL’in API’lerini kullanarak kurulu\u015f, proje, uygulama ve kullan\u0131c\u0131 olu\u015fturma gibi i\u015flemleri kod ile y\u00f6netebilirsiniz (Infrastructure as Code). Bu, \u00f6zellikle \u00e7ok say\u0131da proje veya kirac\u0131 y\u00f6neten b\u00fcy\u00fck organizasyonlar i\u00e7in zaman ve emek tasarrufu sa\u011flar.<\/p>\n
        Bu ileri d\u00fczey kullan\u0131m ve entegrasyon ipu\u00e7lar\u0131, ZITADEL’in tam potansiyelini ortaya \u00e7\u0131karman\u0131za ve kimlik y\u00f6netimi altyap\u0131n\u0131z\u0131 daha sa\u011flam, g\u00fcvenli ve otomatize edilmi\u015f hale getirmenize yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n
        Sonu\u00e7: ZITADEL ile Kimlik Y\u00f6netiminde Gelece\u011fe Y\u00f6nelik Ad\u0131mlar<\/h2>\n
        Bu makale boyunca, ZITADEL’in modern kimlik ve eri\u015fim y\u00f6netimi (IAM) ihtiya\u00e7lar\u0131 i\u00e7in neden g\u00fc\u00e7l\u00fc bir a\u00e7\u0131k kaynak \u00e7\u00f6z\u00fcm\u00fc oldu\u011funu, Kubernetes ve Docker Compose \u00fczerinde nas\u0131l da\u011f\u0131t\u0131laca\u011f\u0131n\u0131, temel ve ileri d\u00fczey yap\u0131land\u0131rmalar\u0131n\u0131 ve g\u00fcvenlik optimizasyonlar\u0131n\u0131 detayl\u0131 bir \u015fekilde inceledik. Geleneksel IAM \u00e7\u00f6z\u00fcmlerinin karma\u015f\u0131kl\u0131\u011f\u0131na ve maliyetine kar\u015f\u0131 ZITADEL, bulut yerlisi mimarisi, \u00e7ok kirac\u0131l\u0131 yap\u0131s\u0131 ve a\u00e7\u0131k standartlara ba\u011fl\u0131l\u0131\u011f\u0131 ile geli\u015ftiricilere ve kurumlara esneklik, \u00f6l\u00e7eklenebilirlik ve veri egemenli\u011fi sunmaktad\u0131r.<\/p>\n
        ZITADEL’i kendi altyap\u0131n\u0131zda bar\u0131nd\u0131rma yetene\u011fi, \u00f6zellikle hassas verilerle \u00e7al\u0131\u015fan veya belirli d\u00fczenlemelere tabi olan kurulu\u015flar i\u00e7in kritik bir avantajd\u0131r. Kubernetes ile entegrasyonu sayesinde, y\u00fcksek eri\u015filebilirlik, otomatik \u00f6l\u00e7eklendirme ve felaket kurtarma gibi kurumsal d\u00fczeyde gereksinimleri kolayca kar\u015f\u0131layabilirsiniz. Ayr\u0131ca, OpenID Connect ve OAuth 2.0 gibi end\u00fcstri standartlar\u0131n\u0131 desteklemesi, mevcut ve gelecekteki uygulamalar\u0131n\u0131zla sorunsuz entegrasyonu garanti eder.<\/p>\n
        Kimlik y\u00f6netimi, dijital d\u00f6n\u00fc\u015f\u00fcm\u00fcn temel ta\u015flar\u0131ndan biridir ve ZITADEL gibi modern, a\u00e7\u0131k kaynak platformlar, bu alandaki zorluklar\u0131n \u00fcstesinden gelmek i\u00e7in g\u00fc\u00e7l\u00fc ara\u00e7lar sunar. G\u00fcvenli\u011finizi art\u0131r\u0131rken kullan\u0131c\u0131 deneyiminizi iyile\u015ftirmek, operasyonel y\u00fck\u00fcn\u00fcz\u00fc azaltmak ve gelecekteki ihtiya\u00e7lara adapte olabilen bir altyap\u0131 kurmak i\u00e7in ZITADEL’i de\u011ferlendirmenizi \u015fiddetle tavsiye ederiz. ZITADEL toplulu\u011fu s\u00fcrekli geli\u015fmekte ve platforma yeni \u00f6zellikler eklemektedir, bu da onu uzun vadede s\u00fcrd\u00fcr\u00fclebilir ve yenilik\u00e7i bir \u00e7\u00f6z\u00fcm haline getirmektedir.<\/p>\n
        S\u0131k\u00e7a Sorulan Sorular (SSS)<\/h3>\n
        \n
        ZITADEL \u00fccretli mi?<\/dt>\n
        ZITADEL’in \u00e7ekirdek platformu tamamen a\u00e7\u0131k kaynakl\u0131 ve \u00fccretsizdir. Kendi altyap\u0131n\u0131zda bar\u0131nd\u0131rabilir ve kullanabilirsiniz. ZITADEL ayn\u0131 zamanda y\u00f6netilen bir bulut hizmeti (SaaS) de sunar; bu hizmet belirli \u00f6zellikler ve destek seviyeleri i\u00e7in \u00fccretli olabilir. Kurumsal destek veya ek \u00f6zellikler i\u00e7in ticari lisanslama se\u00e7enekleri de mevcuttur.<\/dd>\n
        ZITADEL’i mevcut uygulamalar\u0131ma nas\u0131l entegre ederim?<\/dt>\n
        ZITADEL, OpenID Connect (OIDC) ve OAuth 2.0 gibi a\u00e7\u0131k standartlar\u0131 destekler. Bu, \u00e7o\u011fu modern web, mobil ve API uygulamas\u0131n\u0131n ZITADEL ile kolayca entegre edilebilece\u011fi anlam\u0131na gelir. Uygulaman\u0131z\u0131n programlama diline veya \u00e7er\u00e7evesine (framework) uygun OIDC\/OAuth 2.0 istemci k\u00fct\u00fcphanelerini kullanarak ZITADEL’i kimlik do\u011frulama ve yetkilendirme sa\u011flay\u0131c\u0131s\u0131 olarak yap\u0131land\u0131rabilirsiniz. ZITADEL y\u00f6netici konsolundan uygulaman\u0131z\u0131 kaydederek Client ID ve Client Secret gibi gerekli kimlik bilgilerini alabilirsiniz.<\/dd>\n
        Veri g\u00fcvenli\u011fi konusunda ZITADEL ne gibi \u00f6nlemler al\u0131yor?<\/dt>\n
        ZITADEL, veri g\u00fcvenli\u011fini sa\u011flamak i\u00e7in \u00e7e\u015fitli \u00f6nlemler al\u0131r. Veriler hem aktar\u0131m s\u0131ras\u0131nda (TLS\/SSL ile) hem de depoda (master key ile \u015fifreleme) \u015fifrelenir. Rol Tabanl\u0131 Eri\u015fim Kontrol\u00fc (RBAC) ile kullan\u0131c\u0131lar\u0131n ve uygulamalar\u0131n sadece yetkili olduklar\u0131 verilere eri\u015fimi sa\u011flan\u0131r. Platform, g\u00fcvenlik denetim g\u00fcnl\u00fckleri (audit logs) tutarak t\u00fcm \u00f6nemli etkinlikleri kaydeder. Ayr\u0131ca, \u00c7ok Fakt\u00f6rl\u00fc Kimlik Do\u011frulama (MFA) ve WebAuthn (Passkeys) gibi geli\u015fmi\u015f kimlik do\u011frulama mekanizmalar\u0131n\u0131 destekleyerek hesap g\u00fcvenli\u011fini art\u0131r\u0131r.<\/dd>\n
        ZITADEL’in performans\u0131n\u0131 nas\u0131l izleyebilirim?<\/dt>\n
        ZITADEL, Prometheus uyumlu metrikleri d\u0131\u015fa aktar\u0131r. Prometheus’u kullanarak ZITADEL’den performans metriklerini (CPU kullan\u0131m\u0131, bellek, istek gecikmeleri, hata oranlar\u0131 vb.) toplayabilirsiniz. Bu metrikleri Grafana gibi bir ara\u00e7la g\u00f6rselle\u015ftirerek ZITADEL da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n sa\u011fl\u0131\u011f\u0131n\u0131 ve performans\u0131n\u0131 ger\u00e7ek zamanl\u0131 olarak izleyebilirsiniz. Ayr\u0131ca, ZITADEL’in g\u00fcnl\u00fcklerini merkezi bir g\u00fcnl\u00fck y\u00f6netim sistemine (ELK Stack, Grafana Loki) aktararak sorun giderme ve g\u00fcvenlik denetimi yapabilirsiniz.<\/dd>\n
        Multi-tenancy (\u00e7ok kirac\u0131l\u0131l\u0131k) nedir ve ZITADEL bunu nas\u0131l destekler?<\/dt>\n
        Multi-tenancy, tek bir yaz\u0131l\u0131m \u00f6rne\u011finin (ZITADEL gibi) birden fazla ba\u011f\u0131ms\u0131z m\u00fc\u015fteri veya kurulu\u015fa (kirac\u0131ya) hizmet verebilmesi yetene\u011fidir. ZITADEL bunu “Organizasyonlar” (Organizations) kavram\u0131 arac\u0131l\u0131\u011f\u0131yla destekler. Her kurulu\u015f, kendi kullan\u0131c\u0131lar\u0131na, uygulamalar\u0131na, kimlik sa\u011flay\u0131c\u0131lar\u0131na ve g\u00fcvenlik politikalar\u0131na sahip, tamamen izole edilmi\u015f bir kimlik alan\u0131na sahiptir. Bu, SaaS sa\u011flay\u0131c\u0131lar\u0131n\u0131n veya birden fazla departmana sahip b\u00fcy\u00fck \u015firketlerin, her kirac\u0131 i\u00e7in ayr\u0131 bir ZITADEL \u00f6rne\u011fi kurmaya gerek kalmadan kimlik y\u00f6netimini merkezi ve verimli bir \u015fekilde yapmas\u0131n\u0131 sa\u011flar.<\/dd>\n<\/dl>\n
        #ZITADEL #IAM #KimlikY\u00f6netimi #A\u00e7\u0131kKaynak #Kubernetes #OAuth #OpenIDConnect #SiberG\u00fcvenlik #WebGeli\u015ftirme #Teknoloji<\/p>\n","protected":false},"excerpt":{"rendered":"Modern uygulamalar i\u00e7in g\u00fcvenli, esnek ve \u00f6l\u00e7eklenebilir kimlik ve eri\u015fim y\u00f6netimi (IAM) \u00e7\u00f6z\u00fcmleri arayan geli\u015ftiriciler ve kurumlar i\u00e7in ZITADEL, g\u00fc\u00e7l\u00fc bir a\u00e7\u0131k kaynak alternatifi sunar.","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1],"tags":[],"class_list":{"0":"post-43890","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-genel","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"ZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu\" \/>\n<meta property=\"og:description\" content=\"Modern uygulamalar i\u00e7in g\u00fcvenli, esnek ve \u00f6l\u00e7eklenebilir kimlik ve eri\u015fim y\u00f6netimi (IAM) \u00e7\u00f6z\u00fcmleri arayan geli\u015ftiriciler ve kurumlar i\u00e7in ZITADEL, g\u00fc\u00e7l\u00fc bir a\u00e7\u0131k kaynak alternatifi sunar.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-06T18:11:42+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"26 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"ZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu\",\"datePublished\":\"2026-08-06T18:11:42+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/\"},\"wordCount\":4709,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/#respond\"]}],\"copyrightYear\":\"2026\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/\",\"name\":\"ZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2026-08-06T18:11:42+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"ZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/","og_locale":"tr_TR","og_type":"article","og_title":"ZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu","og_description":"Modern uygulamalar i\u00e7in g\u00fcvenli, esnek ve \u00f6l\u00e7eklenebilir kimlik ve eri\u015fim y\u00f6netimi (IAM) \u00e7\u00f6z\u00fcmleri arayan geli\u015ftiriciler ve kurumlar i\u00e7in ZITADEL, g\u00fc\u00e7l\u00fc bir a\u00e7\u0131k kaynak alternatifi sunar.","og_url":"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2026-08-06T18:11:42+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"26 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"ZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu","datePublished":"2026-08-06T18:11:42+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/"},"wordCount":4709,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/#respond"]}],"copyrightYear":"2026","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/","url":"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/","name":"ZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2026-08-06T18:11:42+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/zitadel-dagitimi-acik-kaynak-kimlik-ve-erisim-yonetimi-platformu\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"ZITADEL Da\u011f\u0131t\u0131m\u0131: A\u00e7\u0131k Kaynak Kimlik ve Eri\u015fim Y\u00f6netimi Platformu"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/43890","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=43890"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/43890\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=43890"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=43890"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=43890"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}