OpenID and user component
Posted: Sun Feb 22, 2009 8:33 pm
I have spent about a week implementing a user component for an application. This component provides all of the 'user' type services, such as login, logout, profiles, register, password reset, etc.
I would like to have users to login using OpenID but at the same time, I would still like them to register as the details collected are useful. I'm trying to understand where OpenID fits into the equation. Is the point behind OpenID to prevent users from having to repeatedly signup/register at every site or is it just to (de)centralize authentication? OpenID providers like SF or Yahoo, etc...I assume users are expected to register for an OpenID account with one of them?
Does OpenID provide an API to allow my application to query for details like city, address, etc?
In order to accomplish what I desire, would I have to start my own OpenID provider service?
Cheers,
Alex
I would like to have users to login using OpenID but at the same time, I would still like them to register as the details collected are useful. I'm trying to understand where OpenID fits into the equation. Is the point behind OpenID to prevent users from having to repeatedly signup/register at every site or is it just to (de)centralize authentication? OpenID providers like SF or Yahoo, etc...I assume users are expected to register for an OpenID account with one of them?
Does OpenID provide an API to allow my application to query for details like city, address, etc?
In order to accomplish what I desire, would I have to start my own OpenID provider service?
Cheers,
Alex