Authentication

I do not speak for CI but the answer I believe is no. The feeling seems to be that since different auth systems work in very different ways, and there are already tons of libraries of all sorts to do this sort of thing which can be easily implemented, that it should be considered a tool for the CI toolbox, not part of the toolbox itself (to continue a poor analogy).

Personally, I definitely have a foot in both camps, and can see arguments on both sides. I think my personal preference is that it should be part of the core framework, and I feel the same should apply to a template engine. That the CI team should select what they think is the best third party solution today, and implement that and ship it as part of the default install, ready to use out of the box. I think this would be very good for CI, and very very useful to newbies and less expert users like myself.

However, as I said, I can see the arguments against and they do make sense. Just not enough to completely persuade me that it is the right decision.

Best wishes,

Paul.