We don't want users changing url's to do something else. We also don't want other people capturing URL's not meant for them (presumably Windows authentication comes in here somewhere).
Any suggestions/links to articles on how to achieve this ?
Thanks,
Andy Mackie
There isn't any built-in functionality in Windows Workflow Foundation to generate "tamper-proof URL's". What you might want to consider doing is storing the details about the approval process to a database before sending the email notification. Then you could implement the authentication/authorization on the web site layer to make sure the user is authorized to approve/reject the data at hand.
James Conard
Architect Evangelist - Windows Workflow Foundation
http://www.WindowsWorkflow.net
http://blogs.msdn.com/jamescon
