We would like to inform you that the MS and MR SecureConnect feature, which enables the secure automation of MS switch ports configuration connected to MR access points, is now SecurePort. This name change will simply allow us to clarify the feature functionality.
New name, same great feature
The functionality of the feature remains unchanged on the dashboard. However, please note that this name change will impact the following API end-point, where customers will need to modify the key ‘secureConnect’ to ‘securePort’ on their API calls:
1.https://developer.cisco.com/meraki/api-v1/#!get-network-settings
2.https://developer.cisco.com/meraki/api-v1/#!get-device-switch-ports-statuses
What is SecurePort?
SecurePort automates the process of securely provisioning Meraki MR Access Points when directly connected to switch-ports on Meraki MS Switches, without requiring a per-port configuration. With this feature, IT teams no longer need to claw their way through multiple disparate dashboards and manual, complex tasks to secure their networks. In just a few clicks on a single dashboard, network professionals (like you) can implement a security posture that reliably protects every layer of the network. It effectively secures switch ports and automates device configurations, eliminating potential configuration errors and downtime.
How does it work?
When a SecurePort-capable MR access-point is connected to an MS switch configured for SecurePort, the switchport's configuration is automatically modified to implement traffic and security restrictions on the MR access-point, while still allowing it to communicate with the Meraki Dashboard. The access-point is provided with an identity certificate which it uses to validate itself as an MR belonging to the same Dashboard Organization before it is authorized to use the network.
The SecurePort status of a switchport is reported to users with a new port-state indicator on the switch's mimic panel, and via state-specific banners in the port details view.
A configuration override by SecurePort is applicable to a port only while the MR access-point remains connected to it. The user-defined config for the port remains accessible and can be modified even while SecurePort is active on the port.
Learn more
Read more about SecurePort here.