Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add frontizo as productType in Network #130

Open
TimVerheul opened this issue May 22, 2023 · 4 comments
Open

Add frontizo as productType in Network #130

TimVerheul opened this issue May 22, 2023 · 4 comments

Comments

@TimVerheul
Copy link

TimVerheul commented May 22, 2023

Hi,
Meraki recently implemented something new which is called "Secure Connect". This is a network on it's own. My client uses this.
The productType of this is "frontizo". Currently I get a parse error because this value is not in the list of productType.

image

My request is to have the value "frontizo" added to the file Meraki.Api/Data/ProductType.cs

The code that needs to be added would be:

[EnumMember(Value = "frontizo")]
Frontizo,

@danielabbatt @stashjones

@danielabbatt
Copy link
Contributor

Hi @TimVerheul - thanks for raising this.
Could you double check that this is a correct value being returned by the API as in the past we have seen values like this as part of early release/beta and it wasn't intentional and should have been a different value. I don't see anything in the API documentation relating to this either so can't confirm it's correct, even though it's clearly what is being returned for you.
Please reach out to Meraki to confirm that this value for productTypes is correct for the SecureConnect (now SecurePort I believe) networks.

@TimVerheul
Copy link
Author

Hi @danielabbatt. Thank you for replying.
Indeed it could be an early release/beta. SecureConnect (not SecurePort) is a new product of Cisco and it's their SASE solution. It looks like that Frontizo is the original company that is aquired by Cisco (there is a Frontizo team working at Cisco upon research).

We checked with Cisco but we have not received any confirmation that they are planning a name change in the future.

@danielabbatt
Copy link
Contributor

@TimVerheul
Copy link
Author

@danielabbatt it looks like this field has been renamed to "secureConnect" in the api response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants