cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

response time on splashAuthorizationStatus call

Highlighted
Here to help

response time on splashAuthorizationStatus call

Hello,

 

I've noticed something odd with this function. If I set the SSID authorization field to false I get a result back in ~1.5-2 seconds but if I set authorization to true I have to wait between 30-40 seconds for the response. Tested in postman with same results.

 

I can get round this by making my urlfetch calls async but its not ideal.

 

Thanks,


Dave

4 REPLIES 4
Meraki Employee

Re: response time on splashAuthorizationStatus call

Hi, I tried to replicate your scenario, but not getting the same results. 

 

Here are two curl commands that basically set authorization to false, and then to true. I output the time at the end of each command. 

 

I also verified sending the update, then calling the status for each update. The results were all pretty fast. 

 

 

$curl -X PUT \
>   https://n143.meraki.com/api/v0/networks/N_1234567890/clients/ff:ff:ff:aa:aa:aa/splashAuthorizationStatus \
>   -H 'Cache-Control: no-cache' \
>   -H 'Content-Type: application/json' \
>   -H 'Postman-Token: f3f9dbd6-9220-4e69-98d3-753409c3fd86' \
>   -H 'X-Cisco-Meraki-API-Key: be647eed304654BoGuS9ad07b7f7cef4c002de' \
>   -d '{
>   "ssids": {
>     "4": {
>       "isAuthorized": false
>     }
>   }
> }' \
> -w "\n Time Total: %{time_total}\n"
{"ssids":{"4":{"isAuthorized":false}}}
 Time Total: 0.320160
$
$
$curl -X PUT \
>   https://n143.meraki.com/api/v0/networks/N_1234567890/clients/ff:ff:ff:aa:aa:aa/splashAuthorizationStatus \
>   -H 'Cache-Control: no-cache' \
>   -H 'Content-Type: application/json' \
>   -H 'Postman-Token: f3f9dbd6-9220-4e69-98d3-753409c3fd86' \
>   -H 'X-Cisco-Meraki-API-Key: be647eed3046Bogus895ea9ad07b712345678' \
>   -d '{
>   "ssids": {
>     "4": {
>       "isAuthorized": true
>     }
>   }
> }' \
> -w "\n Time Total: %{time_total}\n"
{"ssids":{"4":{"isAuthorized":true,"authorizedAt":"2018-03-16 18:51:07 UTC","expiresAt":"2018-03-17 18:51:07 UTC"}}}
 Time Total: 0.493673

 

Here to help

Re: response time on splashAuthorizationStatus call

Hi, thanks for following up, your results are interesting and I replicated the tests:

 

 

$ curl -X PUT \
> https://n177.meraki.com/api/v0/networks/N_XXX592095176884YYY/clients/b4:f1:da:b3:23:9c/splashAuthorizationStatus \
> -H 'Cache-Control: no-cache' \
> -H 'Content-Type: application/json' \
> -H 'Postman-Token: 0f880d94-fd45-bfc5-96b9-ea710625fd10' \
> -H 'X-Cisco-Meraki-API-Key: XXXYYYZZZ' \
> -d '{
> "ssids":
> {"1":
> {"isAuthorized": "false"},
> "2":
> {"isAuthorized": "false"}
> }
> }' \
> -w "\n Time Total: %{time_total}\n"
{"ssids":{"1":{"isAuthorized":false},"2":{"isAuthorized":false}}}
Time Total: 1.272


$ curl -X PUT https://n177.meraki.com/api/v0/networks/N_XXX592095176884YYY/clients/b4:f1:da:b3:23:9c/splashAuthorizationStatus -H 'Cache-Control: no-cache' -H 'Content-Type: application/json' -H 'Postman-Token: 0f880d94-fd45-bfc5-96b9-ea710625fd10' -H 'X-Cisco-Meraki-API-Key: XXXYYYZZZ' -d '{
"ssids":
{"1":
{"isAuthorized": "true"},
"2":
{"isAuthorized": "true"}
}
}' \
> -w "\n Time Total: %{time_total}\n"
{"ssids":{"1":{"isAuthorized":true,"authorizedAt":"2018-03-19 11:54:52 UTC","expiresAt":"2018-03-26 11:54:52 UTC"},"2":{"isAuthorized":true,"authorizedAt":"2018-03-19 11:55:06 UTC","expiresAt":"2018-03-26 11:55:06 UTC"}}}
Time Total: 29.615

