Field registration_idand message_idare not displayed, but if the user has previously been authenticated in your application, any fetch()server on your employee's work will include the credentials (and session information), which you can use to identify them.
If this does not work for your case, you can store the user / session information in IndexedDB.
Helpful information coming soon - probably Chrome 50 or 51 - based on the Web Push protocol. This is a little extra overhead and works to set up (necessary) encryption.
source
share