I'm using the last stable release, 0.4.0. I should probably get on the trunk, you think it's good for production use?
I'm using the sqlalchemy_044 driver from the trunk at the moment anyhow. -Mark On Sep 2, 4:36 pm, "Rick Flosi" <[EMAIL PROTECTED]> wrote: > Oh, I ran into that problem too. You might need a newer version or trunk. > > I'm using AuthKit>=0.4.1dev-r155 > > I'd have to dig up the emails to remember what the problem was, but it was > something to do with that flag only getting applied to either authorize or > authenticate, but not both. > > What version of AuthKit are you using? > > -r. > > On Tue, Sep 2, 2008 at 3:26 PM, Mark Mitchell <[EMAIL PROTECTED]> wrote: > > > Thanks! > > > That makes a lot of sense... I didn't know there was an > > authkit.setup.enable flag. I still got an exception though with it > > on: > > > Exception: Authenticate middleware not present > > > Which corresponded to my middleware.py's: > > > permission = ValidAuthKitUser() > > app = authkit.authorize.middleware(app, permission) > > app = authkit.authenticate.middleware(app, app_conf) > > > (the last line). > > > So I added the following to the shell.ini file you recommended > > creating: > > > [app:main] > > use = config:development.ini > > *full_stack = false* > > > authkit.setup.enable=false > > > By setting the full_stack = false, it didn't even try to run the > > authkit setup lines. I think I needed this b/c I have authkit > > installed throughout all my application, not just for some > > controllers, but requiring every action from every controller to have > > a valid logged in user. > > > Thanks for getting me on the right track, hope this helps someone, > > > -Mark > > > On Aug 27, 10:30 am, "Rick Flosi" <[EMAIL PROTECTED]> wrote: > > > What I've been doing is using a different config file for running the > > paster > > > shell. > > > > eg. shell.ini: > > > > [DEFAULT] > > > debug = true > > > email_to = [EMAIL PROTECTED] > > > smtp_server = localhost > > > error_email_from = [EMAIL PROTECTED] > > > #sqlalchemy.default.echo = True > > > > [server:main] > > > use = egg:Paste#http > > > host = 0.0.0.0 > > > port = 5000 > > > > [app:main] > > > use = config:development.ini > > > > *# AuthKit Config > > > # disable authkit for paster shell* > > > *authkit.setup.enable = false* > > > > "authkit.setup.enable = false" will disable authkit for you. Then run > > > `paster shell shell.ini`. > > > > Hope this helps in the short run. > > > > -r. > > > > On Tue, Aug 26, 2008 at 4:35 PM, Mark <[EMAIL PROTECTED]> wrote: > > > > > I installed authkit into my pylons app so it works across all requests > > > > of my site. Unfortunately, this makes the paster shell command not > > > > work with the following error: > > > > > paste.fixture.AppError: Bad response: 401 Unauthorized (not 200 OK or > > > > 3xx redirect for /_test_vars) > > > > > (It's trying to HTTP GET /_test_vars which is protected by authkit on > > > > my site). > > > > > Is there a way to pass in authentication details? I've seen previous > > > > postings on this before but with no resolution (there was resolution > > > > for test fixture support but not for paster shell)... > > > > > Thanks, > > > > > -Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
