Too few fields for users about gatekeeper

[enygma]

Good point - the library this was modeled after (Sentry) only had a few user fields in it. I think it's definitely reasonable to add a "user attributes" kind of setup to allow for much more flexible user details to be stored along with the core information. I'd say that username, password, email and things like that should stay in the users table but I could definitely see the attributes being used for other things.

[Ser5]

I can think of a few more ways of implementing additional fields. Don't know if they are "Gatekeeper-way" or easy to code, though.
1.) Most straightforward is inheriting UserModel, adding some fields to $properties variable, adding fields to database accordingly, then use Gatekeeper::init() to force usage of inherited class, something like Gatekeeper::init(blah, array('UserModel' => '\My\User\Model'))
2.) Make UserModel configurable, so one can pass his own array of properties to UserModel constructor. Then you pass configured UserModel to Gatekeeper::init(). Of course manual adjustment of users table is required too.
3.) Doctrine & Symfony2 way. You create your own User class containing any set of fields then say "Doctrine, use it, please", then magic occurs, users table modified automatically and everything works. Kind of. Both Doctrine and Symfony2 are too much complicated and I doubt that it will be easy to implement and use.

[Ser5]

0.) Mostest of the most simple variants: you add dozen more of fields into UserModel, enough for 99% of users - middleName, homeAddress, homePhone, workAddress, workPhone, mobilePhone etc - and make a new release =)

[Swader]

I would recommend against having non-auth info in Gatekeeper - you can easily extend the model and DB setup to have linked followup tables etc. Have a table in your own app logic like users_contact or users_personal etc and just link them to the gatekeeper tables - that way we keep GK lean, and you still get full flexibility for your app.