Versions Compared

Old Version 14

changes.mady.by.user user-e1945

Saved on

compared with

New Version 15

changes.mady.by.user user-e1945

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagenone
titlebatch users csv
fullName,gsmNumber,email,securityModel,description Alessandro Bergamaschi,+391234567890,alessandro.bergamaschi@privatewavebergamaschi@acme.com,end-to-site,Personal account Luigi Rossi,+3932456753,luigi.rossi@privatewaverossi@acme.com,end-to-site,Personal account Marco Bianchi,+39432242342,mbianchi@gmail.com,end-to-site,Personal account Mario Colombo,+394325346546,colombo.mario@privatewavemario@acme.com,end-to-site,Personal account

...

The communication model of the licence can change quite a bit based on how user activated his account. Manual account creation leads the licence client on

Brand
brandclient
to communicate directly with PrivateWave
Brand
brandcompany
's licence server. Automatic Activated clients would communicated with their own
Brand
brandserver
, which plays the role of a proxy to PrivateWave
Brand
brandcompany
's licence server. In the latter case, the current licence is cached on
Brand
brandserver
and visible in account details.

Info
titleexample given

Let's say we have a

Brand
brandserver
named test1.privatewaveacme.com. This
Brand
brandserver
sent an Automatic Activation text message to the client PGSM_A. PGSM_A would ask to test1.privatewaveacme.com for its licence validation.

If it was a manual configured account, then it would ask its licence validation to the main licence server.

...