You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Jinghua Gu <eg...@cisco.com> on 2002/04/17 20:53:24 UTC

Authentication in AXIS

How can the authentication be done in AXIS? Any examples?
Did anybody make the example in security directory work?

Thx,
Emily


RE: Authentication in AXIS

Posted by Brenda Coulson <bc...@cysive.com>.
just a quick clarification on my notes below - you do not actually need to
compile ClientSigningHandler.java if you use the default deploy/undeploy
command files. This also means that you do not need to add it to your
web-inf/classes/... directory.

-----Original Message-----
From: Brenda Coulson [mailto:bcoulson@cysive.com]
Sent: Wednesday, April 17, 2002 4:01 PM
To: axis-user@xml.apache.org
Subject: RE: Authentication in AXIS


Funny you should ask - I just got it working a few moments ago. The security
sample makes use of the Digital Signature extension to SOAP and does not
address authentication. It relies on several other packages for it to work
but I was successful. Here are the other packages it requires

- XML Security package from Apache
- JCE provider (required by XML Security). Check out www.bouncycastle.org
- The following libs from the XML Security distribution are required in your
web-inf/lib directory:
	1. jakarta-log4j-1.2beta2.jar (to replace the log4j-core.jar from Axis
distribution)
	2. xml-apis.jar
	3. xmlParserAPIs.jar
	4. xercesImpl.jar
	5. xmsec.jar
	6. xalan.jar
- Add The JCE provider classes both to your client-side classpath as well as
the web-inf/lib directory. Assuming you are using Bouncy Castle as your
provider, this requires you to actually create the jar as the distribution
comes as a directory of class files.
- Compile the java source files. This requires having all of the above
mentioned jar files in your compiler classpath in addition to the Axis jar
files with the exception of the log4j-core.jar file - this has been replaced
by jakarta-log4j-1.2beta2 as mentioned above.
- Once all the files are successfully compiled, copy the following files to
your web-inf/classes/samples/security directory
	1. keystore.jks
	2. LogHandler.class
	3. Service.class
	4. SignedSOAPEnvelope.class

Once you have done all of this, you should be able to run the following
commands from the security directory:
deployit.cmd
testit.cmd
undeployit.cmd

regards-
brenda
-----Original Message-----
From: Jinghua Gu [mailto:egu@cisco.com]
Sent: Wednesday, April 17, 2002 2:53 PM
To: axis-user@xml.apache.org
Subject: Authentication in AXIS


How can the authentication be done in AXIS? Any examples?
Did anybody make the example in security directory work?

Thx,
Emily


RE: Authentication in AXIS

Posted by Brenda Coulson <bc...@cysive.com>.
Funny you should ask - I just got it working a few moments ago. The security
sample makes use of the Digital Signature extension to SOAP and does not
address authentication. It relies on several other packages for it to work
but I was successful. Here are the other packages it requires

- XML Security package from Apache
- JCE provider (required by XML Security). Check out www.bouncycastle.org
- The following libs from the XML Security distribution are required in your
web-inf/lib directory:
	1. jakarta-log4j-1.2beta2.jar (to replace the log4j-core.jar from Axis
distribution)
	2. xml-apis.jar
	3. xmlParserAPIs.jar
	4. xercesImpl.jar
	5. xmsec.jar
	6. xalan.jar
- Add The JCE provider classes both to your client-side classpath as well as
the web-inf/lib directory. Assuming you are using Bouncy Castle as your
provider, this requires you to actually create the jar as the distribution
comes as a directory of class files.
- Compile the java source files. This requires having all of the above
mentioned jar files in your compiler classpath in addition to the Axis jar
files with the exception of the log4j-core.jar file - this has been replaced
by jakarta-log4j-1.2beta2 as mentioned above.
- Once all the files are successfully compiled, copy the following files to
your web-inf/classes/samples/security directory
	1. keystore.jks
	2. LogHandler.class
	3. Service.class
	4. SignedSOAPEnvelope.class

Once you have done all of this, you should be able to run the following
commands from the security directory:
deployit.cmd
testit.cmd
undeployit.cmd

regards-
brenda
-----Original Message-----
From: Jinghua Gu [mailto:egu@cisco.com]
Sent: Wednesday, April 17, 2002 2:53 PM
To: axis-user@xml.apache.org
Subject: Authentication in AXIS


How can the authentication be done in AXIS? Any examples?
Did anybody make the example in security directory work?

Thx,
Emily