search

couch2code / couch2code.com

Couch to Code - A social application that inspires developers to continue to practice to push
5 stars 1 forks source link

Registration/Login Methods #3

Closed jsouthard closed 10 years ago

jsouthard commented 10 years ago

Is there a convenient framework/module that does a lot of the heavy lifting for performing authentication via the different proposed identity providers or will each one need an individual implementation?

Is it correct to assume that there will be common registration elements (e.g. filling out profile details) that are then tied to the user's chosen authentication method?

Said differently, will the tasks be:

I imagine setting up that way would allow reuse of the profile edit view for both registration and profile modification.

twilson63 commented 10 years ago

Yes firebase handles all the above, with email auth you just have to create the forms, but fire base handles the rest very well. I have created the registration and login template, I just have to add the firebase simple login js module

Thx

Tom

Sent from my iPad

On Feb 22, 2014, at 1:06 PM, James Southard notifications@github.com wrote:

Is there a convenient framework/module that does a lot of the heavy lifting for performing authentication via the different proposed identity providers or will each one need an individual implementation?

Is it correct to assume that there will be common registration elements (e.g. filling out profile details) that are then tied to the user's chosen authentication method?

Said differently, will the tasks be:

Login: e-mail/password Login: Twitter API Login: Facebook API Login: GitHub API Login: Persona Profile setup/creation (where first login requires an initial profile setup I imagine setting up that way would allow reuse of the profile edit view for both registration and profile modification.

— Reply to this email directly or view it on GitHub.

twilson63 commented 10 years ago

I usually keep the registration and login separate from profile edit, very much like twitter, this allows for easy sign up, then the user can fill in the details later. We can leverage many different registration paths this way, we can also pull profile info from those paths, like if registered with twitter get avatar from twitter, if registered from email, get avatar from gravitar

Make sense?

Sent from my iPad

On Feb 22, 2014, at 1:06 PM, James Southard notifications@github.com wrote:

Is there a convenient framework/module that does a lot of the heavy lifting for performing authentication via the different proposed identity providers or will each one need an individual implementation?

Is it correct to assume that there will be common registration elements (e.g. filling out profile details) that are then tied to the user's chosen authentication method?

Said differently, will the tasks be:

Login: e-mail/password Login: Twitter API Login: Facebook API Login: GitHub API Login: Persona Profile setup/creation (where first login requires an initial profile setup I imagine setting up that way would allow reuse of the profile edit view for both registration and profile modification.

— Reply to this email directly or view it on GitHub.

jsouthard commented 10 years ago

I was certainly advocating for keeping them modular enough that they could readily be linked or not.

I can see the benefit of not linking the profile editing to the registration process, decreases barrier to entry among others.

On Feb 22, 2014 1:30 PM, "Tom Wilson" notifications@github.com wrote:

I usually keep the registration and login separate from profile edit, very much like twitter, this allows for easy sign up, then the user can fill in the details later. We can leverage many different registration paths this way, we can also pull profile info from those paths, like if registered with twitter get avatar from twitter, if registered from email, get avatar from gravitar

Make sense?

Sent from my iPad

On Feb 22, 2014, at 1:06 PM, James Southard notifications@github.com wrote:

Is there a convenient framework/module that does a lot of the heavy lifting for performing authentication via the different proposed identity providers or will each one need an individual implementation?

Is it correct to assume that there will be common registration elements (e.g. filling out profile details) that are then tied to the user's chosen authentication method?

Said differently, will the tasks be:

Login: e-mail/password Login: Twitter API Login: Facebook API Login: GitHub API Login: Persona Profile setup/creation (where first login requires an initial profile setup I imagine setting up that way would allow reuse of the profile edit view for both registration and profile modification.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com/couch2code/couch2code.com/issues/3#issuecomment-35810113 .