Authentication

The whole authentication problems to be solved:

* Database with tables for users, user roles (optionally), permissions (based on roles or hard-coded). The first difficulty is the structure that fits to all needs.

* The second difficulty: Some people prefer to use models based on CI_Model to access the database. Other like me use another base model. Other people even might like to use Doctrine for example. So, seemingly here abstract models with "drivers" or "adapters" are needed. This is difficult. The other way is a second database connection for the authentication solution only, but this is ... ugly (a debatable opinion).

* The third difficulty: You need whole pages with login form, password recovery form, etc., that means visual design. Some guys prefer PHP for the views, other like me use template engines. Which would it be? And the visual design should be based on Bootstrap, Semantic or what? Email-communication? - visual templates again, language lines, work.

* 4. External authentication through Facebook, Google, etc. you might want? Again, abstractions, adapters, support during the time, who would do this.

* 5. And some exotic features? I want a CLI script to log in using its system account too. CLI means there is no PHP session. Would there be consensus about such things? Unlikely.

---------

What can be done. Yesterday I saw yet another naive implementation of password generation. I lead me to the thought, maybe, it would be good the framework to provide only some low-level features done right instead of a whole implementation. And things like this one https://codeigniter.com/user_guide/helpe...dom_string could be re-factored in order preventing wrong usage.