This section outlines how a client organisation can receive notification of the verification of an individual.
The client organisation can trigger a request for an individuals details from a redirection back to the client web site after a user centric verification is completed by the user, however, this will not capture verifications caused through the admin panel, nor will it capture users who get verified but do no press the “finish” button.
GreenID provides the ability for a client organisation to receive a notification to a specified URL whenever an individual becomes verified. The URL is called when an individual becomes verified, no matter where or when that verification occurred. This occurs for the Verified, Verified With Changes and Verified By Admin states. Optionally, it can also occur for the Pending Review state.
The URL will be called as a POST HTTP request with the person’s individual identifier included as a POST parameter. The identifier is also be appended as a URL parameter, for example if we configure http://www.example.com/notify.html as the notification URL then if the person with userId 123 is verified then the notification URL will be http://www.example.com/notify.html?userId=123. We can, if required, remove the URL parameter.
We recommend that when a client organisation receives the notification a call to the getVerificationResult web service method be made to check that the individual is truly verified. This avoids any risk of an attacker faking a call from greenID and tricking the client organisation into believing that a person has been verified.
Finally, the notification URL is set as a property for a client organisation and can only be configured or changed by greenID staff.