Joe Gregorio wrote:
> How should authentication and security be handled? Are Basic and Digest good enough?
An alternative question would be, if we cook up a custom solution, would it be any easier to code, deploy, use or be any more secure ?
I see no reason to specify anything more than use HTTP's existing options for authentication, confidentiality and tamper proofing as required. With perhaps something that points out guidelines and/or best practices.
http://www-106.ibm.com/developerworks/library/ws-trust/#Challenges http://www-106.ibm.com/developerworks/library/ws-trust/#PasswordBasedKeyExchange
Cheers Simon www.pocketsoap.com