wood burning stoves 2.0*
The moose likes Web Services and the fly likes Securing Web Services Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Securing Web Services" Watch "Securing Web Services" New topic
Author

Securing Web Services

Russell Ray
Ranch Hand

Joined: Apr 25, 2005
Posts: 116
I am hoping others in this group can provide me some solid feedback concerning web services and securing them.

The task at hand is we have two application servers--WebLogic and WebSphere. We are looking for a uniform approach.

We have instituted a userNameToken approach within the Header, but all the examples we see are clear text examples. We would like to encrypt the password. This leads us to the next level of security and how it should be implemented. My initial design is for the handlers to encrypt and decrypt the password using a private key.

I would like to hear from others who have used encryption and how they tackled the process........

Thanks in advance
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 39578
    
  27
Before you tackle encryption, have you looked at using a digest password instead of cleartext? It's just as easy to set up, although your Handler oin the server will need to work a bit differently.


Ping & DNS - updated with new look and Ping home screen widget
Russell Ray
Ranch Hand

Joined: Apr 25, 2005
Posts: 116
okay, I looked at message digest briefly and thought this was good. Can you point me in the right direction? I need examples.......
Russell Ray
Ranch Hand

Joined: Apr 25, 2005
Posts: 116
duh........google it silly.......
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 39578
    
  27
You may have figured it out by now, but in case you're using something like WSS4J, instead of using
<parameter name="passwordType" value="PasswordText"/>
you would use
<parameter name="passwordType" value="PasswordDigest"/>

while in your server-side PasswordCallback, you need to set the password that you're expecting for the user, instead of getting it. That's because a digested password can't be undigested into cleartext, but the expected password needs to be digested as well.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Securing Web Services
 
Similar Threads
securing webapplication
Securing Web Services
Programming .NET Web Services - Release Announcement - O'Reilly
Secure Web Services
encrypt password