If you configure your ProMaster Master-Keying "PM8" and your customer's ProMaster Key Manager 8 "KM8" then you can send updates to your customer using the ProMaster publishing service instead of emailing the update files.
Faster for you.
Faster for your KM8 customer.
More secure than email, and the updates show up in KM8 without the KM8 customer needing to check their email.
The same underlying service that is used for ProMaster Master-Keying Mobile is used to deliver the data to KM8.
Your customer's KM8 is paired to your PM8 with a unique encryption key.
The data transferred to KM8 through this mechanism is identical to that which is send when you email an update file to the KM8 user.
KM8 publishing is available to PM8 users on all editions (Basic, Premium and Manufacturer).
PM8 version 8.16805.0.0 (15 Dec 2020) or later is required
It is a no-cost service that is available any time that your PM8 support and maintenance and your customer's KM8 support and maintenance are active.
There is no limit on the number of KM8 customers you may configure.
WH Software operates a publishing server through which published KM8 data is transferred. We host this service on Amazon EC2.
Each time you add a customer's KM8 to your PM8 you are given a time limited 12 character pairing code to enter into the customer's KM8 and this establishes the authenticity of that customer.
PM8 has three permissions to control who may configure publishing, who may configure publishing for Key Manager users and who may publish systems to Key Manager users.
You may configure multiple publishing relationships for a single customer if they have multiple KM8 installations. Likewise, a KM8 customer may have publishing relationships with multiple PM8 installations, which will be the case for customers that use multiple locksmiths.
All system information is encrypted to the specific customer's KM8 to which you sent it.
Each KM8 encryption key is transferred securely and can be decoded only by knowing the ephemeral pairing code.
At no time are the encryption keys available to us or anyone else so there is no way that the published system can ever be retrieved and read by any KM8 other than the one to which you sent it.
System information is encrypted using AES 256
Data transfer from PM8 to the publishing server and then to the customer's KM8 is encrypted again by using HTTPS data transfers.
There are three permissions in PM8 that control who may perform each part of the KM8 publishing process.
These are at the bottom of the security group list of permissions in the group Publishing.
| Permission | Description |
|---|---|
| Configure publishing | Allows PM8 to be configured as a publisher, thereby allowing devices to be configured. |
| Configure publishing for Key Manager users | Allows KM8 relationships to be created ready to receive systems. |
| Publish systems to Key Manager users | Allows systems to be sent to KM8 from the Export To Key Manager screen. |
On the Setup and Admin menu choose Mobile services then choose Configure publishing.
If it is not already checked, turn on the option Allow publishing service to be used.
Select the Key Manager tab.
You may choose to alter the setting for 'System life' from the default more conservative value of 7 days to one of the longer values.
Click OK to save.
Once publishing is configured you should not need to return to this screen.
This is the part where you establish the publishing relationship with your KM8 user and securely transfer the encryption key. You will do this for each of your KM8 customers who want to use the publishing service.
The KM8 customer must be ready to receive the code from you - the code lasts for a short time so there is no point in trying to do this process until the KM8 customer is ready.
System menu choose Configure Key Manager publishing.If there is already a publishing relationship, do not create another one unless you want to send systems from PM8 to more than one KM8 installation for the customer.
Click Add to add a publishing relationship. The relationship is called 'Default' and there is no reason to change this unless the customer has multiple publishing relationships with you (i.e., Multiple KM8 installations at multiple sites)
When you click OK, a 12 character pairing code is generated and displayed.
Read this pairing code to the KM8 user so they can type it directly into their KM8.
Do not email the pairing code.
First, it has a very short life span, but more important it is used for the transfer of the encryption key and should be used immediately and not sent in any way that it may be intercepted.
After the KM8 customer has entered the pairing code, you may dismiss it from your screen by clicking OK.
Next, the Key Manager Publishing System Authorities window is shown. Put a check on all systems that may be sent to the KM8 customer using the relationship you have created, then click OK to save it.
Key Manager pairing is done
That is the publishing relationship with the customer's KM8 complete.
You need to return to this setup only in the event that you want to alter the customer relationship, such as making additional systems available. Everything else you need to know about publishing data to KM8 is done as part of the normal process of sending the KM8 customer a system update, and we will talk about that now.
This is the process you will do each time you make a change to the master-key system and want to send it to your KM8 customer.
System menu choose Export to Key Manager.ProMaster Key Manager 8Ready to create export, turn on the option Use the Key Manager publishing service to send the update.Finish to send the update to the customer.You've done it.
That is all you have to do - even easier than emailing the update file to the customer.
The customer's KM8 will show the update as being available after a short time. Depending on what the KM8 user is doing it may appear immediately or after a few minutes since KM8 strikes the balance of checking for updates without too much aggressive internet activity.