Comments on: Understanding Devise roles /2009/11/understanding-devise-roles/ Plataformatec's place to talk about Ruby, Ruby on Rails, Elixir, and software engineering Thu, 22 Apr 2010 17:57:19 +0000 hourly 1 https://wordpress.org/?v=6.4.2 By: Michael van Rooijen /2009/11/understanding-devise-roles/comment-page-1/#comment-381 Sun, 22 Nov 2009 00:38:29 +0000 /?p=426#comment-381 Hi! Very nice update! I was actually one of those people that asked if there was a possibility for using another attribute (other than the email attribute) to do authentication with. For my next project (which I’ll be starting on soon) I was still undecided whether to go with Authlogic or Devise. Not because I’d rather use a “username” over “email”, because the next project will probably use the email attribute to authenticate, but because I don’t want to continuously change authentication gems because depending on whether I need another attribute or not. But this update made me decide to go with Devise with new introduction of the scoped authentication feature. Next to just being able to say: “Use the Username Attribute”, that you can say: “Use the Username Attribute that belongs to ‘this’ subdomain/account/website” or whatever. This is actually the perfect solution for one of my current projects, so you at the same time inspired me with this blog post!

Thanks a lot!

]]> By: Michael van Rooijen /2009/11/understanding-devise-roles/comment-page-1/#comment-888 Sun, 22 Nov 2009 00:38:00 +0000 /?p=426#comment-888 Hi! Very nice update! I was actually one of those people that asked if there was a possibility for using another attribute (other than the email attribute) to do authentication with. For my next project (which I’ll be starting on soon) I was still undecided whether to go with Authlogic or Devise. Not because I’d rather use a “username” over “email”, because the next project will probably use the email attribute to authenticate, but because I don’t want to continuously change authentication gems because depending on whether I need another attribute or not. But this update made me decide to go with Devise with new introduction of the scoped authentication feature. Next to just being able to say: “Use the Username Attribute”, that you can say: “Use the Username Attribute that belongs to ‘this’ subdomain/account/website” or whatever. This is actually the perfect solution for one of my current projects, so you at the same time inspired me with this blog post!

Thanks a lot!

]]>