Auth

I totally agree with Narf and bclinton on the idea of a "built-in" auth utility.
I use both a very simple user registration system and a more complex authorization tool.
I wrote both (sorry, they are owned by my clients) and the complex system is just that, complex. It has to be to meet the needs of the program/application.

No, it is not a good idea to make a general purpose auth tool because it is far too easy to hack it from external systems. Do what bclinton advises, above, and analyze your real needs for the system. Perhaps you can get by with a simple registration system. And perhaps you cannot because you need the complex, secure features of a full auth system. But it is up to you to decide. It is not and should not be the responsibility of the CI developers and maintainers to keep > Your < security system truly secure.

That being said, I would really like to see someone address, in the CI world, just what needs to be included in an auth system. A "How-to" on Auth, oriented to CI3, singleton, PHP 5.x. There are plenty of books on the subject and they are still an uphill climb to digest and they generally are not CI oriented.
/rant off

[edit] I'd like to see a separate sub-forum, here, to address authorization and security issues. The 'net is not getting any more secure and we could all use some feedback on what is happening and how it might be addressed under CI...

CI 3.1 Kubuntu 19.04 Apache 5.x&nbsp; Mysql 5.x PHP 5.x PHP 7.x
Remember: Obfuscation is a bad thing.
Clarity is desirable over Brevity every time.