LogoLogo
  • PlaceOS Documentation
  • Overview
    • Key Concepts
      • Drivers
      • Interfaces
      • Modules
      • Settings
      • Systems
      • Triggers
      • Zones
    • Languages
      • Crystal
      • TypeScript
    • Protocols
      • MQTT
      • SAML
      • OAuth2
  • How To
    • Configure PlaceOS for Microsoft 365
      • Step 1: Room Calendar Access
        • Create Azure App Registration (Application Permissions)
        • Exchange Calendar Group
        • Limit Application Permissions
        • Configure PlaceOS Calendar Driver
      • Step 2: User Authentication & Calendar Access
        • Create a PlaceOS Authentication Source
        • Create Azure App Registration (Delegated Permissions)
        • Configure PlaceOS Authentication Source
        • Add User Login Redirects
      • Concierge Access
      • Troubleshooting
        • Blocked or Blacklisted IP Error
    • Configure PlaceOS for Google Workspace
      • Google Configuration
        • Create Google Cloud Project & Enable API
        • Configure Google Cloud Service Account
        • Add Google Workplace Permissions
        • Create Google Marketplace App (optional)
        • Google Workspace Service User (RBAC)
        • Configure Access to Google Resource Calendars
      • User Authentication
        • Create a PlaceOS Authentication Source for Google
        • Create Google Cloud OAuth2 Client App
        • Configure PlaceOS Auth Source for Google
        • Add User Login Redirects
    • Deployment
      • Deploy AWS Fargate on Modular CloudFormation Stacks
      • Deploy AWS Fargate on Nested CloudFormation Stacks
      • Writing Import Scripts
    • Analytics
      • MQTT Integration
    • Backoffice
      • Add a Domain to PlaceOS
      • Backoffice File Upload
      • Configure Staff API
      • Calendar Driver
      • Enable Sensor UI
      • Bookings Driver
      • Configure a webhook
    • Authentication
      • Azure B2C
        • Azure B2C Custom Policy Framework
        • Configure PlaceOS for Azure B2C
        • 365 Room Resources on Azure B2C
      • Configure SAML SSO
        • Configure SAML2 with AD FS
        • Configure SAML2 with Auth0
        • Configure SAML2 with Azure AD
        • Configure SAML2 with Google Workspace
      • Configure OAuth2 SSO
      • X-API Keys
      • Bearer tokens
    • Location Services
      • Location Services
      • Area Management
      • Discovering User Devices
      • Locating Users on a Network
      • People Finding with Cisco Meraki on PlaceOS
      • People Finding with Juniper Mist on PlaceOS
    • Notifications
      • Catering Orders
    • User Interfaces
      • Booking Panel App
      • Workplace App
      • Native Booking Panel App
      • Deploy a Frontend Interface
      • Microsoft Outlook Plugin
      • Configure Endpoint Auto Login
      • SVG Map Creation
      • Configuring a default UI
  • Tutorials
    • Setup a dev environment
    • Backend
      • Troubleshooting Backend Failures
      • Import Bookable Rooms
      • Writing A Driver
        • Testing drivers
        • ChatGPT / LLM Capabilities
          • Native GPT Plugins
      • Testing Internal Builds
    • Backoffice
      • Adding Drivers & Modules
      • Add Zone Structure
    • Common Configurations
      • Asset Manager
      • Catering
      • Locker Booking
      • Webex Instant Connect
      • Desk booking
      • Sensor Data Collection
        • Configure Kontakt IO
        • Configuring Meraki
        • Configuring DNA Spaces
      • Elevated Privileges
  • Reference
    • API
      • Real-time Websocket
      • Rest API
      • Staff API
    • Drivers
      • PlaceOS
        • Bookings
        • Staff API
        • Visitor Mailer
        • Lockers
      • Microsoft
        • Graph API
    • PlaceOS Skills
    • Privacy Policy
    • Recommended Products
    • Supported Integrations
    • System Architecture
    • System Functionality & Requirements
    • Infrastructure Requirements
    • Security Compliance
      • FAQ
      • GDPR
      • Security
    • Microsoft Azure Permissions
  • Glossary
  • 🎯PlaceOS Roadmap
  • 🆘PlaceOS Support
  • 👩‍💻PlaceOS Github
  • 📝PlaceOS Changelog
Powered by GitBook
On this page
  • Wireless
  • Data Collected
  • Device Certificates
  • Integration Requirements
  • Wired
  • Data Collected
  • Integration Requirements
Export as PDF
  1. How To
  2. Location Services

People Finding with Cisco Meraki on PlaceOS

How to locate people using Cisco Meraki

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

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.

  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

PreviousLocating Users on a NetworkNextPeople Finding with Juniper Mist on PlaceOS

Last updated 3 years ago