Yep got it working fine just ensure that you are using the rails3 branch of authlogic

I’ve tried this with Rails 3 and it seems to be broken. Have you by any chance tried this with Rails 3?

You’ll want to use validations_scope to do this. Look into this and
authenticates_many for details.

You may have something like this in your models:

class User < ActiveRecord::Base
acts_as_authentic do |c|
c.validations_scope = :company_id
end
[.....associations, etc ....]
end

class Company < ActiveRecord::Base
authenticates_many :user_sessions
[.....associations, etc ....]
end

This much should allow you to create the same user/email for different
companies.

Your sessions controller will have to be updated to reflect that you
are scoping the user to a company for the new, create, and destroy
actions. How you implement this in your app is up to you. Hope this
helps.

I guess that authlogic assumes a slightly lower position in the systems’ tree than we need to peg it at. I.e. No authentication branches below it, whereas we are further up the tree with multiple branches below the authentication layer.

Yeah the only way l think would be to fork it from what l can see quickly reviewing the gem. A shame really would have thought you could do that simply guess they are just trying to make is as secure as possible.

Good luck with it and let me know if l can help at all and how you go

I am thinking that I may need to fork the code and add a company field by cloning the login field handling but obviously I would prefer not to do this!


class UserSession < Authlogic::Session::Base
find_by_login_method :find_by_username_and_company_id
end



class User < ActiveRecord::Base
def self.find_by_username_and_company_id(login, company_id)
find_by_username_and_company_id(login, company_id)
end
end


How would I extend authlogic so that instead of using just one field it uses two?