{"id":70867,"date":"2020-02-22T06:40:58","date_gmt":"2020-02-22T03:40:58","guid":{"rendered":"https:\/\/prohoster.info\/blog\/prikruchivaem-ldap-avtorizacziyu-k-kubernetes"},"modified":"2020-03-03T16:14:36","modified_gmt":"2020-03-03T13:14:36","slug":"prikruchivaem-ldap-avtorizacziyu-k-kubernetes","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/prikruchivaem-ldap-avtorizacziyu-k-kubernetes","title":{"rendered":"Integracija LDAP autorizacije s Kubernetesom","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Integracija LDAP autorizacije s Kubernetesom\" src=\"\/wp-content\/uploads\/2020\/02\/2b0f0a4921e049a78a015e7693d697cf.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>Kratki vodi\u010d o tome kako povezati Kubernetes s va\u0161im LDAP poslu\u017eiteljem koriste\u0107i Keycloak i postaviti uvoz korisnika i grupa. To \u0107e omogu\u0107iti konfiguraciju RBAC-a za va\u0161e korisnike i kori\u0161tenje auth-proxy-a za za\u0161titu Kubernetes Dashboards i drugih aplikacija koje ne mogu samostalno provesti autorizaciju.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2 id=\"ustanovka-keycloak\">Instalacija Keycloak-a<\/h2>\n<p><\/p>\n<p>Pretpostavimo da ve\u0107 imate LDAP poslu\u017eitelj. To mo\u017ee biti Active Directory, FreeIPA, OpenLDAP ili ne\u0161to drugo. Ako nemate LDAP poslu\u017eitelj, mo\u017eete stvarati korisnike izravno u su\u010delju Keycloak-a ili koristiti javne oidc pru\u017eatelje (Google, Github, Gitlab), rezultat \u0107e biti gotovo isti.<\/p>\n<p><\/p>\n<p>Prvo \u0107emo instalirati sam Keycloak, instalacija se mo\u017ee obaviti odvojeno ili odmah u Kubernetes klasteru. Ako imate vi\u0161e Kubernetes klastera, obi\u010dno bi bilo lak\u0161e instalirati ga odvojeno. S druge strane, uvijek mo\u017eete koristiti <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/helm\/charts\/tree\/master\/stable\/keycloak\">slu\u017ebeni helm chart<\/a><\/noindex> i instalirati ga izravno u va\u0161 klaster.<\/p>\n<p><\/p>\n<p>Za pohranu podataka Keycloak-a bit \u0107e vam potrebna baza podataka. Po defaultu se koristi <code>h2<\/code> (svi podaci se \u010duvaju lokalno), ali tako\u0111er mo\u017eete koristiti <code>postgres<\/code>, <code>mysql<\/code> ili <code>mariadb<\/code>.<br \/>\nAko ste se odlu\u010dili instalirati Keycloak odvojeno, detaljnije upute mo\u017eete prona\u0107i u <noindex><a rel=\"nofollow\" href=\"https:\/\/www.keycloak.org\/docs\/latest\/getting_started\/index.html\">slu\u017ebene dokumentacije<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h2 id=\"nastroyka-federacii\">Postavljanje federacije<\/h2>\n<p><\/p>\n<p>Prvo \u0107emo stvoriti novo kraljevstvo. Kraljevstvo je prostor na\u0161e aplikacije. Svaka aplikacija mo\u017ee imati svoje kraljevstvo s razli\u010ditim korisnicima i postavkama autorizacije. Master kraljevstvo koristi sam Keycloak i pogre\u0161no je koristiti ga za ne\u0161to drugo.<\/p>\n<p><\/p>\n<p>Kliknemo <strong>Dodaj kraljevstvo<\/strong><\/p>\n<p><\/p>\n<p>Opcija<br \/>\nVrijednost<\/p>\n<p><strong>Name<\/strong><br \/>\n<code>kubernetes<\/code><\/p>\n<p><strong>Prikazno ime<\/strong><br \/>\n<code>Kubernetes<\/code><\/p>\n<p><strong>HTML Prikazno ime<\/strong><br \/>\n<code>&lt;img src=&quot;https:\/\/kubernetes.io\/images\/nav_logo.svg&quot; width=&quot;400&quot; &gt;<\/code><\/p>\n<p><\/p>\n<p>Kubernetes standardno provjerava je li korisnik potvrdio svoj email. Budu\u0107i da koristimo vlastiti LDAP poslu\u017eitelj, ova provjera \u0107e gotovo uvijek vra\u0107ati <code>false<\/code>. Isklju\u010dimo prikaz ove postavke u Kubernetes-u:<\/p>\n<p><\/p>\n<p><strong>Klijentske sfere<\/strong> --&gt; <strong>Email<\/strong> --&gt; <strong>Mapperi<\/strong> --&gt; <strong>Email potvr\u0111en<\/strong> (Izbri\u0161i)<\/p>\n<p><\/p>\n<p>Sada \u0107emo postaviti federaciju, za to idemo na:<\/p>\n<p><\/p>\n<p><strong>Federacija korisnika<\/strong> --&gt; <strong>Dodajte pru\u017eatelja\u2026<\/strong> --&gt; <strong>ldap<\/strong><\/p>\n<p><\/p>\n<p>Dajem primjer postavke za FreeIPA:<\/p>\n<p><\/p>\n<p>Opcija<br \/>\nVrijednost<\/p>\n<p><strong>Naziv prikaza konzole<\/strong><br \/>\n<code>freeipa.example.org<\/code><\/p>\n<p><strong>Dobavlja\u010d<\/strong><br \/>\n<code>Red Hat Directory Server<\/code><\/p>\n<p><strong>UUID LDAP atribut<\/strong><br \/>\n<code>ipauniqueid<\/code><\/p>\n<p><strong>URL veze<\/strong><br \/>\n<code>ldaps:\/\/freeipa.example.org<\/code><\/p>\n<p><strong>DN korisnika<\/strong><br \/>\n<code>cn=users,cn=accounts,dc=example,dc=org<\/code><\/p>\n<p><strong>Bind DN<\/strong><br \/>\n<code>uid=keycloak-svc,cn=users,cn=accounts,dc=example,dc=org<\/code><\/p>\n<p><strong>Bind vjerodajnica<\/strong><br \/>\n<code>&lt;password&gt;<\/code><\/p>\n<p><strong>Dopusti Kerberos autentifikaciju:<\/strong><br \/>\n<code>uklju\u010deno<\/code><\/p>\n<p><strong>Kerberos kraljevstvo:<\/strong><br \/>\n<code>EXAMPLE.ORG<\/code><\/p>\n<p><strong>Server Principal:<\/strong><br \/>\n<code>HTTP\/freeipa.example.org@EXAMPLE.ORG<\/code><\/p>\n<p><strong>KeyTab:<\/strong><br \/>\n<code>\/etc\/krb5.keytab<\/code><\/p>\n<p><\/p>\n<p>Korisnika <code>keycloak-svc<\/code> treba prethodno stvoriti na na\u0161em LDAP poslu\u017eitelju.<\/p>\n<p><\/p>\n<p>U slu\u010daju Active Directory, dovoljno je samo odabrati <strong>Dobavlja\u010d: Active Directory<\/strong> i potrebne postavke \u0107e se automatski unijeti u obrazac.<\/p>\n<p><\/p>\n<p>Kliknemo <strong>Spremi<\/strong><\/p>\n<p><\/p>\n<p>Sada idemo na:<\/p>\n<p><\/p>\n<p><strong>Federacija korisnika<\/strong> --&gt; <strong>freeipa.example.org<\/strong> --&gt; <strong>Mapperi<\/strong> --&gt; <strong>Ime<\/strong><\/p>\n<p><\/p>\n<p>Opcija<br \/>\nVrijednost<\/p>\n<p><strong>Ldap atribut<\/strong><br \/>\n<code>givenName<\/code><\/p>\n<p><\/p>\n<p>Sada \u0107emo uklju\u010diti mapiranje grupa:<\/p>\n<p><\/p>\n<p><strong>Federacija korisnika<\/strong> --&gt; <strong>freeipa.example.org<\/strong> --&gt; <strong>Mapperi<\/strong> --&gt; <strong>Create<\/strong><\/p>\n<p><\/p>\n<p>Opcija<br \/>\nVrijednost<\/p>\n<p><strong>Name<\/strong><br \/>\n<code>groups<\/code><\/p>\n<p><strong>Tip mappera<\/strong><br \/>\n<code>group-ldap-mapper<\/code><\/p>\n<p><strong>LDAP Grupe DN<\/strong><br \/>\n<code>cn=groups,cn=accounts,dc=example,dc=org<\/code><\/p>\n<p><strong>Strategija dobivanja korisni\u010dkih grupa<\/strong><br \/>\n<code>GET_GROUPS_FROM_USER_MEMBEROF_ATTRIBUTE<\/code><\/p>\n<p><\/p>\n<p>Time je postavljanje federacije zavr\u0161eno, pre\u0111imo na postavku klijenta.<\/p>\n<p><\/p>\n<h2 id=\"nastroyka-klienta\">Postavka klijenta<\/h2>\n<p><\/p>\n<p>Stvorimo novog klijenta (aplikacija koja \u0107e primati korisnike iz Keycloak-a). Idemo na:<\/p>\n<p><\/p>\n<p><strong>Klijenti<\/strong> --&gt; <strong>Create<\/strong><\/p>\n<p><\/p>\n<p>Opcija<br \/>\nVrijednost<\/p>\n<p><strong>Client ID<\/strong><br \/>\n<code>kubernetes<\/code><\/p>\n<p><strong>Tip pristupa<\/strong><br \/>\n<code>confidenrial<\/code><\/p>\n<p><strong>Osnovni URL<\/strong><br \/>\n<code>http:\/\/kubernetes.example.org\/<\/code><\/p>\n<p><strong>Valjane URI preusmjeravanja<\/strong><br \/>\n<code>http:\/\/kubernetes.example.org\/*<\/code><\/p>\n<p><strong>Admin URL<\/strong><br \/>\n<code>http:\/\/kubernetes.example.org\/<\/code><\/p>\n<p><\/p>\n<p>Tako\u0111er \u0107emo stvoriti scope za grupe:<\/p>\n<p><\/p>\n<p><strong>Scopes klijenta<\/strong> --&gt; <strong>Create<\/strong><\/p>\n<p><\/p>\n<p>Opcija<br \/>\nVrijednost<\/p>\n<p><strong>Predlo\u017eak<\/strong><br \/>\n<code>Nema predlo\u0161ka<\/code><\/p>\n<p><strong>Name<\/strong><br \/>\n<code>groups<\/code><\/p>\n<p><strong>Puni put do grupe<\/strong><br \/>\n<code>false<\/code><\/p>\n<p><\/p>\n<p>I postavi\u0107emo mapper za njih:<\/p>\n<p><\/p>\n<p><strong>Scopes klijenta<\/strong> --&gt; <strong>groups<\/strong> --&gt; <strong>Mapperi<\/strong> --&gt; <strong>Create<\/strong><\/p>\n<p><\/p>\n<p>Opcija<br \/>\nVrijednost<\/p>\n<p><strong>Name<\/strong><br \/>\n<code>groups<\/code><\/p>\n<p><strong>Tip mappera<\/strong><br \/>\n<code>\u010clanstvo u grupi<\/code><\/p>\n<p><strong>Ime tokenovog zahtjeva<\/strong><br \/>\n<code>groups<\/code><\/p>\n<p><\/p>\n<p>Sada trebamo omogu\u0107iti mapiranje grupa u na\u0161em client scope-u:<\/p>\n<p><\/p>\n<p><strong>Klijenti<\/strong> --&gt; <strong>kubernetes<\/strong> --&gt; <strong>Scopes klijenta<\/strong> --&gt; <strong>Zadani client scope-ovi<\/strong><\/p>\n<p><\/p>\n<p>Biramo <strong>groups<\/strong> u <strong>Dostupni client scope-ovi<\/strong>, kliknite <strong>Dodaj odabrano<\/strong><\/p>\n<p><\/p>\n<p>Sada \u0107emo postaviti autentifikaciju na\u0161e aplikacije, idemo na:<\/p>\n<p><\/p>\n<p><strong>Klijenti<\/strong> --&gt; <strong>kubernetes<\/strong><\/p>\n<p><\/p>\n<p>Opcija<br \/>\nVrijednost<\/p>\n<p><strong>Autorizacija omogu\u0107ena<\/strong><br \/>\n<code>ON<\/code><\/p>\n<p><\/p>\n<p>Kliknite <strong>spremi<\/strong> i time je postavka klijenta zavr\u0161ena, sada na kartici<\/p>\n<p><\/p>\n<p><strong>Klijenti<\/strong> --&gt; <strong>kubernetes<\/strong> --&gt; <strong>Akreditivi<\/strong><\/p>\n<p><\/p>\n<p>mo\u017eete dobiti <strong>Tajna<\/strong> koju \u0107emo koristiti u nastavku.<\/p>\n<p><\/p>\n<h2 id=\"nastroyka-kubernetes\">Postavka Kubernetes-a<\/h2>\n<p><\/p>\n<p>Postavka Kubernetes-a za OIDC-autorizaciju je relativno trivijalna i nije jako slo\u017eena. Sve \u0161to trebate je staviti CA-certifikat va\u0161eg OIDC-servera u <code>\/etc\/kubernetes\/pki\/oidc-ca.pem<\/code> i dodati potrebne opcije za kube-apiserver.<br \/>\nZa to a\u017eurirajte <code>\/etc\/kubernetes\/manifests\/kube-apiserver.yaml<\/code> na svim va\u0161im majstorima:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">...\nspec:\n  containers:\n  - command:\n    - kube-apiserver\n...\n    - --oidc-ca-file=\/etc\/kubernetes\/pki\/oidc-ca.pem\n    - --oidc-client-id=kubernetes\n    - --oidc-groups-claim=groups\n    - --oidc-issuer-url=https:\/\/keycloak.example.org\/auth\/realms\/kubernetes\n    - --oidc-username-claim=email\n...<\/code><\/pre>\n<p><\/p>\n<p>Tako\u0111er a\u017eurirajte kubeadm konfiguraciju u klasteru kako ne biste izgubili te postavke prilikom a\u017euriranja:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">kubectl edit -n kube-system configmaps kubeadm-config<\/code><\/pre>\n<p><\/p>\n<pre><code class=\"plaintext\">...\ndata:\n  ClusterConfiguration: |\n    apiServer:\n      extraArgs:\n        oidc-ca-file: \/etc\/kubernetes\/pki\/oidc-ca.pem\n        oidc-client-id: kubernetes\n        oidc-groups-claim: groups\n        oidc-issuer-url: https:\/\/keycloak.example.org\/auth\/realms\/kubernetes\n        oidc-username-claim: email\n...<\/code><\/pre>\n<p><\/p>\n<p>Time je postavka Kubernetes-a zavr\u0161ena. Mo\u017eete ponoviti iste radnje u svim va\u0161im Kubernetes klasterima.<\/p>\n<p><\/p>\n<h2 id=\"nachalnaya-avtorizaciya\">Po\u010detna autorizacija<\/h2>\n<p><\/p>\n<p>Nakon tih radnji ve\u0107 \u0107ete imati Kubernetes klaster sa postavljenom OIDC-autorizacijom. Jedina stvar je da va\u0161i korisnici jo\u0161 nemaju postavljenog klijenta kao ni vlastiti kubeconfig. Da biste rije\u0161ili ovaj problem potrebno je postaviti automatsko izdavanje kubeconfig-a korisnicima nakon uspje\u0161ne autorizacije.<\/p>\n<p><\/p>\n<p>Za to mo\u017eete koristiti posebne web-aplikacije koje omogu\u0107uju autentifikaciju korisnika, a zatim preuzimanje gotovog kubeconfiga. Jedna od najprakti\u010dnijih je <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/negz\/kuberos\">Kuberos<\/a><\/noindex>, koja omogu\u0107uje opisivanje svih Kubernetes klastera u jednoj konfiguraciji i jednostavno prebacivanje izme\u0111u njih.<\/p>\n<p><\/p>\n<p>Za postavljanje Kuberosa dovoljno je opisati predlo\u017eak za kubeconfig i pokrenuti s sljede\u0107im parametrima:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">kuberos https:\/\/keycloak.example.org\/auth\/realms\/kubernetes kubernetes \/cfg\/secret \/cfg\/template<\/code><\/pre>\n<p><\/p>\n<p>Za detaljnije informacije pogledajte <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/negz\/kuberos#usage\">Kori\u0161tenje<\/a><\/noindex> na Githubu.<\/p>\n<p><\/p>\n<p>Tako\u0111er je mogu\u0107e koristiti <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/int128\/kubelogin\">kubelogin<\/a><\/noindex> ako \u017eelite provesti autorizaciju izravno na korisni\u010dkom ra\u010dunalu. U tom slu\u010daju korisniku \u0107e se otvoriti preglednik s obrascem za autorizaciju na localhostu.<\/p>\n<p><\/p>\n<p>Dobiveni kubeconfig mo\u017eete provjeriti na web stranici <noindex><a rel=\"nofollow\" href=\"https:\/\/jwt.io\/#debugger-io\">jwt.io<\/a><\/noindex>. Jednostavno kopirajte vrijednost <code>users[].user.auth-provider.config.id-token<\/code> iz va\u0161eg kubeconfiga u obrazac na web stranici i odmah \u0107ete dobiti de\u0161ifriranje.<\/p>\n<p><\/p>\n<h2 id=\"nastroyka-rbac\">Postavljanje RBAC-a<\/h2>\n<p><\/p>\n<p>Prilikom postavljanja RBAC-a mo\u017eete se pozvati kako na ime korisnika (polje <code>ime<\/code> u jwt-tokenu), tako i na grupu korisnika (polje <code>groups<\/code> u jwt-tokenu). Evo primjera postavke prava za grupu <code>kubernetes-default-namespace-admins<\/code>:<\/p>\n<p>\n<b class=\"spoiler_title\">kubernetes-default-namespace-admins.yaml<\/b><\/p>\n<pre><code class=\"plaintext\">apiVersion: rbac.authorization.k8s.io\/v1\nkind: Role\nmetadata:\n  name: default-admins\n  namespace: default\nrules:\n- apiGroups:\n  - '*'\n  resources:\n  - '*'\n  verbs:\n  - '*'\n---\napiVersion: rbac.authorization.k8s.io\/v1\nkind: RoleBinding\nmetadata:\n  name: kubernetes-default-namespace-admins\n  namespace: default\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: Role\n  name: default-admins\nsubjects:\n- apiGroup: rbac.authorization.k8s.io\n  kind: Group\n  name: kubernetes-default-namespace-admins<\/code><\/pre>\n<p><\/p>\n<p>Vi\u0161e primjera za RBAC mo\u017eete prona\u0107i u <noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/reference\/access-authn-authz\/rbac\/\">slu\u017ebenoj dokumentaciji Kubernetes<\/a><\/noindex><\/p>\n<p><\/p>\n<h2 id=\"nastroyka-auth-proxy\">Postavljanje auth-proxy-a<\/h2>\n<p><\/p>\n<p>Postoji odli\u010dan projekt <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/keycloak\/keycloak-gatekeeper\">keycloak-gatekeeper<\/a><\/noindex>, koji omogu\u0107uje za\u0161titu bilo koje aplikacije, daju\u0107i korisniku mogu\u0107nost autentifikacije na OIDC poslu\u017eitelju. Pokazat \u0107u kako ga postaviti na primjeru Kubernetes Dashborda:<\/p>\n<p>\n<b class=\"spoiler_title\">dashboard-proxy.yaml<\/b><\/p>\n<pre><code class=\"plaintext\">apiVersion: extensions\/v1beta1\nkind: Deployment\nmetadata:\n  name: kubernetes-dashboard-proxy\nspec:\n  replicas: 1\n  template:\n    metadata:\n      labels:\n        app: kubernetes-dashboard-proxy\n    spec:\n      containers:\n      - args:\n        - --listen=0.0.0.0:80\n        - --discovery-url=https:\/\/keycloak.example.org\/auth\/realms\/kubernetes\n        - --client-id=kubernetes\n        - --client-secret=\n        - --redirection-url=https:\/\/kubernetes-dashboard.example.org\n        - --enable-refresh-tokens=true\n        - --encryption-key=ooTh6Chei1eefooyovai5ohwienuquoh\n        - --upstream-url=https:\/\/kubernetes-dashboard.kube-system\n        - --resources=uri=\/*\n        image: keycloak\/keycloak-gatekeeper\n        name: kubernetes-dashboard-proxy\n        ports:\n        - containerPort: 80\n          livenessProbe:\n            httpGet:\n              path: \/oauth\/health\n              port: 80\n            initialDelaySeconds: 3\n            timeoutSeconds: 2\n          readinessProbe:\n            httpGet:\n              path: \/oauth\/health\n              port: 80\n            initialDelaySeconds: 3\n            timeoutSeconds: 2\n---\napiVersion: v1\nkind: Service\nmetadata:\n  name: kubernetes-dashboard-proxy\nspec:\n  ports:\n  - port: 80\n    protocol: TCP\n    targetPort: 80\n  selector:\n    app: kubernetes-dashboard-proxy\n  type: ClusterIP<\/code><\/pre>\n<p>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/441112\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041d\u0435\u0431\u043e\u043b\u044c\u0448\u0430\u044f \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0446\u0438\u044f \u043e \u0442\u043e\u043c, \u043a\u0430\u043a \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044f Keycloak \u043c\u043e\u0436\u043d\u043e \u0441\u0432\u044f\u0437\u0430\u0442\u044c Kubernetes \u0441 \u0432\u0430\u0448\u0438\u043c LDAP-\u0441\u0435\u0440\u0432\u0435\u0440\u043e\u043c \u0438 \u043d\u0430\u0441\u0442\u0440\u043e\u0438\u0442\u044c \u0438\u043c\u043f\u043e\u0440\u0442 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0438 \u0433\u0440\u0443\u043f\u043f. \u042d\u0442\u043e \u043f\u043e\u0437\u0432\u043e\u043b\u0438\u0442 \u043d\u0430\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u0442\u044c RBAC \u0434\u043b\u044f \u0432\u0430\u0448\u0438\u0445 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0438 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c auth-proxy \u0447\u0442\u043e\u0431\u044b \u0437\u0430\u0449\u0438\u0442\u0438\u0442\u044c Kubernetes Dashboard \u0438 \u0434\u0440\u0443\u0433\u0438\u0435 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043d\u0435 \u0443\u043c\u0435\u044e\u0442 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u044c \u0430\u0432\u0442\u043e\u0440\u0438\u0437\u0430\u0446\u0438\u044e \u0441\u0430\u043c\u043e\u0441\u0442\u043e\u044f\u0442\u0435\u043b\u044c\u043d\u043e. \u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 Keycloak \u041f\u0440\u0435\u0434\u043f\u043e\u043b\u043e\u0436\u0438\u043c \u0447\u0442\u043e \u0443 \u0432\u0430\u0441 \u0443\u0436\u0435 \u0435\u0441\u0442\u044c LDAP-\u0441\u0435\u0440\u0432\u0435\u0440. \u042d\u0442\u043e \u043c\u043e\u0436\u0435\u0442 \u0431\u044b\u0442\u044c Active [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":70868,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-70867","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041d\u0435\u0431\u043e\u043b\u044c\u0448\u0430\u044f \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0446\u0438\u044f \u043e \u0442\u043e\u043c, \u043a\u0430\u043a.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/prikruchivaem-ldap-avtorizacziyu-k-kubernetes\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"hr_HR\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041f\u0440\u0438\u043a\u0440\u0443\u0447\u0438\u0432\u0430\u0435\u043c LDAP-\u0430\u0432\u0442\u043e\u0440\u0438\u0437\u0430\u0446\u0438\u044e \u043a Kubernetes | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041d\u0435\u0431\u043e\u043b\u044c\u0448\u0430\u044f \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0446\u0438\u044f \u043e \u0442\u043e\u043c, \u043a\u0430\u043a.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/prikruchivaem-ldap-avtorizacziyu-k-kubernetes\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-02-22T03:40:58+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-03-03T13:14:36+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Povezivanje LDAP autorizacije s Kubernetesom | ProHoster","description":"Mala uputa o tome kako.","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/prikruchivaem-ldap-avtorizacziyu-k-kubernetes","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041f\u0440\u0438\u043a\u0440\u0443\u0447\u0438\u0432\u0430\u0435\u043c LDAP-\u0430\u0432\u0442\u043e\u0440\u0438\u0437\u0430\u0446\u0438\u044e \u043a Kubernetes | ProHoster","og:description":"\u041d\u0435\u0431\u043e\u043b\u044c\u0448\u0430\u044f \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0446\u0438\u044f \u043e \u0442\u043e\u043c, \u043a\u0430\u043a.","og:url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/prikruchivaem-ldap-avtorizacziyu-k-kubernetes","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-02-22T03:40:58+00:00","article:modified_time":"2020-03-03T13:14:36+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"70867","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 19:12:23","updated":"2022-09-28 01:58:51","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/70867","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=70867"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/70867\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media\/70868"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=70867"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=70867"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=70867"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}