[EMAIL PROTECTED]
Sent: Monday, December 22, 2003 9:04 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Authentication Information in SOAP Header
Here is what I am specifically doing in my code.
// creating the service locator obj
TestTransactionService serviceLoc
etter [mailto:[EMAIL PROTECTED]
Sent: Monday, December 22, 2003 9:26 AM
To: [EMAIL PROTECTED]
Subject: Re: Authentication Information in SOAP Header
Hello there,
I don't know the details of your code, but I suppose that you have to cast
"transaction" to Stub or TestTransactionSoapBindingS
ntime, it will be of type
TestTransactionSoapBindingStub as well).
Kind regards,
Arno Huetter
-Ursprüngliche Nachricht-
Von: Pani, Gourav [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 22. Dezember 2003 15:04
An: '[EMAIL PROTECTED]'
Betreff: RE: Authentication Information in SOAP Header
Here
/code
snippet/reference on how to set authorization data to the soap envelope
header using Handlers?
Thanks.
-Original Message-
From: Pani, Gourav [mailto:[EMAIL PROTECTED]
Sent: Monday, December 22, 2003 9:04 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Authentication Information in SOAP H
Here is what I am specifically doing in my code.
// creating the service locator obj
TestTransactionService serviceLocator = new
TestTransactionServiceLocator();
// creating and executing the transaction
TestTransaction transaction = serviceLocator.getFastWebService
:[EMAIL PROTECTED]
Sent: den 4 december 2003 14:37
To: [EMAIL PROTECTED]
Subject: Re: Authentication - Could anyone help me plzzz
most time ( i think mor than 80 % ) webservice communication is through html and html also produces a header ( you can
most time ( i think mor than 80 % ) webservice communication is through html and html also produces a header ( you can also see the servlet as a spezal kind of handler ).
So i think handler things not needed to descriped in WSDL.
Am Don, den 04.12.2003 schrieb Yogesh Pant um 14:31:
How does html header come into picture of web service communication?
Harald Pollak <[EMAIL PROTECTED]> wrote:
as you said:Handlers providing a addinal layer to the webservice, you also don't descripe the HTML-Header in the wsdlAm Don, den 04.12.2003 schrieb Yogesh Pant um 14:12:
The header
I
guess you mean HTTP, not HTML. Thank god for three and four letter acronyms...
Regards,
Christer
-Original Message-From: Harald Pollak
[mailto:[EMAIL PROTECTED]Sent: den 4 december 2003
14:37To: [EMAIL PROTECTED]Subject: Re:
Authentication - Could anyone
or servlet container security of the type that I have
> > described in my original message?
> >
> > -Original Message-
> > From: Aaron Hamid [mailto:[EMAIL PROTECTED]
> > Sent: 04 December 2003 13:20
> > To: [EMAIL PROTECTED]
> > Subject: Re:
is for servlet container security of the type that I have
described in my original message?
-Original Message-
From: Aaron Hamid [mailto:[EMAIL PROTECTED]
Sent: 04 December 2003 13:20
To: [EMAIL PROTECTED]
Subject: Re: Authentication - Could anyone help me plzzz
I can't answer why th
[mailto:[EMAIL PROTECTED]
Sent: 04 December 2003 13:20
To: [EMAIL PROTECTED]
Subject: Re: Authentication - Could anyone help me plzzz
I can't answer why the admin app would be failing. But if you want
application-level security you are basically on your own. You can try
to use the ws-sec
9
*To:* [EMAIL PROTECTED]
*Subject:* Re: Authentication - Could anyone help me plzzz
as i have understood:
The handler is a thing befor the WS ( not part of it ) and the WSDL
describe the WS - so elements only used in handler shouldn't and
couldn't be described in Webservice,
as you said:
Handlers providing a addinal layer to the webservice, you also don't descripe the HTML-Header in the wsdl
Am Don, den 04.12.2003 schrieb Yogesh Pant um 14:12:
The header element is a part of SOAP message. As per web services specification, message description should be inclu
axis authentication/security, I would appreciate info on this
Thanks
Tony
-Original Message-
From: Harald Pollak [mailto:[EMAIL PROTECTED]
Sent: 04 December 2003 12:59
To: [EMAIL PROTECTED]
Subject: Re: Authentication - Could a
, if anyone knows any articles on axis
authentication/security, I would appreciate info on this
Thanks
Tony
-Original Message-
From: Harald Pollak
[mailto:[EMAIL PROTECTED]
Sent: 04 December 2003 12:59
To: [EMAIL PROTECTED]
Subject: Re: Authentication - Could
anyone help me
The header element is a part of SOAP message. As per web services specification, message description should be included in the wsdl document.
Handler is a mechanism used by Axis to provide an additional layer for processing incoming/outgoing message. In any case wsdl should be a complete descrip
as i have understood:
The handler is a thing befor the WS ( not part of it ) and the WSDL describe the WS - so elements only used in handler shouldn't and couldn't be described in Webservice, so you can only tell your opposit what to do in document the webservice in hardware ways ( email, lett
Hello ppl,
I have got a custom authentication handler. It authenticates the incoming message very well.
My problem is that the generated wsdl has no mention of header elements at all. HOW DO I ACHIEVE THIS?
Do I need to configure the deployment descriptor a little bit more?
Please help.
Tha
Hi Tony,
If you wanted to use application level security, maybe try using
ws-security (encryption and signatures) using handlers in axis. You will
find quite a few links on
this in the axis mailing list.
You may have to design the authentication protocol and then implement this
using ws-security.
H
you can write own handlers and put it into the chain for the webservice.
This handler kann check the authentication and give access to the WS or rize a AxisFault
this is the simplest way to do such things.
Harry
Am Don, den 04.12.2003 schrieb Tony Vieitez um 11:08:
Hi
Hi,
If you look at the authentication handler and authorization handler. the way
they implemented are according to the same concept.
But if want the authentication to your flexibility it is easy to write your
own handler.(You can refer the current handler codes and may change it for
your usage).
I
Implement your own handlers.
I've got users and groups stored in an XML file.
To deal with groups I had to make custom implementations of
org.apache.axis.security.*
stephen
Karthik krishnamurthy wrote:
Hi,
I'm trying to implement the Authentication and Authorization features in
Axis.
1. Is the
Why not use with AXIS SOAP Message Handler the WS-Security
Password-based Authentication mechanism and/or WS-Security
with SAML Assertion.
Are there any plans to support WS-Security for AXIS SOAP
Message exchanges either by Apache/AXIS or by IBM?
Benjamin Tomasini <[EMAIL PROTECTED]> wrote
2003 15:18
> Aan: [EMAIL PROTECTED]
> Onderwerp: Re: Authentication
>
>
> Consider enforcing that in your servlet container or web server.
>
> Ben
>
> On Wed, 2003-06-18 at 09:09, Lanigan, Ronan wrote:
> > Hi,
> >
> > I want to perform some Auth
Or rather in your firewall if you have one...
Greetz
Leo
-Oorspronkelijk bericht-
Van: Benjamin Tomasini [mailto:[EMAIL PROTECTED]
Verzonden: woensdag, juni 2003 15:18
Aan: [EMAIL PROTECTED]
Onderwerp: Re: Authentication
Consider enforcing that in your servlet container or web server
Consider enforcing that in your servlet container or web server.
Ben
On Wed, 2003-06-18 at 09:09, Lanigan, Ronan wrote:
> Hi,
>
> I want to perform some Authentication for my Web Service. I have a list of
> machine names e.g. devmachine.xxx.com and I only want to service requests
> that come fro
>Sax and xercesI've been having problems getting authentication to work
>from non-Java clients (e.g. VB6, etc).
I've gotten digest authentication to work from a legacy, non-Java client.
I let TomCat (or whatever app server you prefer) take care of all the
details via the usual HTTP methods, and i
erver side to
authenticate. I assume that I will be able to write some server side Java to
check and authenticate this username and password? I'm also just starting
with Axis so I might be missing something very simple here.
Thanks
Xander
- Original Message -
From: "Phillip Rho
What do you mean by authentication not working?
Axis is able to use the servlet container's session tracking mechanism, so
it should return a cookie to the client. Can you run an http sniffer and
see if the cookie is being returned to your client? Is the client sending
the cookie in the http
Title: Message
Using
the Connector Property means that you rely on the HTTP basic authentication
mechanism, meaning that you will not be the one validating the user and password
but your HTTP Server/Servlet container will do it for you. According to which
HTTP Server/Servlet container you ar
RE: Authentication and digital signaturesNaresh,
"It appears that these classes don't exist in Axis beta 2. The equivalent is
probably:
org.apache.axis.client.Call.setUsername(uid);
org.apache.axis.client.Call.setPassword(password); "
The examples from the book come
Title: RE: Authentication and digital signatures
Dan,
Thanks for all this wonderful information. I downloaded the examples and have couple of questions about basic authentication.
Example 1 sets that username and password as follows:
org.apache.axis.client.ServiceClient.set
Authentication and digital signaturesNaresh,
Basic Authentication and SSL can be handled directly by your web server.
The following are links to the relevant Tomcat How-To.
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/realm-howto.html
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/ssl-howto.
Hi Naresh,
You may find the following sketchy description helpful:
Authentication is about proving to someone that you are who you claim to be.
In PKI world, this would mean possession of the private key corresponding to
a X509 certificate having the public key issued by a well known CA. Usual
:[EMAIL PROTECTED]]
Sent: Wednesday, April 17, 2002 4:01 PM
To: [EMAIL PROTECTED]
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
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 17, 2002 4:01 PM
To: [EMAIL PROTECTED]
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
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 Secu
38 matches
Mail list logo
