{"id":3893,"date":"2021-11-26T13:59:00","date_gmt":"2021-11-26T12:59:00","guid":{"rendered":"https:\/\/blog.besharp.it\/?p=3893"},"modified":"2021-11-26T13:08:21","modified_gmt":"2021-11-26T12:08:21","slug":"federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/","title":{"rendered":"Federazione cross-account tra Amazon Connect e Azure AD con AWS SSO"},"content":{"rendered":"\n<p>Per le aziende \u00e8 diventato molto importante essere in grado di utilizzare differenti canali di comunicazione con i propri clienti, specialmente per fornire loro supporto.&nbsp;<\/p>\n\n\n\n<p>Nel mercato dei servizi di contact center, in cui esistono gi\u00e0 aziende affermate da tempo, Amazon Connect \u00e8 una alternativa interessante da prendere in considerazione: \u00e8 interamente gestito, facilmente&nbsp; scalabile e con un costo competitivorispettoai competitor sul mercato..<\/p>\n\n\n\n<p><a href=\"https:\/\/aws.amazon.com\/connect\/contact-lens\/\" target=\"_blank\" rel=\"noreferrer noopener\">L&#8217;intelligenza artificiale abbinata agli algoritmi di machine learning rende possibile la sentiment analysis<\/a> permettendo al business di ottenere informazioni di valore dai propri utenti.<\/p>\n\n\n\n<p>Ogni cliente ha esigenze differenti che, a volte, ci portano a provare integrazioni tra servizi inusuali e non presenti nelle guide ufficiali.<\/p>\n\n\n\n<p>In questo articolo descriveremo come siamo riusciti a configurazione una federazione cross-account fra Amazon Connect e Azure AD mediante l\u2019uso di AWS SSO.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Use Case<\/h2>\n\n\n\n<p>Per un nostro cliente \u00e8 emersa l\u2019esigenza di configurare Amazon Connect affinch\u00e9 fosse possibile per gli utenti esistenti su Office365, contenuti quindi in una istanza Azure Active Directory, autenticarsi. L\u2019altro requisito era di mantenere il servizio in un account AWS separato, per permettere ad un gruppo ristretto di utenti la gestione di Amazon Connect ed altri servizi.&nbsp;<\/p>\n\n\n\n<p>Amazon Connect permette l\u2019utilizzo di AWS Managed Microsoft AD ma, per realizzare la soluzione, abbiamo sfruttato gli Identity Provider aziendali gi\u00e0 configurati.<\/p>\n\n\n\n<p>La nostra scelta \u00e8 ricaduta quindi su AWS SSO. Oltre ad essere molto flessibile nella configurazione di applicazioni SAML, offre la possibilit\u00e0 di implementare il single-sign-on sugli account AWS.<\/p>\n\n\n\n<p>Come vedremo in questo articolo, Amazon Connect non consente di implementare direttamente l\u2019integrazione nativa con AWS SSO. Dovremo quindi configurare un\u2019applicazione SAML ed usarla come identity provider nell\u2019account di destinazione.<\/p>\n\n\n\n<p>In questo articolo ci occuperemo di:&nbsp;<\/p>\n\n\n\n<ul><li>Configurare AWS SSO nell\u2019account master dell\u2019organizzazione per utilizzare Azure Active Directory (usato da Office365) ed autenticare gli utenti<\/li><li>Attivare una istanza Amazon Connect con autenticazione SAML in un account differente nella stessa organizzazione (chiamato internal-services)<\/li><li>Creare e configurare un&#8217;applicazione SAML per Amazon Connect<\/li><li>Configurare un identity provider nell\u2019account internal-services per autorizzare l\u2019applicazione SAML ed occuparsi dell\u2019autenticazione cross-account<\/li><li>Aggiungere i ruoli richiesti all\u2019account internal-services per autenticare gli utenti federati<\/li><li>Collaudare la configurazione<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Configurazione di AWS SSO<\/h2>\n\n\n\n<p>Per prima cosa occorre effettuare il login all\u2019<a href=\"https:\/\/aad.portal.azure.com\" target=\"_blank\" rel=\"noreferrer noopener\">admin center di Azure Active Directory<\/a> e selezionare \u201cEnterprise Applications\u201d. Fare click su \u201cCreate your own application\u201d e assegnare un nome univoco<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"341\" height=\"335\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image14.jpg\" alt=\"Azure Active Directory admin center\" class=\"wp-image-3866\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image14.jpg 341w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image14-305x300.jpg 305w\" sizes=\"(max-width: 341px) 100vw, 341px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"878\" height=\"276\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image11-1.png\" alt=\"Azure AD Gallery\" class=\"wp-image-3860\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image11-1.png 878w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image11-1-400x126.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image11-1-768x241.png 768w\" sizes=\"(max-width: 878px) 100vw, 878px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"711\" height=\"485\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image21.jpg\" alt=\"create application Azure AD\" class=\"wp-image-3880\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image21.jpg 711w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image21-400x273.jpg 400w\" sizes=\"(max-width: 711px) 100vw, 711px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>In breve tempo l\u2019applicazione sar\u00e0 disponibile. A quel punto sar\u00e0 necessario impostare il <strong>Single sign-on<\/strong>: fare click sul menu e selezionare \u201c<strong>SAML<\/strong>\u201d<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"489\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image6-1024x489.jpg\" alt=\"\" class=\"wp-image-3850\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image6-1024x489.jpg 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image6-400x191.jpg 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image6-768x367.jpg 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image6-1536x733.jpg 1536w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image6.jpg 1999w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"306\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image9-1-1024x306.png\" alt=\"\" class=\"wp-image-3856\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image9-1-1024x306.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image9-1-400x120.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image9-1-768x230.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image9-1.png 1026w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>Fare click sul link \u201c<strong>Federation data XML\u201d <\/strong>&nbsp;e scaricare il file.<br><br>N.B.: il file non dovr\u00e0 essere condiviso e andr\u00e0 mantenuto al sicuro.<\/p>\n\n\n\n<p>A questo punto \u00e8 possibile assegnare gli utenti all\u2019applicazione.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"767\" height=\"427\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image12-1.png\" alt=\"\" class=\"wp-image-3862\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image12-1.png 767w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image12-1-400x223.png 400w\" sizes=\"(max-width: 767px) 100vw, 767px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>Terminata la configurazione dell\u2019applicazione fare login sulla console AWS nell\u2019account di management e selezionare il servizio \u201c<strong>Aws Single Sign on<\/strong>\u201d<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"474\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image19-1024x474.png\" alt=\"\" class=\"wp-image-3876\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image19-1024x474.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image19-400x185.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image19-768x356.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image19-1536x711.png 1536w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image19.png 1548w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>Se AWS SSO \u00e8 gi\u00e0 stato configurato, \u00e8 sempre possibile cambiare l\u2019identity provider in uso sulla pagina \u201cSettings\u201d<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"259\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image3-1-1024x259.png\" alt=\"\" class=\"wp-image-3844\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image3-1-1024x259.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image3-1-400x101.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image3-1-768x194.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image3-1.png 1307w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"930\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image15-1-1024x930.png\" alt=\"\" class=\"wp-image-3868\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image15-1-1024x930.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image15-1-330x300.png 330w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image15-1-768x698.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image15-1.png 1257w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p>Selezionare \u201c<strong>External identity provider\u201d, <\/strong>scaricare il metadata file e, come fatto in precedenza, conservarlo in un luogo sicuro.&nbsp;<\/p>\n\n\n\n<p>A questo punto occorre fare upload del file di metadati scaricato dalla console Azure.<br>Sulla console Azure Active Directory Administration fare click su \u201c<strong>upload metadata file\u201d <\/strong>utilizzando il file scaricato dalla console AWS<\/p>\n\n\n\n<p><\/p>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image7-1.png\" alt=\"\" class=\"wp-image-3852\" width=\"812\" height=\"147\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image7-1.png 812w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image7-1-400x72.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image7-1-768x139.png 768w\" sizes=\"(max-width: 812px) 100vw, 812px\" \/><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p>In questo modo, la configurazione della federazione fra Azure Active Directory e AWS SSO \u00e8 stata portata a termine.&nbsp;<\/p>\n\n\n\n<p>Sulla console Azure \u00e8 possibile provare l\u2019applicazione, simulando un login con le credenziali correnti.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"273\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image17-1024x273.png\" alt=\"\" class=\"wp-image-3872\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image17-1024x273.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image17-400x106.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image17-768x204.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image17-1536x409.png 1536w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image17.png 1999w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>Se sulla console AWS sono state gi\u00e0 assegnate alcune applicazioni sar\u00e0 possibile vederle ed utilizzarle.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"642\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image10-1-1024x642.png\" alt=\"\" class=\"wp-image-3858\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image10-1-1024x642.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image10-1-400x251.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image10-1-768x482.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image10-1.png 1240w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>\u00c8 possibile anche abilitare l\u2019auto provisioning degli utenti ed assegnare gli utenti in modo che siano automaticamente importati su AWS SSO.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Setup di Amazon Connect<\/h2>\n\n\n\n<p>Utilizzeremo un account AWS differente (<strong>internal-services<\/strong>) per configurare Amazon Connect. Utilizzando AWS SSO e Organization saremo in grado di assegnare permessi molto granulari a differenti utenti e ruoli.&nbsp;<\/p>\n\n\n\n<p>Sull\u2019account internal-service alla sezione \u201cAmazon Connect\u201d, fare click su \u201cCreate new instance\u201d.<br>Alla sezione&nbsp; \u201cidentity management\u201d, selezionare&nbsp; \u201c<strong>SAML 2.0-based authentication<\/strong>\u201d. Una volta selezionato il tipo di autenticazione non sar\u00e0 pi\u00f9 possibile modificarlo.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"733\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image5-1-1024x733.png\" alt=\"\" class=\"wp-image-3848\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image5-1-1024x733.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image5-1-400x286.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image5-1-768x550.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image5-1.png 1057w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>A questo punto, nel wizard di configurazione, \u00e8 possibile selezionare le opzioni preferite e procedere con la creazione. Il servizio dopo pochi minuti sar\u00e0 pronto:<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"124\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image13-1-1024x124.png\" alt=\"\" class=\"wp-image-3864\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image13-1-1024x124.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image13-1-400x49.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image13-1-768x93.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image13-1.png 1053w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"420\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image18-1024x420.png\" alt=\"\" class=\"wp-image-3874\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image18-1024x420.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image18-400x164.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image18-768x315.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image18.png 1386w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p><strong>Attenzione<\/strong>: Amazon Connect non supporta il provisioning automatico degli utenti: \u00e8 necessario creare un utente con lo stesso username definito in Azure Active Directory<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Integrazione Con SSO<\/h2>\n\n\n\n<p>Sulla console SSO dell\u2019account di management fare click su \u201cApplications\u201d \u201cAdd a new Application\u201d, ricercando l\u2019applicazione \u201c<strong>Amazon Connect<\/strong>\u201d.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"795\" height=\"1024\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image16-795x1024.png\" alt=\"\" class=\"wp-image-3870\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image16-795x1024.png 795w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image16-233x300.png 233w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image16-768x989.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image16-1193x1536.png 1193w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image16.png 1403w\" sizes=\"(max-width: 795px) 100vw, 795px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>Dopo aver assegnato un nome all\u2019applicazione, fare click su \u201cDownload\u201d alla sezione \u201cAWS SSO SAML metadata file\u201d.<\/p>\n\n\n\n<p>Nell\u2019account <strong>internal-services<\/strong> selezionare il servizio IAM e, alla sezione \u201c<strong>Identity Providers\u201d<\/strong>, fare click su \u201cAdd provider\u201d e fare l\u2019upload del metadata file appena caricato<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"935\" height=\"1024\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image23-935x1024.png\" alt=\"\" class=\"wp-image-3884\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image23-935x1024.png 935w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image23-274x300.png 274w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image23-768x841.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image23.png 1257w\" sizes=\"(max-width: 935px) 100vw, 935px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Impostazione dei ruoli<\/h2>\n\n\n\n<p>Una volta creato l\u2019identity provider \u00e8 necessario creare i ruoli e le policy per fare in modo che gli utenti SSO riescano ad accedere al servizio.Nella console IAM dell\u2019account internal-services fare click su Roles e \u201cCreate a new Role\u201d. Selezionare \u201c<strong>SAML 2.0 federation<\/strong>\u201d come tipo di trusted identity e selezionare l\u2019identity provider appena creato.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"618\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image22-1024x618.png\" alt=\"\" class=\"wp-image-3882\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image22-1024x618.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image22-400x241.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image22-768x464.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image22.png 1529w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>Creare una nuova policy per permettere al ruolo di ottenere un \u201cFederation Token\u201d dall\u2019istanza Amazon Connect, utilizzando questo template json:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>{\n\t\"Version\": \"2012-10-17\",\n\t\"Statement\": &#91;\n    \t{\n        \t\"Sid\": \"Statement1\",\n        \t\"Effect\": \"Allow\",\n        \t\"Action\": \"connect:GetFederationToken\",\n        \t\"Resource\": &#91;\n            \t\"arn:aws:connect:region:Account-id:instance\/amazonconnectintanceid\/user\/${aws:userid}\"\n        \t]\n    \t}\n\t]\n}\n<\/code><\/pre>\n\n\n\n<p>\u00c8 possibile trovare il valore di \u201camazonconnectinstanceid\u201d facendo click sull\u2019istanza Connect e copiando l\u2019ultima parte del campo \u201cARN\u201d per <strong>region<\/strong>:<strong>Account-id <\/strong>utilizzare invece la region e l\u2019id dell\u2019account internal-service.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"197\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image1-1-1024x197.png\" alt=\"\" class=\"wp-image-3840\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image1-1-1024x197.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image1-1-400x77.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image1-1-768x148.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image1-1.png 1481w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>Terminata la creazione occorre tornare sulla console AWS SSO sull\u2019account di management e modificare l\u2019applicazione Connect per concludere la configurazione.&nbsp;<br>Selezionare \u201cEdit configuration\u201d e lasciare vuoto il campo \u201c<strong>Application start URL<\/strong>\u201d. Per il campo \u201c<strong>Relay state\u201d<\/strong> utilizzare: <a href=\"https:\/\/region.console.aws.amazon.com\/connect\/federate\/amazonconnectid\">https:\/\/<strong>region<\/strong>.console.aws.amazon.com\/connect\/federate\/<strong>amazonconnectid<\/strong><\/a> inserendo i valori utilizzati in precedenza.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"905\" height=\"1024\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image20-905x1024.png\" alt=\"\" class=\"wp-image-3878\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image20-905x1024.png 905w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image20-265x300.png 265w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image20-768x869.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image20-1357x1536.png 1357w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image20.png 1404w\" sizes=\"(max-width: 905px) 100vw, 905px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>A questo punto alla sezione \u201c<strong>Attribute Mappings<\/strong>\u201d aggiungere un nuovo mapping, impostando <a href=\"https:\/\/aws.amazon.com\/SAML\/Attributes\/Role\">https:\/\/aws.amazon.com\/SAML\/Attributes\/Role<\/a> come valore per il campo <strong>User attribute in the application<\/strong>\u201d e arn:aws:iam::<strong>internal-services-account-id<\/strong>:saml-provider\/<strong>saml-provider-name<\/strong>,arn:aws:iam::<strong>internal-services-account-id<\/strong>:role\/<strong>amazon-connect-federation-role<\/strong> come valore per il campo&nbsp; \u201cMaps to this string value or user attribute in AWS SSO\u201d<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"660\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image2-1-1024x660.png\" alt=\"\" class=\"wp-image-3842\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image2-1-1024x660.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image2-1-400x258.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image2-1-768x495.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image2-1.png 1273w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>Una volta salvati i cambiamenti assegnare gli utenti utilizzando il tab&nbsp; \u201c<strong>Assigned users<\/strong>\u201d.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Testing<\/h2>\n\n\n\n<p>Utilizzare lo \u201cstart url\u201d definito in amazon sso (solitamente <a href=\"https:\/\/nomeimpostato.awsapps.com\/start\/\">https:\/\/nomeimpostato.awsapps.com\/start\/<\/a> ) e fare login con le credenziali Azure AD\/Office365.<\/p>\n\n\n\n<p>A questo punto l\u2019applicazione Amazon Connect sar\u00e0 disponibile.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"541\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image4-1-1024x541.png\" alt=\"\" class=\"wp-image-3846\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image4-1-1024x541.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image4-1-400x211.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image4-1-768x406.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image4-1.png 1088w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p>Facendo click sull\u2019applicazione sar\u00e0 possibile utilizzare la dashboard di Amazon Connect con le credenziali corrette:<\/p>\n\n\n\n<p><\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large is-resized\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image8-1-1024x162.png\" alt=\"\" class=\"wp-image-3854\" width=\"840\" height=\"132\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image8-1-1024x162.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image8-1-400x63.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image8-1-768x122.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image8-1-1536x244.png 1536w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/image8-1.png 1968w\" sizes=\"(max-width: 840px) 100vw, 840px\" \/><\/figure><\/div>\n\n\n\n<p><\/p>\n\n\n\n<p><\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Per le aziende \u00e8 diventato molto importante essere in grado di utilizzare differenti canali di comunicazione con i propri clienti, [&hellip;]<\/p>\n","protected":false},"author":13,"featured_media":3900,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[467],"tags":[545,514,543,549,547,329],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v21.9.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Federazione cross-account tra Amazon Connect e Azure AD con AWS SSO - Proud2beCloud Blog<\/title>\n<meta name=\"description\" content=\"Abbiamo configurato Amazon Connect con Azure AD come IDP garantendo gestione centralizzata degli utenti e controllo dell\u2019accesso con AWS SSO.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/\" \/>\n<meta property=\"og:locale\" content=\"it_IT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Federazione cross-account tra Amazon Connect e Azure AD con AWS SSO\" \/>\n<meta property=\"og:description\" content=\"Abbiamo configurato Amazon Connect con Azure AD come IDP garantendo gestione centralizzata degli utenti e controllo dell\u2019accesso con AWS SSO.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/\" \/>\n<meta property=\"og:site_name\" content=\"Proud2beCloud Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-11-26T12:59:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-11-26T12:08:21+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/Copertina-blog-26-11-21_27-11-21-social-ita.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"628\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Damiano Giorgi\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"Federazione cross-account tra Amazon Connect e Azure AD con AWS SSO\" \/>\n<meta name=\"twitter:description\" content=\"Abbiamo configurato Amazon Connect con Azure AD come IDP garantendo gestione centralizzata degli utenti e controllo dell\u2019accesso con AWS SSO.\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/Copertina-blog-26-11-21_27-11-21-social-ita.png\" \/>\n<meta name=\"twitter:label1\" content=\"Scritto da\" \/>\n\t<meta name=\"twitter:data1\" content=\"Damiano Giorgi\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tempo di lettura stimato\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minuti\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/\",\"url\":\"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/\",\"name\":\"Federazione cross-account tra Amazon Connect e Azure AD con AWS SSO - Proud2beCloud Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.besharp.it\/it\/#website\"},\"datePublished\":\"2021-11-26T12:59:00+00:00\",\"dateModified\":\"2021-11-26T12:08:21+00:00\",\"author\":{\"@id\":\"https:\/\/blog.besharp.it\/it\/#\/schema\/person\/a9195473e4a658b45cb12d3df3fdf293\"},\"description\":\"Abbiamo configurato Amazon Connect con Azure AD come IDP garantendo gestione centralizzata degli utenti e controllo dell\u2019accesso con AWS SSO.\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/#breadcrumb\"},\"inLanguage\":\"it-IT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.besharp.it\/it\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Federazione cross-account tra Amazon Connect e Azure AD con AWS SSO\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.besharp.it\/it\/#website\",\"url\":\"https:\/\/blog.besharp.it\/it\/\",\"name\":\"Proud2beCloud Blog\",\"description\":\"il blog di beSharp\",\"alternateName\":\"Proud2beCloud Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.besharp.it\/it\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"it-IT\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.besharp.it\/it\/#\/schema\/person\/a9195473e4a658b45cb12d3df3fdf293\",\"name\":\"Damiano Giorgi\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\/\/blog.besharp.it\/it\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/9a20b8c97250d4fb49857192f7e4bedf?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/9a20b8c97250d4fb49857192f7e4bedf?s=96&d=mm&r=g\",\"caption\":\"Damiano Giorgi\"},\"description\":\"Ex sistemista on-prem, pigro e incline all'automazione di task noiosi. Alla ricerca costante di novit\u00e0 tecnologiche e quindi passato al cloud per trovare nuovi stimoli. L'unico hardware a cui mi dedico ora \u00e8 quello del mio basso; se non mi trovate in ufficio o in sala prove provate al pub o in qualche aeroporto!\",\"url\":\"https:\/\/blog.besharp.it\/it\/author\/damiano-giorgi\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Federazione cross-account tra Amazon Connect e Azure AD con AWS SSO - Proud2beCloud Blog","description":"Abbiamo configurato Amazon Connect con Azure AD come IDP garantendo gestione centralizzata degli utenti e controllo dell\u2019accesso con AWS SSO.","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:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/","og_locale":"it_IT","og_type":"article","og_title":"Federazione cross-account tra Amazon Connect e Azure AD con AWS SSO","og_description":"Abbiamo configurato Amazon Connect con Azure AD come IDP garantendo gestione centralizzata degli utenti e controllo dell\u2019accesso con AWS SSO.","og_url":"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/","og_site_name":"Proud2beCloud Blog","article_published_time":"2021-11-26T12:59:00+00:00","article_modified_time":"2021-11-26T12:08:21+00:00","og_image":[{"width":1200,"height":628,"url":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/Copertina-blog-26-11-21_27-11-21-social-ita.png","type":"image\/png"}],"author":"Damiano Giorgi","twitter_card":"summary_large_image","twitter_title":"Federazione cross-account tra Amazon Connect e Azure AD con AWS SSO","twitter_description":"Abbiamo configurato Amazon Connect con Azure AD come IDP garantendo gestione centralizzata degli utenti e controllo dell\u2019accesso con AWS SSO.","twitter_image":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2021\/11\/Copertina-blog-26-11-21_27-11-21-social-ita.png","twitter_misc":{"Scritto da":"Damiano Giorgi","Tempo di lettura stimato":"10 minuti"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/","url":"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/","name":"Federazione cross-account tra Amazon Connect e Azure AD con AWS SSO - Proud2beCloud Blog","isPartOf":{"@id":"https:\/\/blog.besharp.it\/it\/#website"},"datePublished":"2021-11-26T12:59:00+00:00","dateModified":"2021-11-26T12:08:21+00:00","author":{"@id":"https:\/\/blog.besharp.it\/it\/#\/schema\/person\/a9195473e4a658b45cb12d3df3fdf293"},"description":"Abbiamo configurato Amazon Connect con Azure AD come IDP garantendo gestione centralizzata degli utenti e controllo dell\u2019accesso con AWS SSO.","breadcrumb":{"@id":"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/#breadcrumb"},"inLanguage":"it-IT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.besharp.it\/it\/federazione-cross-account-tra-amazon-connect-e-azure-ad-con-aws-sso\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.besharp.it\/it\/"},{"@type":"ListItem","position":2,"name":"Federazione cross-account tra Amazon Connect e Azure AD con AWS SSO"}]},{"@type":"WebSite","@id":"https:\/\/blog.besharp.it\/it\/#website","url":"https:\/\/blog.besharp.it\/it\/","name":"Proud2beCloud Blog","description":"il blog di beSharp","alternateName":"Proud2beCloud Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.besharp.it\/it\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"it-IT"},{"@type":"Person","@id":"https:\/\/blog.besharp.it\/it\/#\/schema\/person\/a9195473e4a658b45cb12d3df3fdf293","name":"Damiano Giorgi","image":{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/blog.besharp.it\/it\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/9a20b8c97250d4fb49857192f7e4bedf?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9a20b8c97250d4fb49857192f7e4bedf?s=96&d=mm&r=g","caption":"Damiano Giorgi"},"description":"Ex sistemista on-prem, pigro e incline all'automazione di task noiosi. Alla ricerca costante di novit\u00e0 tecnologiche e quindi passato al cloud per trovare nuovi stimoli. L'unico hardware a cui mi dedico ora \u00e8 quello del mio basso; se non mi trovate in ufficio o in sala prove provate al pub o in qualche aeroporto!","url":"https:\/\/blog.besharp.it\/it\/author\/damiano-giorgi\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.besharp.it\/it\/wp-json\/wp\/v2\/posts\/3893"}],"collection":[{"href":"https:\/\/blog.besharp.it\/it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.besharp.it\/it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/it\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/it\/wp-json\/wp\/v2\/comments?post=3893"}],"version-history":[{"count":0,"href":"https:\/\/blog.besharp.it\/it\/wp-json\/wp\/v2\/posts\/3893\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/it\/wp-json\/wp\/v2\/media\/3900"}],"wp:attachment":[{"href":"https:\/\/blog.besharp.it\/it\/wp-json\/wp\/v2\/media?parent=3893"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.besharp.it\/it\/wp-json\/wp\/v2\/categories?post=3893"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.besharp.it\/it\/wp-json\/wp\/v2\/tags?post=3893"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}