crynobone
commented
12 years ago why would i show a registration form after they already signed up over twitter? same goes for the action_login - why would i want a login/password field if im using twitter?!
You can ignore it if you wish to, however do take note that while we would expect Twitter, Facebook or other Provider to provide all the user information there are certain information which is not available. Twitter for example never allow e-mail address to be sent through OAuth, Facebook only return username if it's presented.
In most use case I see today, even with OAuth most web service today still include a normal registration and login.
also, how do i know on the action_register if the user is coming from oauth or if he just submits the form under that route?
Check for Session::get('oauth') to retrieved user information passed by Twitter (or other provider).
can you create an example that authentificates only by oauth, maybe another example that also shows how to show a post form ONLY if the user is fresh registered over oauth to collect maybe an address and the same for login - only the oauth login link > logged in and how to check if user is logged in.
http://www.youtube.com/watch?v=_jsX6J3Ls7g show some basic idea how to archive this.
maybe its late but this example here:
https://github.com/codenitive/laravel-oneauth/wiki/Getting-Started
makes no sense to me...
why would i show a registration form after they already signed up over twitter? same goes for the action_login - why would i want a login/password field if im using twitter?!
also, how do i know on the action_register if the user is coming from oauth or if he just submits the form under that route?
can you create an example that authentificates only by oauth, maybe another example that also shows how to show a post form ONLY if the user is fresh registered over oauth to collect maybe an address and the same for login - only the oauth login link > logged in and how to check if user is logged in.
thanks!