ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Ws Wiki] Update of "FrontPage/WsFx/wssec" by WernerDittmann
Date Wed, 25 May 2005 14:22:17 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The following page has been changed by WernerDittmann:
http://wiki.apache.org/ws/FrontPage/WsFx/wssec

------------------------------------------------------------------------------
  with a SOAP implementation:
  
  ''Before you use WSS together with SOAP become familiar with the SOAP implementation you
use.''
+ 
+ Web Service Security usually ''can not'' be used just out of the box. People starting with
this shall have some good understanding of Web Services, how to use them, how they work. After
all, it is ''not'' the right stuff for ''Web Service newbies''.
  
  Most people use Axis together with WSS4J because WSS4J provides Axis handlers to simplify
the setup and deployment of Web Service security. In this case it is necessary to understand
the basic concepts of Axis.
  
@@ -66, +68 @@

   
  To develop a procduct that use WS Security I would perform several steps:
  
-  1.#0 Step 0: get a good understanding of you SOAP implementation (see remarks above)
+  1.#0 Step 0: get a good understanding of your SOAP implementation (see remarks above)
-  1. Then develop and set-up the Webservice (client and Server) __without__ any security.
Then test them to have a stable basis. In particular error cases.
+  1. Then develop and set-up the Webservice (client and server) __without__ any security.
Then test them to have a stable basis. In particular test the error cases.
-  1. define an installation procedure, e.g. using Ant or scripts, to reliably install the
product. This includes to copy all libraries, classes, jars, etc to their right places. 1.
Then re-check the classpathes used by your client and server. Many problems just pop up because
of a wrong classpath.
+  1. Define an installation procedure, e.g. using Ant or scripts, to reliably install the
product. This includes to copy all libraries, classes, jars, etc. to their right places. 1.
Then re-check the classpath used by your client and server. Many problems just pop up because
of a wrong classpath and other wrong path settings.
   
  After this works flawlessly then you can introduce security on top. WSS4J was designed that
you can introduce security to an existing Webservice environment without changing existing
source code. 
  

Mime
View raw message