Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <7315.82.161.31.23.1222722524.squirrel@webmail.xs4all.nl>
Date: Mon, 29 Sep 2008 23:08:44 +0200 (CEST)
Subject: Re: Internal/external operations
From: "Richard" <rabbuhl@xs4all.nl>
To: axis-user@ws.apache.org
User-Agent: SquirrelMail/1.4.11
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Keith,

> What do u mean by external and internal WS-Clients?

External web service clients would be our customers which we give a WSDL
so they can call our web service.  Ideally, we could indicate which
operations they are allowed to call but they are limited to the operations
which are for external use.

Internal web service clients would be our web application which calls
operations which are intended for internal use.  The web application might
also call operations which are intended for external use as well.

> Well, If you use something like username token authentication on your
> service, you could access the username of the caller from within your web
> service and thus vary the action you need to perform. This is just
> one way of doing it though.

Customers can use the same username to access the web service either via a
web services client outside of the firewall or by using the web
application which calls the web service from inside the firewall.

Thanks,
Richard

> Hi Richard,
>
> See comments inline.
>
> On Mon, Sep 29, 2008 at 11:09 PM, Richard <rabbuhl@xs4all.nl> wrote:
>
>> Perhaps someone can help me with two questions:
>>
>> 1.  Is it possible to create a web service where most operations can be
>> called by external ws clients but some operations can be called only by
>> internal ws clients.
>
>
> What do u mean by external and internal WS-Clients?
>
>>
>>
>> 2.  The behavior of an operation needs to differ slightly depending on
>> whether an operation is called internally or externally--this can be
>> done
>> by checking the value an attribute or an element.  Is there a more
>> transparent way to determine the ws caller so that behavior such as how
>> to
>> connect to the database can differ slightly.
>
>
> Well, If you use something like username token authentication on your
> service, you could access the username of the caller from within your web
> service and thus vary the action you need to perform. This is just one way
> of doing it though.
>
> Thanks,
> Keith.
>
>>
>>
>> Thanks,
>> Richard
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org