Vork is an open-source PHP framework designed for rapid development of performance-oriented scalable applications.
The mission of Vork is to provide an MVC architecture and full-featured toolkit in a gimmick-free no-frills approach without adding overhead, creating slow & unscalable abstraction layers or re-inventing native PHP functionality.
CakePHP Version 1.2.5
I would like a single user to have multiple email addresses. I would like a single user to have a single password. I would like users to log in using any of their multiple email addresses and their single password.
I have created a users table with an id and a password field. I have created a user_email_addresses table with an id field a user_id field and an email_address field.
Question: How do I modify the auth component minimally to look for the "username" in this case, "email_address", in the user_email_addresses table and the "password" in the users table?
Code would be great!
My web application only has one level of authorization. It's either you're logged in or not. Would ACL be overkill for this? Would the Auth component be sufficient/secure enough to handle this situation?
Does CakePHP session anonymous users? If so, is there a way to turn that off? I don't think I need sessions to be passed around if the user is anonymous.
Hi there,
I am hoping some can help me a little bit, I am currently developing my first site using a PHP framework, part of the site is spilt into a members area, this is where my confusion begins to surface, withing the members area I want normal members to be able to add new comments and edit there own comments, simple enough that I can just check the posters name against the username that is stored in the session, my confusion comes with differentiating between the 'normal' users and the higher level users who have the ability to delete and modify any ones comments etc, they should also be able to access the admin section of the site.
My question is should all user login through the same Zend_Auth controller, or should there be seperate controllers using Zend_Auth for each type of user or can all that be dealt with using Zend_Acl? Any help, advice, article, or tutorials would be greatfully appreciated. Personally I think the Zend documentation is a little raw on some classes.
Thanks in advance
sico87
Latest release: v1.2.3
Initially I was going to wait for my Layerful Framework (a transparent layering framework for Kohana) to mature before releasing its bundled modules. However, since this Authlite module can be used independently to Layerful, I am releasing it now.
Authlite is a user authentication module for Kohana.
What’s the difference between Authlite and Auth?
Kohana comes with an official Auth module which does exactly what was described in the last paragraph, so why another module then?
It is because Authlite offers greater flexibilty. Please read the features outlined below to find more.
Legacy database compatibility
One thing that keeps me away from using Kohana’s Auth module, is that it forces us to use a password hash seed. This is okay for a brand new application, but what about the ones with legacy databases? There are a lot of existing applications use plain MD5 or SHA1 hashes, Auth makes it impossible to use these existing data.
Authlite, on the other hand, does not force developers to use any seeds at all. Like Auth, we can define the encryption method (e.g. md5, sha1) in the config file.
Configurable database columns
Further than that, the user model, username column, password column and session column are all configurable.
Multiple instances of Authlite
If your application has more than one user tables, you will struggle to make it work in Auth. In Authlite, simply have one config file for each user object, and config their user model, session key and the other variables accordingly.
Does not enforce user roles
For simple applications we often do not even want to have roles attached to our user model. In Auth, user role is mandatory, which makes things more complicated than they should be. In Authlite, roles are handled by Kohana framework itself. By using ORM model relationships, roles can be added, removed and modified very easily. A tailoured ACL (Access Control List) solution can be developed in no time.
Auth-like syntax and usage
Authlite is based on Auth, so if you’re already familiar with using Auth, you will find Authlite a breeze to use.
Lightweight
Even if you have never used Auth before, you will find Authlite to be extremely easy to use. :)
// Authlite instance $this->authlite = Authlite::instance('authlite'); // login check if ( ! $this->authlite->logged_in() && Router::$method != 'login') { url::redirect(Router::$controller.'/login'); } else { // assigns the user object $this->user = $this->authlite->get_user(); }
v1.2.3 [2009-02-05]
v1.2.2 [2009-02-05]
v1.2.1 [2009-01-27]
v1.2 [2009-01-27]
Older versions were not tagged with version numbers, you may check out the commit history on GitHub.
Source Code / Download
