AuthKit status question
Matt Feifarek
I'm very keen to use something like James Gardner's AuthKit in a real project.
I understand that the module is not finished, and that the docs say that it hasn't been used in production, etc.
Is that mainly just the standard "don't blame us if your app crashes" disclaimer, or is the module missing pieces or broken in fundamental ways? I'm not the sort of person who would blame you for anything, and I understand that there are cranks out there who demand guarantees. My concern is that if I make an investment in using AuthKit, I will eventually want to take it into production for some small b2b sites (no "enterprise" here).
I'm just getting started this week with WSGI/Pylons so I can't offer much expert help yet, but I've been doing Webware development for about 4 years, and have made our own near-equivalent to AuthKit for intranet projects, so maybe I can help eventually.
Thanks
-- Matt
James Gardner
Answering a few different emails in one go here:
> AuthKit>=0.2.2b doesn't exist in a default pylons app either, so needs
> to be added along with the "web==0.6.0" item.
I've now clarified this in the docs of the latest version 0.2.3b
> Teensy typo on line 58 perhaps, (also in the account.py sandbox file):
>
> c.tempate_dir = 'authkit/standard'
>
> Should that be "c.template_dir"?
Oops, that's a mistake! At least I was consistent though ;-)
The new version in SVN has that corrected to c.template_dir so when you
upgrade you will need to rename c.tempate_dir everywhere in your code.
> I'm having a weird issue with Authkit. Having followed the instructions
> in manual.txt, The account/signin and account/create pages only appear
> to pass through the first character of the text fields. That is, I try
> to login with 'ad...@example.org' and 'admin' but this returns a 'No
> such username' page, with just an 'a' in the username field.
I wrote the AuthKit docs before Pylons 0.9 was released. In Pylons
0.9dev request.params was handled differently. I've updated AuthKit to
use Pylons 0.9 now so you won't get this truncation of form fields to
the first character.
> Did I screw something up, or is there a problem with Authkit or one of
> its dependencies?
If you upgrade to the latest AuthKit it will work properly with Pylons
0.9 final.
> I noticed the same thing when I did the Quick-Start tutorial
It is the same problem. (I went on holiday before the final format of
request.params was agreed and unfortunately Ben released 0.9 before I
was back so I didn't get a chance to correct it before the release. It
is corrected now though.)
> I understand that the module is not finished, and that the docs say that
> it hasn't been used in production, etc.
>
> Is that mainly just the standard "don't blame us if your app crashes"
> disclaimer, or is the module missing pieces or broken in fundamental
> ways?
AuthKit genuinely isn't finished yet as the problems above highlight so
you are free to use it in production systems (I do myself) as long as
you know there will be bugs and that the APIs are likely to change.
I've been concentrating on getting Pylons 0.9 really good and now it is
released you can expect AuthKit to be my primary focus so hopefully it
will be fit for a release soon.
> I'm just getting started this week with WSGI/Pylons so I can't offer
> much expert help yet, but I've been doing Webware development for about
> 4 years, and have made our own near-equivalent to AuthKit for intranet
> projects, so maybe I can help eventually.
That would be great. I'll keep you posted ;-)
Cheers for the bug reports everyone.
James