07-25-2021 05:06 PM
There is a small environment, 4 ap will enough. I prefer to use ppsk local as authentication method, but it's a annoyingly to update user on each ap individually, so any possible to config one of AP as ppsk server, the others AP will query it when authentication. Then I could update user info only once.
By the way, ppsk local is my favor, not ppsk cloud.
Solved! Go to Solution.
07-26-2021 01:32 PM
When using PPSK local, unfortunately you will need to update each AP when adding a new user, there is no way to designate one AP to be a type of PPSK server for the others.
08-02-2021 05:56 PM
If you’re anticipating frequent changes to your user database, and cloud based DB storage is not an option, then yes I’d suggest going with Radius instead.
08-02-2021 04:30 PM
The ppsk cloud have a drawback, if the wan link broken, then the whole ap system will down.
Then if going to implement use db on premise, the only choise is 802.1x+radius?
08-02-2021 04:19 PM
When using local DB storage for your PPSK user credentials, each AP acts as it’s own user database. You’ll have to update each AP (i.e. each PPSK independent database) each time you add or alter user credentials. The only way to avoid this would be to use cloud based storage for your PPSK credentials.
07-29-2021 04:13 PM
Than except ppsk cloud, how to implement ppsk’s user db on-premise as single source of truth?