[
Lists Home |
Date Index |
Thread Index
]
Client Certificates over SSL is one way that people are doing this in
production today. Some sort of signing procedure with a trusted
certification authority will probably be the continuing model, although
there will probably be differing classes of certification for different
needs (for example, passport doesn't really verify your identity, it
just identifies that the mailbox exists, regardless of what name you
made up).
Joshua Allen
Microsoft WebData XML
425.705.7857
> -----Original Message-----
> From: Don Park [mailto:donpark@docuverse.com]
> Sent: Wednesday, May 01, 2002 4:09 PM
> To: Xml-Dev
>
>
> 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>
|
