[OpenID] How can adopt the openid in mobile web envirionment
Guido Sohne
guido at sohne.net
Tue Apr 10 17:02:52 UTC 2007
On 4/10/07, Paul Madsen <paulmadsen at rogers.com> wrote:
> Guido, I see how a phone's camera capabilities are relevant for
> capturing such a 2D code (e.g. from a screen), but not for input, i.e.
> if the phone were to submit the URL to a server, it surely wouldn't be
> sending a semacode representation would it?
Software on the phone decodes the semacode and it is the URL that is
passed to the server. Initiating authentication would be as simple as
taking out your wallet and taking a picture of your semacode.
The bigger problem is whether the user will have access to the
semacode when wanting to do authentication and the 'wallet' idea is
clumsy I think. But with respect to your question, it does send the
semacode representation (which is the URL encoded in the semacode, and
would in this case be the OpenID URL of the user).
-- G.
More information about the general
mailing list