So I thought maybe its because I'm trying to authorize two SSIDs at once but even with one I get the same results:

 

$ curl -X PUT   https://n177.meraki.com/api/v0/networks/N_XXX592095176884YYY/clients/b4:f1:da:b3:23:9c/splashAuthorizationStatus   -H 'Cache-Control: no-cache'   -H 'Content-Type: application/json'   -H 'Postman-Token: 0f880d94-fd45-bfc5-96b9-ea710625fd10'   -H 'X-Cisco-Meraki-API-Key: XXXYYYZZZ'   -d '{
"ssids":
{"1":
{"isAuthorized": "true"}
}
}' -w "\n Time Total: %{time_total}\n"
{"ssids":{"1":{"isAuthorized":true,"authorizedAt":"2018-03-19 12:06:14 UTC","expiresAt":"2018-03-26 12:06:14 UTC"},"2":{"isAuthorized":true,"authorizedAt":"2018-03-19 11:55:06 UTC","expiresAt":"2018-03-26 11:55:06 UTC"}}}
 Time Total: 15.855

$ curl -X PUT https://n177.meraki.com/api/v0/networks/N_XXX592095176884YYY/clients/b4:f1:da:b3:23:9c/splashAuthorizationStatus -H 'Cache-Control: no-cache' -H 'Content-Type: application/json' -H 'Postman-Token: 0f880d94-fd45-bfc5-96b9-ea710625fd10' -H 'X-Cisco-Meraki-API-Key: XXXYYYZZZ' -d '{ "ssids": {"2": {"isAuthorized": "true"} } }' -w "\n Time Total: %{time_total}\n" {"ssids":{"1":{"isAuthorized":true,"authorizedAt":"2018-03-19 12:06:14 UTC","expiresAt":"2018-03-26 12:06:14 UTC"},"2":{"isAuthorized":true,"authorizedAt":"2018-03-19 12:06:42 UTC","expiresAt":"2018-03-26 12:06:42 UTC"}}} Time Total: 15.655

Maybe its something to do with size of network/number of clients?

 

Thanks,

Dave

 

Meraki Employee

Re: response time on splashAuthorizationStatus call

The number of clients is a good guess. Have you been able to test with a smaller network to rule that out? I'm interested as well.

Here to help

Re: response time on splashAuthorizationStatus call

This is a client in a network of 29 clients (last 24 hours) with 8 WAPs compared to the original network I was testing which had 559 clients and 50 WAPs.

 

$ curl -X PUT   https://n177.meraki.com/api/v0/networks/N_XXX592095176884YYY/clients/c4:61:8b:61:e4:9c/splashAuthorizationStatus   -H 'Cache-Control: no-cache'   -H 'Content-Type: application/json'   -H 'Postman-Token: a7742d3b-233d-5e6c-6fa9-3c01d3fddb62'   -H 'X-Cisco-Meraki-API-Key: XXXYYYZZZ'   -d '{
"ssids":
{"1":
{"isAuthorized": "true"},
"2":
{"isAuthorized": "true"}
}
}' -w "\n Time Total: %{time_total}\n"
{"ssids":{"1":{"isAuthorized":true,"authorizedAt":"2018-03-20 10:12:47 UTC","expiresAt":"2018-03-27 10:12:47 UTC"},"2":{"isAuthorized":true,"authorizedAt":"2018-03-20 10:12:50 UTC","expiresAt":"2018-03-27 10:12:50 UTC"}}}
 Time Total: 7.164

(I tested again and got 6.400 seconds).

 

So the time is just less than half for this smaller network, if network size definitely has something to do with it then the next step would be to determine if its number of WAPs or number of clients that is effecting it. Usually more WAPs = more clients, I think I'd have to wait until a weekend to have the same number of WAPs but less clients to test that theory.

 

Dave

Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.