{"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\/sl\/blog\/administrirovanie\/prikruchivaem-ldap-avtorizacziyu-k-kubernetes","title":{"rendered":"\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","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"\u041f\u0440\u0438\u043a\u0440\u0443\u0447\u0438\u0432\u0430\u0435\u043c<\/p>\n

<\/p>\n

Majhna navodila o tem, kako lahko z uporabo Keycloaka pove\u017eete Kubernetes z va\u0161im LDAP stre\u017enikom in nastavite uvoz uporabnikov in skupin. To bo omogo\u010dilo nastavitev RBAC za va\u0161e uporabnike ter uporabo auth-proxy za za\u0161\u010dito Kubernetes nadzorne plo\u0161\u010de in drugih aplikacij, ki ne morejo samostojno izvajati avtorizacije.<\/p>\n

<\/a><\/noindex><\/p>\n

Instalacija Keycloak-a<\/h2>\n

<\/p>\n

Recimo, da \u017ee imate LDAP stre\u017enik. To je lahko Active Directory, FreeIPA, OpenLDAP ali karkoli drugega. \u010ce LDAP stre\u017enika nimate, lahko v bistvu ustvarite uporabnike neposredno v vmesniku Keycloaka ali pa uporabite javne oidc ponudnike (Google, Github, Gitlab), rezultat bo skoraj enak.<\/p>\n

<\/p>\n

Najprej namestimo sam Keycloak, namestitev se lahko izvede posebej ali takoj v Kubernetes grozdu, obi\u010dajno, \u010de imate ve\u010d Kubernetes grozdov, bi bilo la\u017eje namestiti ga posebej. Po drugi strani pa lahko vedno uporabite uradni helm graf<\/a><\/noindex> in ga namestite neposredno v va\u0161 grozd.<\/p>\n

<\/p>\n

Za shranjevanje podatkov Keycloaka potrebujete bazo podatkov. Po privzetu se uporablja h2<\/code> (vsi podatki se shranijo lokalno), vendar je mogo\u010de tudi uporabiti postgres<\/code>, mysql<\/code> ili mariadb<\/code>.
\n\u010ce se kljub vsemu odlo\u010dite namestiti Keycloak posebej, boste na\u0161li bolj podrobna navodila v uradni dokumentaciji<\/a><\/noindex>.<\/p>\n

<\/p>\n

Nastavitev federacije<\/h2>\n

<\/p>\n

Najprej ustvarimo nov realm. Realm je prostor na\u0161e aplikacije. Vsaka aplikacija ima lahko svoj realm z razli\u010dnimi uporabniki in nastavitvami avtorizacije. Master realm se uporablja samim Keycloakom in ga ni primerno uporabljati za kaj drugega.<\/p>\n

<\/p>\n

Kliknite Dodaj domeno<\/strong><\/p>\n

<\/p>\n

Option
\nVrednost<\/p>\n

Ime<\/strong>
\nkubernetes<\/code><\/p>\n

Prikazno ime<\/strong>
\nKubernetes<\/code><\/p>\n

HTML Display Name<\/strong>
\n<img src="https:\/\/kubernetes.io\/images\/nav_logo.svg" width="400" ><\/code><\/p>\n

<\/p>\n

Kubernetes po privzetu preverja, ali je uporabnik potrdil svoj e-po\u0161tni naslov ali ne. Ker uporabljamo lasten LDAP stre\u017enik, bo to preverjanje skoraj vedno vrnilo false<\/code>. Izklopimo prikaz te mo\u017enosti v Kubernetesu:<\/p>\n

<\/p>\n

Client scopes<\/strong> \u2192 Email<\/strong> \u2192 Mappers<\/strong> \u2192 Email verified<\/strong> (Zbri\u0161i)<\/p>\n

<\/p>\n

Zdaj nastavimo federacijo, zato pojdimo na:<\/p>\n

<\/p>\n

User federation<\/strong> \u2192 Dodaj ponudnika\u2026<\/strong> \u2192 ldap<\/strong><\/p>\n

<\/p>\n

Navedel bom primer nastavitve za FreeIPA:<\/p>\n

<\/p>\n

Option
\nVrednost<\/p>\n

Console Display Name<\/strong>
\nfreeipa.example.org<\/code><\/p>\n

Vendor<\/strong>
\nRed Hat Directory Server<\/code><\/p>\n

UUID LDAP attribute<\/strong>
\nipauniqueid<\/code><\/p>\n

Connection URL<\/strong>
\nldaps:\/\/freeipa.example.org<\/code><\/p>\n

Users DN<\/strong>
\ncn=users,cn=accounts,dc=example,dc=org<\/code><\/p>\n

Bind DN<\/strong>
\nuid=keycloak-svc,cn=users,cn=accounts,dc=example,dc=org<\/code><\/p>\n

Bind Credential<\/strong>
\n<password><\/code><\/p>\n

Dovoli Kerberos avtorizacijo:<\/strong>
\non<\/code><\/p>\n

Kerberos Realm:<\/strong>
\nEXAMPLE.ORG<\/code><\/p>\n

Server Principal:<\/strong>
\nHTTP\/freeipa.example.org@EXAMPLE.ORG<\/code><\/p>\n

KeyTab:<\/strong>
\n\/etc\/krb5.keytab<\/code><\/p>\n

<\/p>\n

Uporabnika keycloak-svc<\/code> treba ustvariti vnaprej na na\u0161em LDAP stre\u017eniku.<\/p>\n

<\/p>\n

V primeru Active Directory je dovolj, da preprosto izberete Vendor: Active Directory<\/strong> in potrebne nastavitve se samodejno vstavijo v obrazec.<\/p>\n

<\/p>\n

Kliknite Shrani<\/strong><\/p>\n

<\/p>\n

Zdaj preidemo na:<\/p>\n

<\/p>\n

User federation<\/strong> \u2192 freeipa.example.org<\/strong> \u2192 Mappers<\/strong> \u2192 Ime<\/strong><\/p>\n

<\/p>\n

Option
\nVrednost<\/p>\n

Ldap attribure<\/strong>
\ngivenName<\/code><\/p>\n

<\/p>\n

Sedaj vklju\u010dimo skupinsko preslikavo:<\/p>\n

<\/p>\n

User federation<\/strong> \u2192 freeipa.example.org<\/strong> \u2192 Mappers<\/strong> \u2192 Stworzy\u0107<\/strong><\/p>\n

<\/p>\n

Option
\nVrednost<\/p>\n

Ime<\/strong>
\ngroups<\/code><\/p>\n

Vrsta mapperja<\/strong>
\ngroup-ldap-mapper<\/code><\/p>\n

LDAP skupine DN<\/strong>
\ncn=groups,cn=accounts,dc=example,dc=org<\/code><\/p>\n

Strategija pridobivanja uporabni\u0161kih skupin<\/strong>
\nGET_GROUPS_FROM_USER_MEMBEROF_ATTRIBUTE<\/code><\/p>\n

<\/p>\n

S tem je nastavitev federacije zaklju\u010dena, preidemo na nastavitev odjemalca.<\/p>\n

<\/p>\n

Nastavitev stranke<\/h2>\n

<\/p>\n

Ustvarimo novega odjemalca (aplikacija, ki bo pridobivala uporabnike iz Keycloak-a). Preidemo na:<\/p>\n

<\/p>\n

Odjemalci<\/strong> \u2192 Stworzy\u0107<\/strong><\/p>\n

<\/p>\n

Option
\nVrednost<\/p>\n

Client ID<\/strong>
\nkubernetes<\/code><\/p>\n

Vrsta dostopa<\/strong>
\nzaupno<\/code><\/p>\n

Koren URL<\/strong>
\nhttp:\/\/kubernetes.example.org\/<\/code><\/p>\n

Veljavne preusmeritvene URI<\/strong>
\nhttp:\/\/kubernetes.example.org\/*<\/code><\/p>\n

URL skrbnika<\/strong>
\nhttp:\/\/kubernetes.example.org\/<\/code><\/p>\n

<\/p>\n

Prav tako bomo ustvarili obseg za skupine:<\/p>\n

<\/p>\n

Obsegi odjemalca<\/strong> \u2192 Stworzy\u0107<\/strong><\/p>\n

<\/p>\n

Option
\nVrednost<\/p>\n

Template<\/strong>
\nBrez predloge<\/code><\/p>\n

Ime<\/strong>
\ngroups<\/code><\/p>\n

Polna pot skupine<\/strong>
\nfalse<\/code><\/p>\n

<\/p>\n

In nastavimo mappers zanje:<\/p>\n

<\/p>\n

Obsegi odjemalca<\/strong> \u2192 groups<\/strong> \u2192 Mappers<\/strong> \u2192 Stworzy\u0107<\/strong><\/p>\n

<\/p>\n

Option
\nVrednost<\/p>\n

Ime<\/strong>
\ngroups<\/code><\/p>\n

Vrsta mapperja<\/strong>
\n\u010clanstvo v skupini<\/code><\/p>\n

Ime zahteve \u017eetona<\/strong>
\ngroups<\/code><\/p>\n

<\/p>\n

Sedaj moramo vklju\u010diti preslikavo skupin v na\u0161em obsegu odjemalca:<\/p>\n

<\/p>\n

Odjemalci<\/strong> \u2192 kubernetes<\/strong> \u2192 Obsegi odjemalca<\/strong> \u2192 Privzeti obsegi odjemalca<\/strong><\/p>\n

<\/p>\n

Izbiramo groups<\/strong> u Na voljo Client Scopes<\/strong>, kliknite Dodaj izbrano<\/strong><\/p>\n

<\/p>\n

Sedaj bomo nastavili avtentikacijo na\u0161e aplikacije, preidemo na:<\/p>\n

<\/p>\n

Odjemalci<\/strong> \u2192 kubernetes<\/strong><\/p>\n

<\/p>\n

Option
\nVrednost<\/p>\n

Avtorizacija omogo\u010dena<\/strong>
\nVKLJU\u010cENO<\/code><\/p>\n

<\/p>\n

Kliknite save<\/strong> in s tem je nastavitev odjemalca zaklju\u010dena, zdaj na zavihku<\/p>\n

<\/p>\n

Odjemalci<\/strong> \u2192 kubernetes<\/strong> \u2192 Zahteve<\/strong><\/p>\n

<\/p>\n

boste lahko pridobili Tajni<\/strong> ki ga bomo uporabili naprej.<\/p>\n

<\/p>\n

Nastavitev Kubernetes<\/h2>\n

<\/p>\n

Nastavitev Kubernetes za OIDC-avtorizacijo je precej enostavna in ni zelo zapletena. Vse, kar potrebujete, je, da nalo\u017eite CA-certifikat va\u0161ega OIDC stre\u017enika v \/etc\/kubernetes\/pki\/oidc-ca.pem<\/code> in dodate potrebne mo\u017enosti za kube-apiserver.
\nZato posodobite \/etc\/kubernetes\/manifests\/kube-apiserver.yaml<\/code> na vseh va\u0161ih masterih:<\/p>\n

<\/p>\n

...\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>\n
Prav tako posodobite kubeadm konfiguracijo v klasterju, da ne izgubite teh nastavitev pri posodobitvah:<\/p>\n
<\/p>\n
kubectl edit -n kube-system configmaps kubeadm-config<\/code><\/pre>\n
<\/p>\n
...\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>\n
S tem je nastavitev Kubernetes zaklju\u010dena. Te iste korake lahko ponovite v vseh va\u0161ih Kubernetes klasterjih.<\/p>\n
<\/p>\n
Za\u010detna avtentikacija<\/h2>\n
<\/p>\n
Po teh korakih boste imeli Kubernetes klaster z nastavljeno OIDC-avtorizacijo. Edina zadeva je, da va\u0161i uporabniki trenutno nimajo nastavljene stranke, prav tako niti svojega kubeconfig. Da bi to te\u017eavo re\u0161ili, je treba nastaviti samodejno izdajo kubeconfiga uporabnikom po uspe\u0161ni avtentikaciji.<\/p>\n
<\/p>\n
Za to lahko uporabite posebne spletne aplikacije, ki omogo\u010dajo avtentikacijo uporabnika in nato prenos pripravljenega kubeconfiga. Ena izmed najbolj priro\u010dnih je Kuberos<\/a><\/noindex>, ki omogo\u010da opis vseh Kubernetes klasterjev v eni konfiguraciji in enostavno preklapljanje med njimi.<\/p>\n
<\/p>\n
Za nastavitev Kuberos je dovolj, da opi\u0161ete predlogo za kubeconfig in za\u017eenete z naslednjimi parametri:<\/p>\n
<\/p>\n
kuberos https:\/\/keycloak.example.org\/auth\/realms\/kubernetes kubernetes \/cfg\/secret \/cfg\/template<\/code><\/pre>\n
<\/p>\n
Za podrobnej\u0161e informacije si oglejte Usage<\/a><\/noindex> na Githubu.<\/p>\n
<\/p>\n
Prav tako je mogo\u010de uporabiti kubelogin<\/a><\/noindex> \u010de \u017eelite izvesti avtentikacijo neposredno na uporabnikovem ra\u010dunalniku. V tem primeru se bo uporabniku odprl brskalnik s prijavno formo na localhost.<\/p>\n
<\/p>\n
Prejeti kubeconfig lahko preverite na spletni strani jwt.io<\/a><\/noindex>. Preprosto kopirajte vrednost users[].user.auth-provider.config.id-token<\/code> iz va\u0161ega kubeconfiga v obrazec na spletu in takoj prejmite razlago.<\/p>\n
<\/p>\n
Nastavitev RBAC<\/h2>\n
<\/p>\n
Pri nastavitvi RBAC se lahko sklicujete tako na uporabni\u0161ko ime (polje name<\/code> v jwt-tokenu), kot tudi na skupino uporabnikov (polje groups<\/code> v jwt-tokenu). Tukaj je primer nastavitve pravic za skupino kubernetes-default-namespace-admins<\/code>:<\/p>\n
\nkubernetes-default-namespace-admins.yaml<\/b><\/p>\n
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>\n
Ve\u010d primerov za RBAC lahko najdete v slu\u017ebene dokumentacije Kubernetes-a<\/a><\/noindex><\/p>\n
<\/p>\n
\u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 auth-proxy<\/h2>\n
<\/p>\n
Obstaja odli\u010den projekt keycloak-gatekeeper<\/a><\/noindex>, ki omogo\u010da za\u0161\u010dito katere koli aplikacije, tako da uporabniku omogo\u010di avtentikacijo na OIDC-stre\u017eniku. Poka\u017eem vam, kako ga nastaviti na primeru Kubernetes Dashboard:<\/p>\n
\ndashboard-proxy.yaml<\/b><\/p>\n
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
Izvor: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\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 […]<\/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\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Povezovanje LDAP-avtentikacije s Kubernetesom | ProHoster","description":"Kratka navodila o tem, kako.","canonical_url":"https:\/\/prohoster.info\/sl\/blog\/administrirovanie\/prikruchivaem-ldap-avtorizacziyu-k-kubernetes","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sl_SI","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\/sl\/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\/sl\/wp-json\/wp\/v2\/posts\/70867","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/comments?post=70867"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts\/70867\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/media\/70868"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/media?parent=70867"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/categories?post=70867"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/tags?post=70867"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}