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

\"Integrerer<\/p>\n

<\/p>\n

En kort vejledning til, hvordan du kan forbinde Kubernetes med din LDAP-server ved hj\u00e6lp af Keycloak og konfigurere import af brugere og grupper. Dette vil g\u00f8re det muligt at konfigurere RBAC for dine brugere og bruge auth-proxy til at beskytte Kubernetes Dashboard og andre applikationer, der ikke kan autentificere sig selv.<\/p>\n

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

Installation af Keycloak<\/h2>\n

<\/p>\n

Lad os antage, at du allerede har en LDAP-server. Det kan v\u00e6re Active Directory, FreeIPA, OpenLDAP eller noget andet. Hvis du ikke har en LDAP-server, kan du grundl\u00e6ggende oprette brugere direkte i Keycloak-interfacet eller bruge offentlige oidc-udbydere (Google, Github, Gitlab), resultatet vil blive n\u00e6sten det samme.<\/p>\n

<\/p>\n

F\u00f8rst skal vi installere selve Keycloak; installationen kan udf\u00f8res separat eller direkte i Kubernetes-klyngen. Hvis du har flere Kubernetes-klynger, vil det typisk v\u00e6re lettere at installere det separat. P\u00e5 den anden side kan du altid bruge den officielle helm-chart<\/a><\/noindex> og installere den direkte i din klynge.<\/p>\n

<\/p>\n

For at gemme data i Keycloak har du brug for en database. Som standard bruges h2<\/code> (alle data gemmes lokalt), men det er ogs\u00e5 muligt at bruge postgres<\/code>, mysql<\/code> eller mariadb<\/code>.
\nHvis du alligevel har besluttet at installere Keycloak separat, finder du mere detaljerede instruktioner i den officielle dokumentation<\/a><\/noindex>.<\/p>\n

<\/p>\n

Konfiguration af federation<\/h2>\n

<\/p>\n

F\u00f8rst opretter vi et nyt realm. Et realm er et rum for vores applikation. Hver applikation kan have sit eget realm med forskellige brugere og autentifikationsindstillinger. Master realm bruges af Keycloak selv, og det er forkert at bruge det til andet.<\/p>\n

<\/p>\n

Klik p\u00e5 Tilf\u00f8j realm<\/strong><\/p>\n

<\/p>\n

Mulighed
\nV\u00e6rdi<\/p>\n

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

Visningsnavn<\/strong>
\nKubernetes<\/code><\/p>\n

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

<\/p>\n

Kubernetes tjekker som standard, om en brugers e-mail er bekr\u00e6ftet eller ej. Da vi bruger vores egen LDAP-server, vil denne kontrol n\u00e6sten altid returnere false<\/code>. Lad os deaktivere visningen af denne parameter i Kubernetes:<\/p>\n

<\/p>\n

Klientomfang<\/strong> \u2192 E-mail<\/strong> \u2192 Mapper<\/strong> \u2192 E-mail bekr\u00e6ftet<\/strong> (Slet)<\/p>\n

<\/p>\n

Nu konfigurerer vi federation, for dette g\u00e5r vi til:<\/p>\n

<\/p>\n

Brugerfederation<\/strong> \u2192 Tilf\u00f8j udbyder\u2026<\/strong> \u2192 ldap<\/strong><\/p>\n

<\/p>\n

Her er et eksempel p\u00e5 konfiguration for FreeIPA:<\/p>\n

<\/p>\n

Mulighed
\nV\u00e6rdi<\/p>\n

Konsol Visningsnavn<\/strong>
\nfreeipa.example.org<\/code><\/p>\n

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

UUID LDAP-attribut<\/strong>
\nipauniqueid<\/code><\/p>\n

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

Brugere 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

Tillad Kerberos autentifikation:<\/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

Brugeren keycloak-svc<\/code> skal oprettes p\u00e5 forh\u00e5nd p\u00e5 vores LDAP-server.<\/p>\n

<\/p>\n

I tilf\u00e6lde af Active Directory er det tilstr\u00e6kkeligt blot at v\u00e6lge Leverand\u00f8r: Active Directory<\/strong> og de n\u00f8dvendige indstillinger vil automatisk blive indsat i formen.<\/p>\n

