[ EDIT—This post has been edited since the original post ]
[ a summary of key points is below ]
In this lively topic:
an overwhelming 67.5% of those who voted established a need for a standardized security control system within CodeIgniter.
I break the “security control system” into three appropriate parts:
2) Role Based Access Control
3) Identity Management and Control
My software is compartmentalized that way too.
In post #43, Derek Jones stated
Nothing about writing nor supporting (especially not supporting) an ACL solution is easy, quick, or cheap.
and then proceeded to issued a challenge for someone to “put up” (my words - not his).
I can’t afford to do this work and support it for free. The fact is I am one person consultancy / software house and I consult, travel, write code, teach, etc. But if enough (market) interest is generated, I am willing to put my company behind a broader effort. If that happens, it means the product gets supported.
Obviously a commercial solution:
Plurious Auth is the Authentication part. Plurious Auth is very simple, extensible, flexible, and it just works. You’re welcome to go check it out.
Summary of key points
On behalf of the community
The use of the NuSphere PhpExpress extension makes the solution too restrictive
The developers I’m selling too expect to be able to modify all code they use
Support provided to overseas locations may take too much time
I personally…am a little nuts
On behalf of Plurious
Plurious wishes to maintain a Class A product with Class A support
Plurious wishes to control a software baseline from which all support is derived
Plurious wishes to extend additional capabilities from the existing baseline and not a moving target!
Plurious will not support dishonorable people