[
Lists Home |
Date Index |
Thread Index
]
The basic model is that the requirements of a service are expressed as
policy (WSDL can be thought of as one sort of policy in that it
indicates the required schemas used for request messages).
The security roadmap jointly authored by ms and ibm give clues to where
at least two parties in this world plan on going wrt security and
policy.
DB
> -----Original Message-----
> From: Don Park [mailto:donpark@docuverse.com]
> Sent: Wednesday, May 01, 2002 4:09 PM
> To: Xml-Dev
> Subject: [xml-dev] Google License Key
>
>
> Looking at Google's API closer, I noticed that license key is used as
an
> argument. The license key is obtained by:
>
> 1. HTTP POST
>
> Submit e-mail-address and chosen Google password
>
> 2. POP3
>
> Retrieve verification URL to verify e-mail address ownership
>
> 3. HTTP GET
>
> Confirm e-mail address ownership
>
> 4. POP3
>
> Retrieve license key
>
> While these four steps can be done manually to setup server-side
Google
> client or automatically for each client-side Google client, the
> registration process seems clunky and requires much human
intervention.
> Registration for server-side use can and will likely remain manual for
a
> while, but I feel that client-side registration process needs to be
> improved if client-side use cases for web services are to be realized.
>
> How are people planning to solve these sort of bootstrapping problems?
> The need to identify web service clients seems like a pretty basic
> requirement.
>
> Best,
>
> Don Park
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
|
