Closed r-brown closed 5 years ago
Possibly even needed on first validation (in background) while calling PluginPass_Guard.validate(). User consent request can be enabled/disable by adding new parameter to the validate() function.
Once user accepted this, concent timestamp should be stored in the database - concent_ts
and not requested again until user revokes this (new issue needed here) or plugin is deregistered #15
Discussion notes from 16.07.19: As consent dialog is related to the UI, it is impossible to show it from within vendor's plugin - UI in the vendor's plugin is undefined and may even not exist. Instead, we agreed to describe mechanisms for the vendor how to redirect to the PluginPass admin area where the dialog is implemented and consent can be collected. In all other cases of PluginPass_Guard use, if consent is not yet collected, calls to the NetLicensing to be silently skipped, and unsuccessful validation to be returned (i.e. valid == false). Appropriate sentence is required in the PluginPass ToS, that puts the responsibility for consent collection on the vendor.
Two events in the PluginPass plugin can be still considered:
Validate
link
=> ask for consent before sed request to NetLicensingTODO / @r-brown - add to the docs
FAQ updated with the consent information - https://github.com/Labs64/PluginPass/wiki/FAQ#gdpr-how-to-update-user-consent
I updated the Wiki and FAQ with consent information.
Show popup to ask an explicit confirmation from the user before executing NetLicensing validation request.
Consent popup form Text:
Buttons: Agree / Cancel