New name, same great feature - MS and MR SecurePort

[Minyi]

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 

Check out this new feature announcement post and learn more. 

[Inderdeep]

@Minyi : Awesome 

[rhbirkelund]

Since SecureConnect, now SecurePort, automatically detects Meraki AP, and allows it to obtain a certificate, and do 802.1x on the port. Out of curiosity, are we going to see the same behaviour in the future when connecting Meraki switches to each other? Are there talks about bringing this feature to switch uplink ports?

As far as I recall, Catalyst 1000 switches already do something similar.

[Minyi]

Hi @rhbirkelund, thanks for your feedback.  It’s our mission to make networking operations scalable and intuitive. We are always looking to grow, so please keep following along! 😊

[burnz]

Will the MS120 switches support this?

[Minyi]

Hi @burnz, SecurePort is currently not supported on MS120. Please see the documentation page for more information. 

[burnz]

Will it be supported there in the future?