<style> .chartjs-size-monitor { display: none !important; height: 0 !important; overflow: hidden !important; }p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><style>
.chartjs-size-monitor {
display: none !important; height: 0 !important; overflow: hidden !important;
}
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><p data-pasted="true"><strong>In this guide we will cover:</strong></p><p><strong>- What is the Juniper Mist Integration?</strong></p><p><strong>- Connecting to Juniper Mist</strong></p><p data-pasted="true"><strong>- Sites</strong></p><p><strong>- Assets</strong></p><p data-pasted="true"><strong>- The Halo Integrator</strong></p><p data-pasted="true"><strong>- Alerting</strong></p><p><br></p><p data-pasted="true"><strong><span style="color: rgb(226, 80, 65);">Note: This Integration is available from v2.248+.</span></strong></p><p><br></p><p><span style="font-size: 14pt;"><strong>What is the Juniper Mist Integration?</strong></span></p><p data-pasted="true">The Juniper Mist Integration allows Sites and Assets to be imported from Juniper Mist into Halo. Alerts can also be configured to automatically create Tickets in Halo each time an alert is triggered in Juniper Mist, allowing agents to manage alerts from within Halo.</p><p><br></p><p data-pasted="true"><span style="font-size: 14pt;"><strong>Connecting to Juniper Mist</strong></span></p><p data-pasted="true">In Configuration > Integrations > Asset Management and Alerting, hover over Juniper Mist and press the plus (+) icon to enable the Module.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImZkOWQyZDhiLWY5MzEtNDI1YS05MTA0LTYwMjY2MWVlYzQ1NCJ9.oN-aGop6H18CMErH38UGg6p9m8s5Z9o1BluiwRpFj7M" class="fr-fic fr-fil fr-dib" width="1100" style="width: 1102px; height: 546.52px;" height="547"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 1. Enabling the module</strong></span></p><p><br></p><p>Once enabled, click into the module to begin configuring the Integration.</p><p><br></p><p>Next click into the "Juniper Mist Configuration" button. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijc1YjAwOWZmLTljZjgtNGFlMy1iOWE5LTdhODA1YjlkNWVhYiJ9.NqV23T-CFI9IL8B6IVpa39a8rzBAamV7GY8r4q5duww" class="fr-fic fr-fil fr-dib" width="1105" style="width: 1107px; height: 418.216px;" height="418"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 2. Juniper Mist Configuration</strong></span></p><p><br></p><p>Click "New" to create a new connection, or edit an existing connection by clicking into it. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjdiZTE4YzllLTcyOGUtNDJlZC1hN2Y1LTJhZDIwMjBkNzRlMyJ9.dtltUVZUUhIUOSuZFDMRKZFV-mk9AhFZ69pkVFTK6YI" class="fr-fic fr-fil fr-dib" width="1112" style="width: 1114px; height: 142.377px;" height="142"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 3. Creating a new connection</strong></span></p><p><br></p><p>Before creating your new connection you will need to create an API Token in Juniper Mist. In Juniper Mist, head to Organization > Settings.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjgwMzU3Mjk2LTY2ZTgtNDFmNy04N2EwLWU1YjM4NDkxZGUzNSJ9.UWDz1QhjiOP_HrnNr1lnL1hz3RFbl9AE_DCBKpTtU2s" class="fr-fic fr-fil fr-dib" width="526" style="width: 528px; height: 369.6px;" height="370"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 4. Juniper Mist Settings</strong></span></p><p><br></p><p>First locate your Organization ID, and copy this for later. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjNjMjMzZjVmLWQwM2YtNDQ3Yi05OTMzLTdiMjRiNWMyYzExYyJ9.j2u_8KJLvINJdnNpoSzBoxPuMrmyUl1GLfTfQHMITBA" class="fr-fic fr-fil fr-dib" width="376" style="width: 378px; height: 430.905px;" height="431"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 5. Organization ID</strong></span></p><p><br></p><p>Next, scroll down to the API Token section, and select "Create Token". </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImVlYmFmMDlmLWNlZDAtNGRjMS04ZWNlLTEwOWMxYTg5NTJlYiJ9.vRzP4pdE2oJKR17G90bzzY-5IOp2QyNJ5PbwyThrRGg" class="fr-fic fr-fil fr-dib" width="369" style="width: 371px; height: 456.33px;" height="456"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 6. Creating a Token</strong></span></p><p><br></p><p>Set a name for your Token, and the desired Access Level, then click "Generate". Copy this as it will be required for your connection. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImI4YmQ4MWI3LWViNDEtNDdjNy1hNWI3LTc2YTY5Njk5YjY0NyJ9.ozTvoaFh4-M9BAT_j1rZtJzII3xLX-uEwUGWSskqXew" class="fr-fic fr-fil fr-dib" width="373" style="width: 375px; height: 558px;" height="558"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 7. Generating a Token</strong></span></p><p><br></p><p>Return to the Integration page in Halo, here you will need to set the Name, Organisation ID, Region, and API key for your connection.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjExYmQ1ZGRlLWJmN2UtNDFkYS1hNTRkLTRiYzc4OTQzZDhmOCJ9.WZ22szZV9THnDql2TOSD3VdVZUzscl3lGANaK4fyDZY" class="fr-fic fr-fil fr-dib" width="1113" style="width: 1115px; height: 399.171px;" height="399"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 8. Connecting to Juniper Mist</strong></span></p><p><br></p><p>Click "Save", then use the "Test Configuration" button to confirm your credentials.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjUyZTQ3NjFiLWYzY2EtNGQ1OS1hNTY0LTFjYjJlNThiZjNkMyJ9.Zy019OCBKgbUKejaA5Tm_QJ3xxqYrOXhu0A-Bj54jwU" class="fr-fic fr-fil fr-dib" width="496" style="width: 498px; height: 423.42px;" height="423"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 9. Testing Configuration</strong></span></p><p><br></p><p data-pasted="true"><span style="font-size: 14pt;"><strong>Sites</strong></span></p><p>Once you have connected to Juniper Mist, head into the Sites tab. Here you will need to set the Site matching method, this determines how Halo and Juniper Mist Sites are matched to each other.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjAyZmYwNjQ3LWJiMTUtNGNlYS05NDRlLWQxNjVkNjY5ZDc2NiJ9.2cQH_ZrGSC83mJMnxwurFD9MkDNAGHg0S-TiZFtRc1M" class="fr-fic fr-fil fr-dib" width="758" style="width: 760px; height: 415.877px;" height="416"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 10. Site imports</strong></span></p><p><span style="font-size: 10pt;"><strong> </strong></span></p><p>Depending on the Site Matching Method you select, different options will show. </p><p><br></p><p data-pasted="true"><strong><span style="font-size: 12pt;">Import and map sites from Juniper Mist to sites in Halo</span></strong></p><p data-pasted="true">When the Site matching method is set to "Import and map sites from Juniper Mist to sites in Halo", you will have the option to add Site Mappings. To do this, click "+ Add" at the top of the Site Mappings table. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjAyYmQwNGZjLWQ1M2EtNGI0Zi04MDYxLWJkY2JjNjU5MTk1OCJ9.JxOzeBjo-4kBfs3IC7fJS5fsMjcZnaMPbnxa-cT5zqY" class="fr-fic fr-fil fr-dib" width="747" style="width: 749px; height: 517.571px;" height="518"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 11. Site matching method</strong></span></p><p><br></p><p>This will open a modal window where a Halo Site can be mapped to a Juniper Mist Site. This allows the Integration to know which Site in Juniper Mist relates to each Site in Halo.</p><p><br></p><p><strong><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjAyZTA1YTc2LWRiY2UtNDAwNi04OTZiLTNhMDFhYWJkM2Y0NSJ9.W5ZyM6ndpobHSmQrMdSlkawnOZP9XJoAMYKEfUbw2Yo" class="fr-fic fr-fil fr-dib" width="569" style="width: 571px; height: 254.703px;" height="255"></strong></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 12. Site Mappings</strong></span></p><p><br></p><p>Once you have completed your Site Mappings, set a Customer for any new Sites to be created under in the "Customer for New Sites" dropdown. Is Sites are not mapped they will be created under the Customer specified here. </p><p><br></p><p data-pasted="true"><strong><span style="font-size: 12pt;">Site Rules</span></strong></p><p data-pasted="true">When the Site matching method is set to "Site Rules", you will have the option to add rules to determine which Site an Asset is assigned to based on a field. To do this, click "+ Add" at the top of the Site Rules table. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjVjNDQ3OGIxLWZkNWEtNDhiZi1iMWFmLTQ5MmZjYjRhNmI1MSJ9.1Tz1tSzgBuv0Frn57AAxcJe09K4Wsp6TyIPWKtG-BXk" class="fr-fic fr-fil fr-dib" width="805" style="width: 807px; height: 536.799px;" height="537"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 13. Site Rules</strong></span></p><p><br></p><p>This will open a modal window where you will need to set the Halo Site to assign the Asset to, and criteria to determine when to assign to this Site. To add criteria, click the "+ Add" button at the top of the Criteria table.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImVjYzc0MTIzLTJkOTUtNDc3Zi05NmNlLTYxMDgxZTRmZWU1OCJ9.2mFxY3ASfuCXnWAuaaYjdNFn5vhMqOy14EUsLa_wYEw" class="fr-fic fr-fil fr-dib" width="529" style="width: 531px; height: 387.382px;" height="387"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 14. Creating a rule</strong></span></p><p><br></p><p>Select the field you would like to use for the rule, and set the value this should be set to in order for the Asset to be assigned to the Site. Then save your new rule. </p><p><br></p><p><strong><em>Note: Criteria is based on Halo fields, so any fields set here will need to be mapped in the following "Assets" tab.</em></strong></p><p><br></p><p>This method does not require the import of Sites after mapping.</p><p><br></p><p data-pasted="true"><span style="font-size: 12pt;"><strong>General Configuration</strong></span></p><p>Both methods then offer additional configuration options.</p><p><br></p><p><strong>Default Site: </strong>This is the Site that Assets will be imported under if they have not been matched to a Site by the matching method.</p><p><strong>Don't update the asset site for existing or matched assets:</strong> If enabled, any Assets that already exist in Halo will not have their Site changed (if different in Juniper Mist).</p><p><br></p><p data-pasted="true">Upon saving, and if using the "Import and map sites from Juniper Mist to sites in Halo" Site matching method, the "Import Sites" button will show to manually import Sites. This button will be hidden if using the "Site Rules" method. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjIyMmZhOGFhLTIxNWEtNDlmYy05ZTRiLWYzMTFkNDc3ZDY2MyJ9._4EFI8oBrUbApACxN2mLbrpMWTRQ49ip6PyySyUOcKg" class="fr-fic fr-fil fr-dib" width="697" style="width: 699px; height: 543.215px;" height="543"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 15. Importing Sites</strong></span></p><p><br></p><p><span style="font-size: 14pt;"><strong>Assets</strong></span></p><p data-pasted="true">Once Sites have been matched (and imported if using the Site mapping method), you can then import the Assets in the Assets tab.</p><p><br></p><p>The first field is the "Asset Matching Field", which will determine how Assets are matched to existing records when updating Assets. This should be an field that is unique per Asset.</p><p><br></p><p data-pasted="true">You can then set Field Mappings in the table below by clicking "+ Add". These mappings determine which Halo fields information from Armis is pulled into. If the "Site Rules" matching method was used, ensure every field that is used as criteria is correctly mapped here to match that.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImNjZjIyNWMzLTM3NDUtNDhmZS04OGI1LWI0MTYyY2NjMzRmNyJ9.O2_68stzUrHoWj6dX_B857jHDb1uPivLtjTNEYrZbdE" class="fr-fic fr-fil fr-dib" width="1010" style="width: 1012px; height: 382.325px;" height="382"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 16. Field Mappings</strong></span></p><p><br></p><p>If you do not have an existing field in Halo for this information to be stored in, you can select the option "Create a new Field during the next import" in the "Halo Field" dropdown. This will create a new field in Halo using the field name from Juniper Mist. If a field with this name already exists, it will instead be linked to the existing Field.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQ0OTdlNzI4LTVkNTgtNGQ3OS1iZTA4LWVmMDM5YzBmNDE1OSJ9.3NzMjr9OQjk2VjIIzCGTwmZxH7gx-VFcR4nxEoBiIN8" class="fr-fic fr-fil fr-dib" width="504" style="width: 506px; height: 319px;" height="319"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 17. Creating a new Field during the import</strong></span></p><p><br></p><p>Once you have set your Field Mappings, you will need to set a Default Group for new Asset Types. Juniper Mist Asset Types are matched to existing Halo Asset Types via their name. Any which do not match will be created under the group set here.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImVkYWM0MmNmLTA4YzktNGMwMC1hNWQ5LTljNTM1ODllZjU4MyJ9.jZnbwEsF8C4dUrWUmwqNYE85FUBWusWhwjZef8koq90" class="fr-fic fr-fil fr-dib" width="759" style="width: 761px; height: 355.424px;" height="355"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 18. Asset Types</strong></span></p><p><br></p><p>To determine the Asset Type of imported Assets, you will need to choose one of three methods from the "Determining an Asset's type" dropdown.</p><p><br></p><p data-pasted="true"><strong>Use the same type for all Assets</strong></p><p>When "Determining an Asset's Type" is set to "Use the same type for all Assets", all Assets imported into Halo from Juniper Mist will have the same specified Asset Type. This Asset Type is set using the "Default Asset Type" dropdown. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjhlMzBiYTFlLTM1OTAtNDExYS1hOTVmLTA1NjMxYmU1MmI2ZiJ9.u63JBwAvElbmlWctpP1MsmA-NAthqemPYsRgF0UriFE" class="fr-fic fr-fil fr-dib" width="740" style="width: 742px; height: 166.413px;" height="166"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 19. Use the same type for all Assets </strong></span></p><p><br></p><p data-pasted="true"><strong>Use a field to determine each Asset's type</strong></p><p>When "Determining an Asset's Type" is set to "Use a field to determine each Asset's type, a set field will be used for determining an Asset's type. If an Asset cannot match via this field, it will be assigned to a set default Asset Type.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijc2N2M2MDIwLWFkNjItNDI2Ny04NGI2LWU5MmU3MWQxOTBjZSJ9.BXAOlobtieL1vkTCpnYj-b0R_iQeSwvFH4Hq11Fmi_s" class="fr-fic fr-fil fr-dib" width="860" style="width: 862px; height: 265.337px;" height="265"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 20. Use a field to determine each Asset's type </strong></span></p><p><br></p><p data-pasted="true"><strong>Determine Asset Type using rules </strong></p><p>When "Determining an Asset's Type" is set to "Determine Asset Type using rules ", criteria can be mapped to Asset Types based on values in Halo Fields. If an Asset cannot match via this Field, it will be assigned to a set default Asset Type. To add a rule, click "+ Add". This will open a modal window where you will need to set the Halo Asset Type to assign the Asset to, and criteria to determine when to apply this Asset Type. To add criteria, click the "+ Add" button at the top of the Criteria table.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjA5NzUyNDg2LTFhYWYtNDJlNy1iNzBlLWMwZTc2ZWZlOGQ5OSJ9.3HknYaGc3hpDazX27-7Q3EyVhDkax--r9_Anh_vpeQ4" class="fr-fic fr-fil fr-dib" width="737" style="width: 739px; height: 277.272px;" height="277"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 21. Determine Asset Type using rules</strong></span></p><p><br></p><p>This will open a modal window where you will need to set the Halo Asset Type to assign the Asset to, and criteria to determine when to apply this Asset Type. To add criteria, click the "+ Add" button at the top of the Criteria table.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjA5YTVjMzAwLWIxNTEtNDQ3NC1hYWM3LTY3NWJjNjBlNzhhNyJ9.M6fjS8t_ypUVI16cr4HB2ipWUadGsWd-Xv8osicTKME" class="fr-fic fr-fil fr-dib" width="614" style="width: 616px; height: 453.422px;" height="453"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 22. Adding rules </strong></span></p><p><br></p><p data-pasted="true"><span style="font-size: 12pt;"><strong>Miscellaneous Asset Import Settings</strong></span></p><p>Finally you can set the miscellaneous Asset Import settings.</p><p><br></p><p data-pasted="true"><strong>Don't create new Assets:</strong> If enabled, Assets will not be created, only updated.</p><p><strong>Status of New Assets:</strong> Newly created Assets will be given this Status.</p><p><strong>Don't update the Asset type for existing or matched Assets:</strong> Existing Assets will keep their current Halo Asset Type, and will not be updated by the import.</p><p><br></p><p data-pasted="true">Click "Save", and to import the Assets, click the "Import Assets" button at the bottom of the tab.</p><p><br></p><p><span style="font-size: 14pt;"><strong>The Halo Integrator</strong></span></p><p data-pasted="true">Once Sites and Assets are configured, you can enable the Halo Integrator to automatically sync Assets and Sites on a schedule. </p><p> </p><p data-pasted="true"><strong><em>Note: It is recommended to ensure you are happy with the configuration by manually importing before enabling automatic syncs via the Integrator.</em></strong></p><p><br></p><p data-pasted="true">Head into the Halo Integrator tab, and check "Enable the Halo Integrator for the Juniper Mist integration". Now select the entities you wish to automatically sync.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjljMjY3YjQ4LTE3MzctNDJiOC04ZmZmLTQwOTg4ZTE1Y2M1MiJ9.mpsl4rG-yY-qf6DDrlpQ3dDJ-C2Dz7m40vxJN6F8fwU" class="fr-fic fr-fil fr-dib" width="993" style="width: 995px; height: 430.088px;" height="430"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 23. The Halo Integrator</strong></span></p><p><br></p><p>If you would like Assets that are deleted in Juniper Mist to be made inactive when then sync to Halo, click "Deactivate Assets in Halo when they are deleted from Juniper Mist (Halo Integrator only)".</p><p><br></p><p><span style="font-size: 14pt;" data-pasted="true"><strong>Alerting</strong></span></p><p>If you would like to receive Alerts from Juniper Mist in Halo, head to the Alerts tab, and select "Enable Alerts". Once selected, you can set the Ticket Type and User for the Alerts to be created under. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImU2YTgzZDJhLWFkNGQtNDhkZS1iNWZiLTQxOTc3ZjhhYTdjYSJ9.K5ZjH1OdJS2bx8z9J_XXLRWXIh-XPBYNuCZbFf8BBlc" class="fr-fic fr-fil fr-dib" width="913" height="706"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 24. Enabling Alerts</strong></span></p><p><br></p><p>Next you will need to set a Webhook Secret, and copy this. Then copy the Webhook URL provided at the top of the page. This will be formatted as https://YOURHALOURL.COM/api/notify/junipermist.</p><p><br></p><p>Now head to Juniper Mist, Organization > Settings. In the Webhooks section click "Add Webhook", and enter the URL and secret you copied earlier. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjVlNTlkYzNhLWEyMzYtNDEwMy1iODM0LTlmYWQ3MzgzNGU0NCJ9.NW1Azhnppmd1lLP9zP2Aon38qKRXlgVKEjByM7MN2PU" class="fr-fic fr-fil fr-dib" width="842" style="width: 844px; height: 364.618px;" height="365"></p><p data-pasted="true"><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 25. Creating a webhook</strong></span></p><p><br></p><p>Add this webhook and return to Halo.</p><p><br></p><p>Head back to the main page of the Integration (Configuration > Integrations > Juniper Mist). Here you can configure additional webhook settings.</p><p><br></p><p><em><strong>Note: This is the page you will see when you first click into the module, not under the Juniper Mist Configuration Button.</strong></em></p><p><br></p><p><em><strong><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjVjZDQ5MTJiLTY4ZGUtNDUyOS04MjgyLTYxMWRiYTFjMDJiZSJ9.KfjE3oHkd7xKkHLimEuoUuqMoetEISpvFkO-d4VK01Q" class="fr-fic fr-fil fr-dib" width="948" style="width: 950px; height: 353.698px;" height="354"> </strong></em><span style="font-size: 10pt;" data-pasted="true"><strong>Fig 26. Wehook Settings</strong></span></p><p><br></p><p>If "Use incoming webhook service" is enabled in Configuration > Advanced Settings, you will have the option to set the <a href="https://www.usehalo.com/guides/2615" target="_blank" rel="noopener noreferrer">Incoming Webhook Processing Method</a>, this will control how the webhooks recieved from Juniper Mist are processed by Halo.</p><p><br></p><p data-pasted="true"><strong>Use the default webhook processing functionality: </strong>This is the default option. Each incoming webhook will be processed immediately, and failed webhooks will not be retried.</p><p><strong>Use the incoming webhook service with immediate processing: </strong>This means the webhook service is in use for the integration. Each incoming webhook will be processed immediately, and any failed webhooks will then be automatically retried a further 2 times via the task scheduling service. This is the recommended option.</p><p><strong>Use the incoming webhook service with delayed processing: </strong>The same as "Use the incoming webhook service with immediate processing", but webhooks are not processed immediately when they are received. Instead, they are automatically queued and picked up by the task scheduling service. This option is only necessary if option 2 is failing to process webhooks after 3 attempts due to rate limits, i.e. the webhook result is returning 429 too many requests.</p><p><br></p><p>Logic has been added to the task scheduler to retrieve webhook resource data in batches. This greatly reduces the number of requests made to the third-party API, thus reducing the chance of hitting third-party rate limits. This logic is always used for "Use the incoming webhook service with delayed processing", and is used before retrying webhooks when using "Use the incoming webhook service with delayed processing".</p><p><br></p><p>In order to control how the Tickets created from Alerts in Juniper Mist are prioritised in Halo, you can map priorities. To do this, click "+ Add" at the top of the Priority Mappings table. This will open a modal window where you can match a Juniper Mist Priority to a Priority in Halo. This means when a Ticket is raised from the webhook, the priority of the Alert in Juniper Mist will be reflected in Halo.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjBjZDhlNjcyLTMyNjktNDI1Yy1iNzAyLTQyNjkzN2RmNWQzNyJ9.ZLe5z1rxBj7p9wgW4XMRSOcC4BqNcxuafYOUu-U84jM" class="fr-fic fr-fil fr-dib" width="561" style="width: 563px; height: 248.532px;" height="249"><span style="font-size: 10pt;"><strong>Fig 27. Priority Mappings</strong></span></p>
