This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
AFAIK, it's possible to encrypt your entire message using Axis2 and Rampart. However, when I specify UsernameToken and Encrypt actions, it only encrypts the body. I'd like for the entire message to be encrypted, including the user/pass header section.
The encryption will just be for the SOAP body, not the header where the username info is. If you want to transmit the password securely you can send it hashed (a.k.a. digested). That's actually the default if I remember correctly; check the passwordType tag.
But sending the username in cleartext shouldn't be a security risk, or is it?
Joined: Sep 24, 2008
Bah. I had a response all typed out and then FF crashed on me.
Anyways, yes, the digest mode is the default. I was just wondering if the digest setup is specific to Axis2/Rampart. From what I read here, it says that the digest is created by the following.
Doesn't the SHA part require both sides to have the key? Since it's sending over the nonce and created, it seems like the digest wouldn't be very secure.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com