Saturday, February 18, 2012

[Rails] Custom authentication first & OmniAuth later. Newbie here.

Hi guys.

I'm having an idea that will be my first Rails app that I'll develop (i'm a newbie developer).

Thing is, I definitely want to have the login with Twitter/Google/Facebook functionality and I know that OmniAuth is a good library that achieves this. Thing is, I went through it's documentation and it was a little too advanced for me, so I want to first write an authentication system myself (normal signup,signin etc) and then, later on, after reaching a certain stage where the app is functional, implement the OmniAuth plugin. I wanted to ask however, is this possible? If I work on my app and write my authentication system (simple one, with has_secure_password), will then be a big headache to implement OmniAuth functionality?

What aspects will I have to change? Will I be able to integrate it in my current authentication system which would use my methods defined in a helper (ex. current_user(), logged_in?(user) etc.)?

Thanks in advance :) 

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/KsPtQoD07WoJ.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate