[{"data":1,"prerenderedAt":626},["ShallowReactive",2],{"connector-fr-workspaceone-uem":3},{"id":4,"title":5,"body":6,"category":616,"description":617,"extension":618,"meta":619,"navigation":620,"path":621,"seo":622,"sidebar":623,"stem":624,"updatedAt":616,"__hash__":625},"connectorsFr\u002Ffr\u002Fconnectors\u002Fworkspaceone-uem.md","Workspace ONE UEM",{"type":7,"value":8,"toc":597},"minimark",[9,13,18,21,34,38,58,62,65,70,163,167,227,231,235,238,291,295,363,367,458,462,488,491,497,542,562,566],[10,11,12],"p",{},"Le connecteur Workspace ONE UEM récupère dans OverView les appareils enrôlés dans votre tenant Omnissa Workspace ONE UEM ainsi que leurs utilisateurs d'enrôlement, via l'API REST de Workspace ONE UEM.",[14,15,17],"h2",{"id":16},"objective","Objectif",[10,19,20],{},"Le connecteur Workspace ONE UEM récupère les informations suivantes :",[22,23,24,28,31],"ul",{},[25,26,27],"li",{},"Appareils enrôlés dans le tenant (nom d'hôte, numéro de série, constructeur, modèle, IMEI, stockage, état du chiffrement et interfaces réseau)",[25,29,30],{},"Système d'exploitation, applications installées et statut de conformité de chaque appareil",[25,32,33],{},"Utilisateurs d'enrôlement associés aux appareils",[14,35,37],{"id":36},"prerequisites","Prérequis",[22,39,40,55],{},[25,41,42,43,47,48,47,51,54],{},"Un compte administrateur autorisé à créer des rôles sur la page ",[44,45,46],"strong",{},"Accounts"," > ",[44,49,50],{},"Administrators",[44,52,53],{},"Admin Roles",", dans l'organization group que le connecteur interroge.",[25,56,57],{},"L'API REST est la même sur les deux déploiements, seul l'identifiant change. Les tenants SaaS s'authentifient avec un client OAuth 2.0. Le Workspace ONE Token Service qui émet ces tokens n'existe pas on-premises, où l'API s'atteint avec une clé d'API et un compte administrateur en lecture seule.",[14,59,61],{"id":60},"information-to-provide-in-overview","Informations à fournir dans OverView",[10,63,64],{},"Renseignez le tableau correspondant à votre déploiement. Tous ses champs sont obligatoires.",[66,67,69],"h3",{"id":68},"saas-fields","Tenant SaaS",[71,72,73,86],"table",{},[74,75,76],"thead",{},[77,78,79,83],"tr",{},[80,81,82],"th",{},"Champ",[80,84,85],{},"Description",[87,88,89,117,143,153],"tbody",{},[77,90,91,97],{},[92,93,94],"td",{},[44,95,96],{},"API URL",[92,98,99,100,104,105,108,109,112,113,116],{},"Le serveur d'API de votre tenant, qui n'est pas la console sur laquelle vous vous connectez : reprenez l'URL de la console et remplacez ",[101,102,103],"code",{},"cn"," par ",[101,106,107],{},"as",". La console ",[101,110,111],{},"https:\u002F\u002Fcn4855.awmdm.com"," donne ",[101,114,115],{},"https:\u002F\u002Fas4855.awmdm.com",".",[77,118,119,124],{},[92,120,121],{},[44,122,123],{},"Token URL",[92,125,126,127,130,131,134,135,138,139,142],{},"Le Workspace ONE Token Service qui émet les tokens OAuth. Un tenant hébergé en Europe utilise ",[101,128,129],{},"https:\u002F\u002Femea.uemauth.workspaceone.com\u002Fconnect\u002Ftoken",", avec ",[101,132,133],{},"na"," ou ",[101,136,137],{},"apac"," à la place de ",[101,140,141],{},"emea"," pour ces régions.",[77,144,145,150],{},[92,146,147],{},[44,148,149],{},"Client ID",[92,151,152],{},"Identifiant du client OAuth, affiché une seule fois à sa création",[77,154,155,160],{},[92,156,157],{},[44,158,159],{},"Client Secret",[92,161,162],{},"Secret de ce même client OAuth, affiché une seule fois à sa création",[66,164,166],{"id":165},"on-premises-fields","Déploiement on-premises",[71,168,169,177],{},[74,170,171],{},[77,172,173,175],{},[80,174,82],{},[80,176,85],{},[87,178,179,194,207,217],{},[77,180,181,185],{},[92,182,183],{},[44,184,96],{},[92,186,187,188,190,191,193],{},"L'URL de base de votre serveur d'API REST. La règle ",[101,189,103],{}," vers ",[101,192,107],{}," ci-dessus est une convention de nommage SaaS : on-premises, le serveur d'API est défini par votre installation et peut différer de l'hôte de la console.",[77,195,196,201],{},[92,197,198],{},[44,199,200],{},"API Key",[92,202,203,204],{},"La clé générée sur la page de paramètres REST API, que le connecteur envoie dans l'en-tête ",[101,205,206],{},"aw-tenant-code",[77,208,209,214],{},[92,210,211],{},[44,212,213],{},"Username",[92,215,216],{},"Nom d'utilisateur du compte administrateur portant le rôle en lecture seule",[77,218,219,224],{},[92,220,221],{},[44,222,223],{},"Password",[92,225,226],{},"Mot de passe de ce même compte administrateur",[14,228,230],{"id":229},"procedure","Procédure",[66,232,234],{"id":233},"create-a-read-only-role","Créer un rôle en lecture seule",[10,236,237],{},"Le rôle définit les endpoints API que l'identifiant peut appeler. Il est attribué au client OAuth en SaaS, et au compte administrateur on-premises.",[239,240,241,250,256,269,286],"ol",{},[25,242,243,244,47,246,47,248,116],{},"Connectez-vous à la console Workspace ONE UEM et allez dans ",[44,245,46],{},[44,247,50],{},[44,249,53],{},[25,251,252,253,116],{},"Cliquez sur ",[44,254,255],{},"Add Role",[25,257,258,259,262,263,266,267,116],{},"Saisissez un ",[44,260,261],{},"Name"," (ex. : ",[101,264,265],{},"OverView Connector",") et une ",[44,268,85],{},[25,270,271,272,277,278,281,282,285],{},"Saisissez chaque permission listée dans ",[273,274,276],"a",{"href":275},"#required-permissions","Permissions requises"," dans le champ ",[44,279,280],{},"Search Resources",", puis cochez sa case ",[44,283,284],{},"Read",". Laissez toutes les autres ressources décochées.",[25,287,252,288,116],{},[44,289,290],{},"Save",[66,292,294],{"id":293},"create-an-oauth-client","Créer un client OAuth, en SaaS",[239,296,297,306,320,325,341,354],{},[25,298,299,300,47,303,116],{},"Allez dans ",[44,301,302],{},"Groups & Settings",[44,304,305],{},"Configurations",[25,307,308,309,312,313,316,317,116],{},"Saisissez ",[101,310,311],{},"OAuth"," dans le champ de recherche ",[44,314,315],{},"Enter a name or category",", puis sélectionnez ",[44,318,319],{},"OAuth Client Management",[25,321,252,322,116],{},[44,323,324],{},"Add",[25,326,258,327,329,330,332,333,336,337,340],{},[44,328,261],{}," et une ",[44,331,85],{},", sélectionnez l'",[44,334,335],{},"Organization Group"," qui contient les appareils à importer, et sélectionnez le ",[44,338,339],{},"Role"," créé ci-dessus.",[25,342,343,344,347,348,351,352,116],{},"Positionnez le ",[44,345,346],{},"Status"," sur ",[44,349,350],{},"Enabled",", puis cliquez sur ",[44,353,290],{},[25,355,356,357,359,360,362],{},"Copiez immédiatement le ",[44,358,149],{}," et le ",[44,361,159],{}," : ils ne sont affichés qu'une seule fois et ne peuvent plus être récupérés une fois l'écran fermé.",[66,364,366],{"id":365},"create-an-api-key-and-an-admin-account","Créer une clé d'API et un compte administrateur, on-premises",[239,368,369,388,411,420,434,445],{},[25,370,299,371,47,373,47,376,47,379,47,382,47,385,116],{},[44,372,302],{},[44,374,375],{},"All Settings",[44,377,378],{},"System",[44,380,381],{},"Advanced",[44,383,384],{},"API",[44,386,387],{},"REST API",[25,389,390,391,394,395,398,399,401,402,329,405,407,408,410],{},"Dans l'onglet ",[44,392,393],{},"General",", cochez ",[44,396,397],{},"Enable API Access",", cliquez sur ",[44,400,324],{},", saisissez un nom de ",[44,403,404],{},"Service",[44,406,85],{},", puis copiez l'",[44,409,200],{}," générée.",[25,412,390,413,416,417,116],{},[44,414,415],{},"Authentication",", sélectionnez ",[44,418,419],{},"Basic",[25,421,299,422,47,424,47,426,351,429,47,431,116],{},[44,423,46],{},[44,425,50],{},[44,427,428],{},"Admins",[44,430,324],{},[44,432,433],{},"Add Admin",[25,435,390,436,438,439,347,442,444],{},[44,437,419],{},", positionnez le ",[44,440,441],{},"User Type",[44,443,419],{}," et renseignez le nom d'utilisateur, le mot de passe, le prénom et le nom.",[25,446,390,447,332,450,452,453,455,456,116],{},[44,448,449],{},"Roles",[44,451,335],{}," qui contient les appareils à importer et le ",[44,454,339],{}," créé ci-dessus, puis cliquez sur ",[44,457,290],{},[66,459,461],{"id":460},"configure-the-connector-in-overview","Configurer le connecteur dans OverView",[239,463,464,473,482],{},[25,465,466,467,47,470,116],{},"Dans OverView, allez dans ",[44,468,469],{},"Data Sources Settings",[44,471,472],{},"Sources",[25,474,475,476,478,479,116],{},"Sélectionnez ",[44,477,5],{}," et cliquez sur ",[44,480,481],{},"Configure",[25,483,484,485,116],{},"Renseignez l'API URL et les identifiants de votre déploiement, puis cliquez sur ",[44,486,487],{},"Save Configuration",[14,489,276],{"id":490},"required-permissions",[10,492,493,494,496],{},"Le rôle a besoin de deux ressources, toutes deux au niveau ",[44,495,284],{}," : le connecteur ne crée, ne modifie et ne supprime rien dans Workspace ONE UEM.",[71,498,499,509],{},[74,500,501],{},[77,502,503,506],{},[80,504,505],{},"Permission",[80,507,508],{},"Données récupérées",[87,510,511,527],{},[77,512,513,524],{},[92,514,515,47,518,47,521],{},[44,516,517],{},"REST",[44,519,520],{},"Devices",[44,522,523],{},"REST API Devices Read",[92,525,526],{},"Appareils, leurs interfaces réseau, leurs applications installées et leur statut de conformité",[77,528,529,539],{},[92,530,531,47,533,47,536],{},[44,532,517],{},[44,534,535],{},"Users",[44,537,538],{},"REST API Users Read",[92,540,541],{},"Utilisateurs d'enrôlement",[10,543,544,545,548,549,548,552,548,555,558,559,116],{},"Elles couvrent les endpoints ",[101,546,547],{},"devices\u002Fsearch",", ",[101,550,551],{},"devices\u002F{id}\u002Fnetwork",[101,553,554],{},"devices\u002F{id}\u002Fapps",[101,556,557],{},"devices\u002F{id}\u002Fcompliance"," et ",[101,560,561],{},"system\u002Fusers\u002Fsearch",[14,563,565],{"id":564},"official-documentation","Documentation officielle",[22,567,568,576,583,590],{},[25,569,570],{},[273,571,575],{"href":572,"rel":573},"https:\u002F\u002Fdocs.omnissa.com\u002Fbundle\u002FWorkspaceONE-UEM-Console-BasicsVSaaS\u002Fpage\u002FUsingUEMFunctionalityWithRESTAPI.html",[574],"nofollow","Using UEM Functionality With a REST API",[25,577,578],{},[273,579,582],{"href":580,"rel":581},"https:\u002F\u002Fdocs.omnissa.com\u002Fbundle\u002FSystemSettingsVSaaS\u002Fpage\u002FRestAPIforWorkspaceONEUEM.html",[574],"Rest API for Workspace ONE UEM",[25,584,585],{},[273,586,589],{"href":587,"rel":588},"https:\u002F\u002Fdocs.omnissa.com\u002Fbundle\u002FWorkspaceONE-UEM-Console-BasicsVSaaS\u002Fpage\u002FRoleBasedAccess.html",[574],"Role Based Access",[25,591,592],{},[273,593,596],{"href":594,"rel":595},"https:\u002F\u002Fdeveloper.omnissa.com\u002Fworkspace-one-uem-apis\u002F",[574],"Workspace ONE UEM API reference",{"title":598,"searchDepth":599,"depth":599,"links":600},"",2,[601,602,603,608,614,615],{"id":16,"depth":599,"text":17},{"id":36,"depth":599,"text":37},{"id":60,"depth":599,"text":61,"children":604},[605,607],{"id":68,"depth":606,"text":69},3,{"id":165,"depth":606,"text":166},{"id":229,"depth":599,"text":230,"children":609},[610,611,612,613],{"id":233,"depth":606,"text":234},{"id":293,"depth":606,"text":294},{"id":365,"depth":606,"text":366},{"id":460,"depth":606,"text":461},{"id":490,"depth":599,"text":276},{"id":564,"depth":599,"text":565},null,"Intégrez Workspace ONE UEM pour récupérer les appareils enrôlés dans votre tenant et leurs utilisateurs d'enrôlement","md",{},true,"\u002Ffr\u002Fconnectors\u002Fworkspaceone-uem",{"title":5,"description":617},{"label":5},"fr\u002Fconnectors\u002Fworkspaceone-uem","o-l8S4ura6i5h-ovnW_glY_PcuT4cDn19Fp3HajPgM4",1791561316974]