People Finding with Cisco Meraki on PlaceOS

People Finding with Cisco Meraki on PlaceOS

Wireless

Cisco Meraki provides two interfaces for locating users:

1. Dashboard API
   • PlaceOS uses version 1 of the API
2. Scanning API
   • Version 3 of the API is required

Data Collected

Ideally you collect the following:

1. Username to MAC address mappings
   • Provided by the Dashboard API
   • Regularly polled via HTTP to learn who owns the devices on the network
2. MAC address to x, y map coordinates and SSID
   • Provided by the Scanning API
   • Cisco Meraki uses a webhook to post data to PlaceOS
   • PlaceOS must be accessible on the public internet with valid TLS certificates

Device Certificates

{% hint style=“info” %} If devices authenticate against the network using certificates, the username is unknown to Cisco Meraki. In this case, you need to determine usernames another way. {% endhint %}

1. Username to IP address
   • You may have an established method for this process, which you may use
   • One of the most reliable methods is parsing Domain Controller authentication logs
2. IP address to MAC address mappings
   • Provided by the Dashboard API
   • Regularly polled to learn who owns the devices on the network
3. MAC address to x, y map coordinates and SSID
   • Provided by the Scanning API
   • Cisco Meraki uses a webhook to post data to PlaceOS
   • PlaceOS must be accessible on the public internet with valid TLS certificates

If you use device certificates, you will need to have Step 1 in near-real-time to match usernames to MAC addresses

Integration Requirements

1. Cisco Meraki must be on Firmware R26 or higher
2. Cisco Meraki must be able to connect to PlaceOS rest-api microservice
3. PlaceOS microservices must be able to connect to Cisco Meraki
4. Cisco Meraki Scanning API v3 or higher must be configured
   • Provide PlaceOS integrator the validator code
   • Provide PlaceOS integrator the secret code
5. Cisco Meraki Dashboard API v1 or higher must be configured
   • Provide PlaceOS integrator with API Key
6. PlaceOS integrator to provide a webhook for posting logs
   • Example script

Wired

For locating users plugged into a wired network, possibly via a docking station.

1. Dashboard API
   • PlaceOS uses version 1 of the API
2. SNMP configuration
   • PlaceOS requires Link Up and Link Down traps
   • PlaceOS requires SNMP access to switches directly

Data Collected

1. Username to IP address
   • You may have an established method for this process, which you may use
   • One of the most reliable methods is parsing Domain Controller authentication logs
2. IP address to MAC address mappings
   • Provided by the Dashboard API
   • Regularly polled to learn who owns the devices on the network
3. MAC address to Switch Port mappings
   • Provided by polling the Network Switches (SNMP queries)
   • SNMP Traps allow you to detect changes in real time
   • PlaceOS must be able to receive traps originating from the public internet

Integration Requirements

1. Cisco Meraki must be able to connect to PlaceOS
2. PlaceOS must be able to connect to Cisco Meraki
3. Cisco Meraki Dashboard API must be configured
   • Provide PlaceOS with API Key
4. Cisco Meraki SNMP access must be configured
   • SNMP Link Up and Link Down traps
   • Direct switch SNMP polling configured
   • Provide PlaceOS with community strings and credentials if using SNMPv3
5. Provide PlaceOS with list of Switch IP addresses
6. Provide PlaceOS with Switch Port to Desk ID mappings