<\/p>\n

Klik p\u00e5 Gem<\/strong><\/p>\n

<\/p>\n

Nu g\u00e5r vi videre til:<\/p>\n

<\/p>\n

Brugerfederation<\/strong> \u2192 freeipa.example.org<\/strong> \u2192 Mapper<\/strong> \u2192 Fornavn<\/strong><\/p>\n

<\/p>\n

Mulighed
\nV\u00e6rdi<\/p>\n

LDAP-attribut<\/strong>
\ngivenName<\/code><\/p>\n

<\/p>\n

Lad os nu aktivere gruppe-mapping:<\/p>\n

<\/p>\n

Brugerfederation<\/strong> \u2192 freeipa.example.org<\/strong> \u2192 Mapper<\/strong> \u2192 Opret<\/strong><\/p>\n

<\/p>\n

Mulighed
\nV\u00e6rdi<\/p>\n

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

Mapper type<\/strong>
\ngroup-ldap-mapper<\/code><\/p>\n

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

Brugergrupper Hentningsstrategi<\/strong>
\nGET_GROUPS_FROM_USER_MEMBEROF_ATTRIBUTE<\/code><\/p>\n

<\/p>\n

Nu er konfigurationen af federation afsluttet, lad os g\u00e5 videre til klientkonfigurationen.<\/p>\n

<\/p>\n

Klientkonfiguration<\/h2>\n

<\/p>\n

Vi opretter en ny klient (applikation, der vil hente brugere fra Keycloak). G\u00e5 til:<\/p>\n

<\/p>\n

Klienter<\/strong> \u2192 Opret<\/strong><\/p>\n

<\/p>\n

Mulighed
\nV\u00e6rdi<\/p>\n

Denne ID bruges til at identificere<\/strong>
\nkubernetes<\/code><\/p>\n

Adgangstype<\/strong>
\nconfidenrial<\/code><\/p>\n

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

