>> why couldn't you implement it [OpenID] in a fat client if you so desired
Not saying I'm an expert with OpenID, but basically OpenID requires on
the ability for the user to be redirected to an OpenID provider site
for authentication. Example: I go to
www.mysite.com, and instead of a
login form, I just see:
"Login using your google, yahoo, myspace or xyz account"
I click on one of the above buttons. Now (depending on the provider) I
will get redirected to their website to enter my authentication info.
So if I'm a gmail user, I'd get redirected to a google login page.
After entering my info, I get redirected again back to
www.mysite.com.
Google returns some user token info identifying me now.
On a thick-client, the redirection isn't possible, I mean I could ask
for the user's authentication info directly, but I doubt many people
would trust doing that! The OpenID kind of relies on being able to
redirect the user and seeing in the address bar that they're
authenticating with their real provider, not some phishing site.
Thanks
On Jun 23, 3:26 am, gscholt <
gsch...@gmail.com> wrote:
> On Jun 23, 4:13 am, Mark <
mar...@gmail.com> wrote:
>
> > The bigger problem for me is that I am using GWT to make the web-app
> > portion of a larger app, which can also be accessed from iPhone/
> > Android/BB thick-clients. In those cases, I cannot useOpenID, and
> > would hate to support more than one login system. For example, my web
> > clients would useOpenID, Android/iPhone/BB clients would sign up
> > using an old-style new username/password system. Maintaining that
> > would be kind of annoying I think.
>
> Well, asking users to log in to the same system using different
> accounts seems wrong indeed :)
> Not knowing much aboutopenID, why couldn't you implement it in a fat