In our system a client can initiate a process that invokes a web service. After the process is done the client is presented with a link to the generated static HTML page to display the results of the requests.
The link utilizes SSL protocol to encrypt contents. However, we have concern that someone might intercept the actual URL, and access the same data. Because the link is generated and points to a different domain it is very difficult to implement proper security, especially since customer might run this process many times during the day.
Example:
Customer initiates request at https://<websiteABC>/request.aspx
The requests calls a web service on another domain, which in turn generates a static HTML file and returns URL to the request page
Customer is presented with URL to access the page at https://<websiteXYZ>/2394839839483489348394024802480204840/data.htm
...
Go to the complete details ...