Not using WebDE, but 2 things we have done in the past is simple IP
checking (only allowing access from specific/authorized IP addresses),
and also (AND or OR) using locking access to specific machines using a
hash of some machine attributes (typically Mac ID, Disk ID & such -->
but we have the advantage of having an ActiveX that grabs & encodes this
for us)

Whilst not quite the same as "the money market", we have clients that
operate with other liquid assets (Beer, Wine & Spirits) and some of the
information is extremely "sensitive" in the market, so needed to ensure
that if an employee left, no data went with them or was accessible
remotely!

Ross Ferris
Stamina Software
Visage > Better by Design!

>-----Original Message-----
>From: [email protected] [mailto:u2-users-
>[email protected]] On Behalf Of David Jordan
>Sent: Friday, 5 June 2009 12:40 AM
>To: U2 Users List
>Subject: Re: [U2] Web services
>
>I am trying to work out how to identify who the person is that is
>consuming a web service using the U2 web services developer.  I know
>techniques to do it in .Net.
>
>How do ensure that a person is authorized to consume that service.
>
>What approaches have others taken to tackle this.
>
>Regards
>
>David Jordan
>_______________________________________________
>U2-Users mailing list
>[email protected]
>http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to