There are a number of different ways to secure web services. You can use WSSE tokens to restrict access by username/password (for access control), XML signartures and/or XML encryption for message-level encryption, and of course running the service over HTTPS as a means of transport level encryption....
I really need more clarification about how you want to secure the service.
Weblogic's documentation is really quite good. I highly suggest you take a look at the following four web pages. They will help you to determine how you want to go about doing things:
Weblogic - The three types of security:
http://edocs.beasys.com/wl
How to configure security at the transport level (I suspect this is what you are looking for):
http://edocs.beasys.com/wl
How to configure security at the message level (this is mainly via implementation of WS-Security standards):
http://edocs.beasys.com/wl
How to configure access control as a means for securing web service calls (this is where you map username/passwords sent in the soap request header to principals in weblogic):
http://edocs.beasys.com/wl
Main Topics
Browse All Topics





by: shivaspkPosted on 2008-07-24 at 03:37:40ID: 22077605
You may like to go through this article
s/docs81/w ebserv/ sec urity.html #1053182
http://edocs.beasys.com/wl
when you meant certificate what certificate are u talking about ? many trust certificate are there in web services world, it it SSL or SAML ??