Parties: Seal service provider (SSP) and customer website
1. The software (CGI scripts?) resides on a shared host computer.
2. The seal image is in a webpage at customer website and is also a link.
See [url removed, login to view] for examples.
3. Website visitor clicks on the seal image and the request goes to a secure server (CGI scripts?) operated by SSP (via shared hosting).
4. The server recognizes the source of the request (URL) as being authentic (from the SSP database) and returns a webpage. If the source isn’t authentic, the server returns a different webpage.
5. System must be reasonably secure and hacker proof.
Code the CGI scripts to create this system including the DB coupling to a MYSQL database and the link code for the seal on customer website.
(The image itself will be installed in the webpage by the customer website and should not be delivered by the authentication system.)
The SSP is publishing this request.