Gyldige omdirigerings-URIs<\/strong>
\nhttp:\/\/kubernetes.example.org\/*<\/code><\/p>\n

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

<\/p>\n

Vi opretter ogs\u00e5 et scope for grupper:<\/p>\n

<\/p>\n

Klient Scopes<\/strong> \u2192 Opret<\/strong><\/p>\n

<\/p>\n

Mulighed
\nV\u00e6rdi<\/p>\n

Skabelon<\/strong>
\nIngen skabelon<\/code><\/p>\n

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

Fuld gruppevej<\/strong>
\nfalse<\/code><\/p>\n

<\/p>\n

Og vi konfigurerer mapper til dem:<\/p>\n

<\/p>\n

Klient Scopes<\/strong> \u2192 groups<\/strong> \u2192 Mapper<\/strong> \u2192 Opret<\/strong><\/p>\n

<\/p>\n

Mulighed
\nV\u00e6rdi<\/p>\n

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

Mapper Type<\/strong>
\nGruppemedlemskab<\/code><\/p>\n

Token Claim Navn<\/strong>
\ngroups<\/code><\/p>\n

<\/p>\n

Nu skal vi aktivere gruppering i vores klient scope:<\/p>\n

<\/p>\n

Klienter<\/strong> \u2192 kubernetes<\/strong> \u2192 Klient Scopes<\/strong> \u2192 Standard Klient Scopes<\/strong><\/p>\n

<\/p>\n

Vi v\u00e6lger groups<\/strong> i Tilg\u00e6ngelige Client Scopes<\/strong>, klik p\u00e5 Tilf\u00f8j valgte<\/strong><\/p>\n

<\/p>\n

Lad os nu konfigurere godkendelse af vores applikation, g\u00e5 til:<\/p>\n

<\/p>\n

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

<\/p>\n

Mulighed
\nV\u00e6rdi<\/p>\n

Autorisation Aktiveret<\/strong>
\nTIL<\/code><\/p>\n

<\/p>\n

Klik p\u00e5 gem<\/strong> og hermed er oprettelsen af klienten f\u00e6rdig, nu p\u00e5 fanen<\/p>\n

<\/p>\n

Klienter<\/strong> \u2192 kubernetes<\/strong> \u2192 Oplysninger<\/strong><\/p>\n

<\/p>\n

vil du kunne f\u00e5 Secret<\/strong> som vi vil bruge fremadrettet.<\/p>\n

<\/p>\n

Kubernetes konfiguration<\/h2>\n

<\/p>\n

Konfiguration af Kubernetes til OIDC-godkendelse er ganske triviel og ikke s\u00e6rlig kompleks. Alt, hvad du beh\u00f8ver, er at placere CA-certifikatet fra din OIDC-server i \/etc\/kubernetes\/pki\/oidc-ca.pem<\/code> og tilf\u00f8je de n\u00f8dvendige indstillinger til kube-apiserver.
\nFor at g\u00f8re dette, opdater \/etc\/kubernetes\/manifests\/kube-apiserver.yaml<\/code> p\u00e5 alle dine mastere:<\/p>\n

<\/p>\n

...\nspec:\n  containere:\n  - kommando:\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
Opdater ogs\u00e5 kubeadm-konfigurationen i klyngen, s\u00e5 du ikke mister disse indstillinger ved opdatering:<\/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
Nu er konfigurationen af Kubernetes afsluttet. Du kan gentage disse handlinger i alle dine Kubernetes-klynger.<\/p>\n
<\/p>\n
Indledende godkendelse<\/h2>\n
<\/p>\n
Efter disse handlinger vil du have en Kubernetes-klynge med konfigureret OIDC-godkendelse. Den eneste ting er, at dine brugere endnu ikke har konfigureret en klient eller deres egen kubeconfig. For at l\u00f8se dette problem skal du konfigurere automatisk udstedelse af kubeconfig til brugerne efter en succesfuld godkendelse.<\/p>\n
<\/p>\n
Til dette kan du bruge specielle webapplikationer, der muligg\u00f8r brugerautentifikation og derefter muligg\u00f8r download af en klar kubeconfig. En af de mest bekvemme er Kuberos<\/a><\/noindex>, som g\u00f8r det muligt at beskrive alle Kubernetes-klynger i \u00e9n konfigurationsfil og nemt skifte imellem dem.<\/p>\n
<\/p>\n
For at konfigurere Kuberos er det nok at beskrive en skabelon til kubeconfig og starte med f\u00f8lgende parametre:<\/p>\n
<\/p>\n
kuberos https:\/\/keycloak.example.org\/auth\/realms\/kubernetes kubernetes \/cfg\/secret \/cfg\/template<\/code><\/pre>\n
<\/p>\n
For more detailed information, see Brug<\/a><\/noindex> on Github.<\/p>\n
<\/p>\n
It is also possible to use kubelogin<\/a><\/noindex> if you want to perform authentication directly on the user's computer. In this case, a browser will open for the user with an authentication form on localhost.<\/p>\n
<\/p>\n
The obtained kubeconfig can be verified on the site jwt.io<\/a><\/noindex>. Just copy the value users[].user.auth-provider.config.id-token<\/code> from your kubeconfig into the form on the site and immediately get the decryption.<\/p>\n
<\/p>\n
Setting up RBAC<\/h2>\n
<\/p>\n
When configuring RBAC, you can refer to either the username (the field name<\/code> in the jwt token) or to the user group (the field groups<\/code> in the jwt token). Here is an example of rights configuration for the group 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
More examples for RBAC can be found in den officielle dokumentation fra Kubernetes<\/a><\/noindex><\/p>\n
<\/p>\n
Konfiguration af auth-proxy<\/h2>\n
<\/p>\n
There is a wonderful project keycloak-gatekeeper<\/a><\/noindex>, which allows securing any application, giving the user the ability to authenticate on an OIDC server. I will show how to set it up using the example of 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
Kilde: 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\udd47Attaching LDAP authentication to Kubernetes | ProHoster","description":"A brief guide on how to do it.","canonical_url":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/prikruchivaem-ldap-avtorizacziyu-k-kubernetes","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"da_DK","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\/da\/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\/da\/wp-json\/wp\/v2\/posts\/70867","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/comments?post=70867"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts\/70867\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media\/70868"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media?parent=70867"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/categories?post=70867"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/tags?post=70867"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}