{"id":36872,"date":"2019-10-31T22:14:26","date_gmt":"2019-10-31T19:14:26","guid":{"rendered":"https:\/\/prohoster.info\/blog\/go-to-2fa-dvuhfaktornaya-autentifikatsiya-dlya-asa-ssl-vpn\/"},"modified":"2019-10-31T22:14:26","modified_gmt":"2019-10-31T19:14:26","slug":"go-to-2fa-dvuhfaktornaya-autentifikatsiya-dlya-asa-ssl-vpn","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/go-to-2fa-dvuhfaktornaya-autentifikatsiya-dlya-asa-ssl-vpn","title":{"rendered":"Accesa\u021bi 2FA (Autentificare dubl\u0103 pentru ASA SSL VPN)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Necesitatea de a oferi acces de la distan\u021b\u0103 la medii corporative devine din ce \u00een ce mai frecvent\u0103, indiferent dac\u0103 sunt utilizatori proprii sau parteneri care au nevoie de acces la anumite servere din organiza\u021bia dumneavoastr\u0103.<\/p>\n

Pentru aceste scopuri, majoritatea companiilor folosesc tehnologia VPN, recunoscut\u0103 ca o modalitate de acces bine securizat\u0103 la resursele locale ale organiza\u021biei.<\/p>\n

Compania mea nu a fost o excep\u021bie \u0219i utiliz\u0103m, la fel ca multe altele, aceast\u0103 tehnologie. \u0218i, ca mul\u021bi al\u021bii, folosim ca poart\u0103 de acces de la distan\u021b\u0103 Cisco ASA 55xx.<\/p>\n

Odat\u0103 cu cre\u0219terea num\u0103rului de utilizatori de la distan\u021b\u0103, apare necesitatea de a simplifica procedura de emitere a credentialelor. Dar, \u00een acela\u0219i timp, trebuie s\u0103 facem acest lucru f\u0103r\u0103 a compromite securitatea.<\/p>\n

Pentru noi, am g\u0103sit o solu\u021bie \u00een aplicarea autentific\u0103rii \u00een dou\u0103 etape pentru conexiunea prin Cisco SSL VPN<\/a>, utiliz\u00e2nd parole de unic\u0103 folosin\u021b\u0103. \u0218i aceast\u0103 publica\u021bie va explica cum s\u0103 organiza\u021bi o astfel de solu\u021bie cu un minim de consum de timp \u0219i cu costuri zero pentru software-ul necesar (sub condi\u021bia c\u0103 Cisco ASA este deja \u00een infrastructura dumneavoastr\u0103).<\/p>\n

Pia\u021ba este plin\u0103 de solu\u021bii standard pentru generarea parolelor de unic\u0103 folosin\u021b\u0103, oferind o mul\u021bime de op\u021biuni pentru ob\u021binerea acestora, fie c\u0103 este vorba de trimiterea parolei prin SMS sau utilizarea token-urilor, fie ele hardware sau software (de exemplu, pe telefonul mobil). \u00cens\u0103 dorin\u021ba de economisire \u0219i de a salva bani pentru angajatorul meu, \u00een condi\u021biile actualei crize, m-a determinat s\u0103 g\u0103sesc o modalitate gratuit\u0103 de a implementa un serviciu pentru generarea parolelor de unic\u0103 folosin\u021b\u0103. Care, av\u00e2nd \u00een vedere gratuitatea sa, se compar\u0103 bine cu solu\u021biile comerciale (este de men\u021bionat c\u0103 acest produs are \u0219i o versiune comercial\u0103, dar am convenit c\u0103 cheltuielile, \u00een bani, vor fi nule).
\n<\/a><\/noindex>
\nA\u0219adar, avem nevoie de:<\/p>\n

\u2014 O imagine Linux cu un set de instrumente \u00eencorporat \u2014 multiOTP, FreeRADIUS \u0219i nginx, pentru accesul la server prin web (http:\/\/download.multiotp.net\/ \u2014 am folosit o imagine gata f\u0103cut\u0103 pentru VMware)
\n \u2014 Un server Active Directory
\n \u2014 Cisco ASA, (eu, pentru comoditate, folosesc ASDM)
\n \u2014 Orice token software care suport\u0103 mecanismul TOTP (Eu, de exemplu, folosesc Google Authenticator, dar FreeOTP este de asemenea potrivit)<\/p>\n

Nu voi detalia procesul de desf\u0103\u0219urare a imaginii. La final ve\u021bi ob\u021bine Debian Linux cu multiOTP \u0219i FreeRADIUS deja instalate, configurate pentru a func\u021biona \u00eempreun\u0103 \u0219i o interfa\u021b\u0103 web pentru administrarea OTP.<\/p>\n

Pasul 1. Ini\u021biem sistemul \u0219i \u00eel configur\u0103m pentru re\u021beaua noastr\u0103<\/b>
\nImplicit, sistemul vine cu acreditivele root root. Cred c\u0103 toat\u0103 lumea a realizat c\u0103 ar fi bine s\u0103 schimbe parola utilizatorului root dup\u0103 prima autentificare. De asemenea, este necesar s\u0103 se schimbe set\u0103rile de re\u021bea (implicit este '192.168.1.44' cu gateway-ul '192.168.1.1'). Dup\u0103, se poate reporni sistemul.<\/p>\n

\u00cen Active Directory vom crea un utilizator otp<\/b>, cu parola MySuperPassword<\/b>.<\/p>\n

Pasul 2. Configur\u0103m conexiunea \u0219i import\u0103m utilizatorii din Active Directory<\/b>
\nPentru aceasta, avem nevoie de acces la consol\u0103 \u0219i, \u00een mod direct, de fi\u0219ierul multiotp.php<\/b>, folosind care vom configura parametrii de conectare la Active Directory.<\/p>\n

Trecem \u00een directorul \/usr\/local\/bin\/multiotp\/<\/i> \u0219i execut\u0103m urm\u0103toarele comenzi pe r\u00e2nd:<\/p>\n

.\\\/multiotp.php -config default-request-prefix-pin=0<\/code><\/pre>\n
\nDefinirea necesit\u0103\u021bii unui PIN suplimentar (permanent) la introducerea PIN-ului unic (0 sau 1)<\/p>\n
.\\\/multiotp.php -config default-request-ldap-pwd=0<\/code><\/pre>\n
\nDefinirea necesit\u0103\u021bii introducerii parolei de domeniu la introducerea PIN-ului unic (0 sau 1)<\/p>\n
.\\\/multiotp.php -config ldap-server-type=1<\/code><\/pre>\n
\nDefinirea tipului de server LDAP (0 = server LDAP obi\u0219nuit, \u00een cazul nostru 1 = Active Directory)<\/p>\n
.\\\/multiotp.php -config ldap-cn-identifier=\"sAMAccountName\"<\/code><\/pre>\n
\nDefinirea formatului \u00een care se va reprezenta numele utilizatorului (aceast\u0103 valoare va afi\u0219a doar numele, f\u0103r\u0103 domeniu)<\/p>\n
.\\\/multiotp.php -config ldap-group-cn-identifier=\"sAMAccountName\"<\/code><\/pre>\n
\nAcela\u0219i lucru, dar pentru grup<\/p>\n
.\\\/multiotp.php -config ldap-group-attribute=\"memberOf\"<\/code><\/pre>\n
\nDefinirea metodei de determinare a apartenen\u021bei utilizatorului la grup<\/p>\n
.\\\/multiotp.php -config ldap-ssl=1<\/code><\/pre>\n
\nFolosirea unei conexiuni securizate la serverul LDAP (cu siguran\u021b\u0103 \u2014 da!)<\/p>\n
.\\\/multiotp.php -config ldap-port=636<\/code><\/pre>\n
\nPortul pentru conectarea la serverul LDAP<\/p>\n
.\\\/multiotp.php -config ldap-domain-controllers=adSRV.domain.local<\/code><\/pre>\n
\nAdresa serverului dumneavoastr\u0103 Active Directory<\/p>\n
.\\\/multiotp.php -config ldap-base-dn=\"CN=Users,DC=domain,DC=local\"<\/code><\/pre>\n
\nDefinirea punctului de unde s\u0103 \u00eencepem c\u0103utarea utilizatorilor \u00een domeniu<\/p>\n
.\\\/multiotp.php -config ldap-bind-dn=\"otp@domain.local\"<\/code><\/pre>\n
\nDefinirea utilizatorului care are drepturi de c\u0103utare \u00een Active Directory<\/p>\n
.\\\/multiotp.php -config ldap-server-password=\"MySuperPassword\"<\/code><\/pre>\n
\nDefinirea parolei utilizatorului pentru conectarea la Active Directory<\/p>\n
.\\\/multiotp.php -config ldap-network-timeout=10<\/code><\/pre>\n
\nStabilirea timeout-ului pentru conectarea la Active Directory<\/p>\n
.\\\/multiotp.php -config ldap-time-limit=30<\/code><\/pre>\n
\nStabilirea limitei de timp pentru opera\u021biunea de import a utilizatorilor<\/p>\n
.\\\/multiotp.php -config ldap-activated=1<\/code><\/pre>\n
\nActiv\u0103m configura\u021bia de conectare la Active Directory<\/p>\n
.\\\/multiotp.php -debug -display-log -ldap-users-sync<\/code><\/pre>\n
\nImport\u0103m utilizatorii din Active Directory<\/p>\n
Pasul 3. Gener\u0103m codul QR pentru token<\/b>
\nAici totul este extrem de simplu. Deschidem interfa\u021ba web a serverului OTP \u00een browser, ne autentific\u0103m (nu uita\u021bi s\u0103 schimba\u021bi parola pentru admin, setat\u0103 implicit!), \u0219i ap\u0103s\u0103m pe butonul \u201ePrint\u201d:<\/p>\n
\"Accesa\u021bi
\nRezultatul acestei ac\u021biuni va fi o pagin\u0103 care con\u021bine dou\u0103 coduri QR. Putem ignora primul dintre ele (\u00een ciuda mesajului atr\u0103g\u0103tor Google Authenticator \\\/ Authenticator \\\/ 2 Steps Authenticator), \u0219i, din nou, putem scana al doilea cod \u00een tokenul software de pe telefon:<\/p>\n
\"Accesa\u021bi
\n(da, am stricat inten\u021bionat codul QR pentru a-l face ilizibil).<\/p>\n
Dup\u0103 ce a\u021bi finalizat aceste ac\u021biuni, aplica\u021bia dumneavoastr\u0103 va genera un cod de \u0219ase cifre la fiecare treizeci de secunde.<\/p>\n
Pentru siguran\u021b\u0103, putem efectua o verificare, \u00een aceea\u0219i interfa\u021b\u0103:<\/p>\n
\"Accesa\u021bi
\nIntroduc\u00e2nd numele utilizatorului \u0219i codul unic din aplica\u021bia de pe telefon. Am primit un r\u0103spuns pozitiv? Atunci continu\u0103m.<\/p>\n
Pasul 4. Finaliz\u0103m \u0219i test\u0103m func\u021bionarea FreeRADIUS<\/b>
\nA\u0219a cum am men\u021bionat mai sus \u2014 multiOTP este deja configurat pentru a func\u021biona cu FreeRADIUS, r\u0103m\u00e2ne s\u0103 facem teste \u0219i s\u0103 introducem \u00een fi\u0219ierul de configurare FreeRADIUS informa\u021biile despre gateway-ul nostru VPN.<\/p>\n
Ne \u00eentoarcem la consola serverului, \u00een directorul \/usr\/local\/bin\/multiotp\/<\/i>, introducem:<\/p>\n
.\\\/multiotp.php -config debug=1\\n.\\\/multiotp.php -config display-log=1<\/code><\/pre>\n
\nActiv\u00e2nd astfel o jurnalizare mai detaliat\u0103.<\/p>\n
\u00cen fi\u0219ierul de configurare al clien\u021bilor FreeRADIUS (\/etc\/freeradius\/clinets.conf<\/i>) coment\u0103m toate liniile referitoare la localhost<\/b> \u0219i ad\u0103ug\u0103m dou\u0103 \u00eenregistr\u0103ri:<\/p>\n
client localhost {\\n        ipaddr = 127.0.0.1\\n        secret          = testing321\\n        require_message_authenticator = no\\n}<\/code><\/pre>\n
\n \u2014 pentru test<\/p>\n
client 192.168.1.254\\\/32 {\\n        shortname =     CiscoASA\\n        secret =        ConnectToRADIUSSecret\\n}<\/code><\/pre>\n
\n \u2014 pentru gateway-ul nostru VPN.<\/p>\n
Repornim FreeRADIUS \u0219i \u00eencerc\u0103m s\u0103 ne autoriz\u0103m:<\/p>\n
radtest username 100110 localhost 1812 testing321<\/code><\/pre>\n
\nunde username <\/i>= numele utilizatorului, 100110 <\/i>= parola, oferit\u0103 de aplica\u021bia de pe telefon, localhost <\/i>= adresa serverului RADIUS, 1812 <\/i> \u2014 portul serverului RADIUS, testing321 <\/i> \u2014 parola clientului serverului RADIUS (pe care am specificat-o \u00een config).<\/p>\n
Rezultatul acestei comenzi va fi un output de aproximativ urm\u0103torul con\u021binut:<\/p>\n
Trimitere Access-Request cu id 44 c\u0103tre 127.0.0.1 port 1812\n        User-Name = \"username\"\n        User-Password = \"100110\"\n        NAS-IP-Address = 127.0.1.1\n        NAS-Port = 1812\n        Message-Authenticator = 0x00000000000000000000000000000000\nrad_recv: pachet Access-Accept de la gazd\u0103 127.0.0.1 port 1812, id=44, lungime=20<\/code><\/pre>\n
\nAcum trebuie s\u0103 ne asigur\u0103m c\u0103 utilizatorul a trecut cu succes de autentificare. Pentru aceasta, vom verifica logul multiotp:<\/p>\n
tail \/var\/log\/multiotp\/multiotp.log<\/code><\/pre>\n
\n\u0218i dac\u0103 ultima \u00eenregistrare de acolo va fi:<\/p>\n
2016-09-01 08:58:17     notice  username  User    OK: Utilizatorul username s-a autentificat cu succes din 127.0.0.1\n2016-09-01 08:58:17     debug           Debug   Debug: 0 OK: Token acceptat din 127.0.0.1<\/code><\/pre>\n
\nAtunci totul a decurs cu succes \u0219i putem continua cu<\/p>\n
Pasul 5. Configurarea Cisco ASA<\/b>
\nS\u0103 presupunem c\u0103 avem deja un grup \u0219i politici configurate pentru accesul prin SLL VPN, setate \u00een leg\u0103tur\u0103 cu Active Directory, \u0219i trebuie s\u0103 ad\u0103ug\u0103m autentificarea cu doi factori pentru acest profil.<\/p>\n
1.<\/strong> Ad\u0103ug\u0103m un nou grup servere<\/a> AAA:<\/p>\n
\"Accesa\u021bi
\n2.<\/strong> Ad\u0103ug\u0103m serverul nostru multiOTP \u00een grup:<\/p>\n
\"Accesa\u021bi
\n3.<\/strong> Corect\u0103m profilul de conectare<\/b>, stabilind ca server principal de autentificare grupul de servere Active Directory:<\/p>\n
\"Accesa\u021bi
\n4.<\/strong> Pe tab-ul Advanced -> Authentification<\/b> de asemenea, alegem grupul de servere Active Directory:<\/p>\n
\"Accesa\u021bi
\n5.<\/strong> Pe tab-ul Advanced -> Secondary<\/b> pentru autentificare alegem grupul de servere creat, \u00een care este inclus serverul multiOTP. Men\u021bion\u0103m c\u0103 Session username este derivate din grupul principal de servere AAA:<\/p>\n
\"Accesa\u021bi
\nAplic\u0103m set\u0103rile \u0219i<\/p>\n
Pasul 6, ultimul<\/b>
\nVerific\u0103m dac\u0103 autentificarea cu doi factori func\u021bioneaz\u0103 pentru SLL VPN:<\/p>\n
\"Accesa\u021bi
\nVoila! Atunci c\u00e2nd ne conect\u0103m prin Cisco AnyConnect VPN Client, va fi solicitat\u0103 \u0219i a doua parol\u0103, unic\u0103.<\/p>\n
Sper c\u0103 acest articol va ajuta pe cineva \u0219i c\u0103 va oferi cuiva inspira\u021bie despre cum poate fi utilizat acest gratuit<\/b> server OTP pentru alte sarcini. V\u0103 rug\u0103m s\u0103 \u00eemp\u0103rt\u0103\u0219i\u021bi \u00een comentarii dac\u0103 dori\u021bi.
\n
Sursa: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u041f\u043e\u0442\u0440\u0435\u0431\u043d\u043e\u0441\u0442\u044c \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0442\u0438\u0432\u043d\u043e\u0439 \u0441\u0440\u0435\u0434\u0435 \u0432\u043e\u0437\u043d\u0438\u043a\u0430\u0435\u0442 \u0432\u0441\u0435 \u0447\u0430\u0449\u0435 \u0438 \u0447\u0430\u0449\u0435, \u043d\u0435 \u0432\u0430\u0436\u043d\u043e, \u0431\u0443\u0434\u044c \u0442\u043e \u0441\u0432\u043e\u0438 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0438\u043b\u0438 \u043f\u0430\u0440\u0442\u043d\u0435\u0440\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u043c \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u0442\u043e\u043c\u0443 \u0438\u043b\u0438 \u0438\u043d\u043e\u043c\u0443 \u0441\u0435\u0440\u0432\u0435\u0440\u0443 \u0432 \u0432\u0430\u0448\u0435\u0439 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0438. \u0414\u043b\u044f \u044d\u0442\u0438\u0445 \u0446\u0435\u043b\u0435\u0439, \u0431\u043e\u043b\u044c\u0448\u0438\u043d\u0441\u0442\u0432\u043e \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0439, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0442 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u044e VPN, \u0437\u0430\u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u043e\u0432\u0430\u0432\u0448\u0443\u044e \u0441\u0435\u0431\u044f, \u043a\u0430\u043a \u043d\u0430\u0434\u0435\u0436\u043d\u043e \u0437\u0430\u0449\u0438\u0449\u0435\u043d\u043d\u044b\u0439 \u0441\u043f\u043e\u0441\u043e\u0431 \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u044b\u043c \u0440\u0435\u0441\u0443\u0440\u0441\u0430\u043c \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0438. \u041c\u043e\u044f \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u044f \u043d\u0435 \u0441\u0442\u0430\u043b\u0430 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27626,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-36872","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\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\udd47Merge\u021bi la 2FA (Autentificare cu doi factori pentru ASA SSL VPN) | ProHoster","description":"Nevoia de a oferi acces la distan\u021b\u0103 la medii corporative apare din ce \u00een ce mai frecvent, fie c\u0103 este vorba de utilizatorii proprii sau de partenerii care au nevoie de acces la un anumit server din organiza\u021bia dvs.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/go-to-2fa-dvuhfaktornaya-autentifikatsiya-dlya-asa-ssl-vpn","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\udd47Go to 2FA (\u0414\u0432\u0443\u0445\u0444\u0430\u043a\u0442\u043e\u0440\u043d\u0430\u044f \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044f \u0434\u043b\u044f ASA SSL VPN) | ProHoster","og:description":"\u041f\u043e\u0442\u0440\u0435\u0431\u043d\u043e\u0441\u0442\u044c \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u0439 \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0442\u0438\u0432\u043d\u043e\u0439 \u0441\u0440\u0435\u0434\u0435 \u0432\u043e\u0437\u043d\u0438\u043a\u0430\u0435\u0442 \u0432\u0441\u0435 \u0447\u0430\u0449\u0435 \u0438 \u0447\u0430\u0449\u0435, \u043d\u0435 \u0432\u0430\u0436\u043d\u043e, \u0431\u0443\u0434\u044c \u0442\u043e \u0441\u0432\u043e\u0438 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0438\u043b\u0438 \u043f\u0430\u0440\u0442\u043d\u0435\u0440\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u043c \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c \u0434\u043e\u0441\u0442\u0443\u043f \u043a \u0442\u043e\u043c\u0443 \u0438\u043b\u0438 \u0438\u043d\u043e\u043c\u0443 \u0441\u0435\u0440\u0432\u0435\u0440\u0443 \u0432 \u0432\u0430\u0448\u0435\u0439 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0438..","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/go-to-2fa-dvuhfaktornaya-autentifikatsiya-dlya-asa-ssl-vpn","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":"2019-10-31T19:14:26+00:00","article:modified_time":"2019-10-31T19:14:26+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"36872","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":"2026-02-09 17:05:56","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:37:23","updated":"2026-02-09 17:05:56","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/36872","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=36872"}],"version-history":[{"count":2,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/36872\/revisions"}],"predecessor-version":[{"id":158589,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/36872\/revisions\/158589"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/27626"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=36872"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=36872"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=36872"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}