Re: [Repoze-dev] repoze.what configuration issues

2009-01-15 Thread Gustavo Narea
Hola, Jorge!

On Thursday January 15, 2009 03:28:43 Jorge Vargas wrote:
 bugs in the docs
 - the sample code is wrong, as BaseAuthPlugin isn't an authenticator.

Right, I've just fixed this in trunk. Thanks!

 - setting it as a form_identifies other than having a wrong name add
 nothing to the log output of repoze.what

form_identifies is not used for that (and it's a boolean):
http://www.turbogears.org/2.0/docs/main/Auth/Customization.html#customizing-authentication-settings
http://code.gustavonarea.net/repoze.what.plugins.sql/Quickstart.html#repoze.what.plugins.quickstart.setup_sql_auth

 I currently added the following to my app_cfg.py file
 base_config.sa_auth.form_plugin = None

 http_auth = BasicAuthPlugin('my cool site')
 base_config.sa_auth.form_identifies = [('http_auth', http_auth)]

Try this:
http_auth = BasicAuthPlugin('my cool site')
base_config.sa_auth.form_plugin = [('http_auth', http_auth)]

In this case, the form_plugin (a challenger) is also an identifier, 
so it's not necessary to set form_identifies=True because that's 
the default value.

HTH.
-- 
Gustavo Narea http://gustavonarea.net/.

Get rid of unethical constraints! Get freedomware:
http://www.getgnulinux.org/
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev


Re: [Repoze-dev] repoze.what configuration issues

2009-01-15 Thread Gustavo Narea
On Thursday January 15, 2009 15:52:26 Gustavo Narea wrote:
     base_config.sa_auth.form_plugin = [('http_auth', http_auth)]

BTW, it should be:
base_config.sa_auth.form_plugin = http_auth

Cheers.
-- 
Gustavo Narea http://gustavonarea.net/.

Get rid of unethical constraints! Get freedomware:
http://www.getgnulinux.org/
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev


Re: [Repoze-dev] Question regarding repoze.who +sql / repoze.who.plugins.sa

2009-01-15 Thread Gustavo Narea
Hello, Mathieu.

On Wednesday January 14, 2009 00:03:52 you wrote:
 I had to change the username field in the database to: user_name even if
 the parameter user_name_translation was set to something else but this is
 minor.

Can you please paste the translation line? The key is user_name, not 
user_name_translation, by the way.

 Now, the issue I have is that when I am logging in or out, the url is not
 redirected to the referer but to the actual login form. When I am looking
 at the log, the plugin forms was asked twice to be identified. I can
 understand that the referer is set the the form after the second passage
 but is it normal?

I didn't understand this very well. The normal behavior is:

 -  when you visit a restricted area in your website, you'll get the login 
form and after you login, you'll get redirected to the restricted page above.
 - if you visit the login page voluntarily, then you'll get redirected to the 
home page after login.
 - if you visit the logout page, you'll get redirected to the previous page.

Is this the behavior you've noticed?

 Do you think maybe my who.ini was not properly set up?
 Here is the last part:

 [identifiers]
 plugins =
   redirform
   auth_tkt

 [authenticators]
 plugins =
   sa_auth

 [challengers]
 plugins =
   redirform

That seems right, but it may also be useful to know how you're defining 
redirform.

Cheers!

 - Gustavo.

 Thank you,
 Mathieu

 2009/1/13 Gustavo Narea m...@gustavonarea.net

  Hello, Mathieu et al.
 
  On Thursday January 8, 2009 00:12:28 you wrote:
   I would like to ask you a simple question, feel free to let me know if
 
  you
 
   don't have time. I decided to just stick with a basic db
   authentication, and I am using an external who.ini conf file. The
   problem is the it
 
  seems
 
   that repoze tries to open its own session with the database. I would
 
  prefer
 
   using the one that is already defined inside pylons to avoid
   redundancies and many db connections. Do you have a clue how it could
   be done? I guess
 
  I
 
   wouldn't be able to use the setup file but instead the middleware
   configuration (even that way, I am not sure how to do it).
 
  Hmmm, repoze.who.plugins.sa doesn't start a new session, instead it
  always uses the one you specified.
 
  In your case, if you have the following line in your who.ini file:
 dbsession = youapp.whatever:DBSession
  repoze.who.plugins.sa will use youapp.whatever.DBSession as the
  SQLAlchemy session, the way you will find here (see
  SQLAlchemyAuthenticatorPlugin):
 
  http://repoze.org/viewcvs/whoplugins/whoalchemy/trunk/repoze/who/plugins/
 sa.py?rev=3125view=markup
 
  Cheers!
  --
  Gustavo Narea http://gustavonarea.net/.
 
  Get rid of unethical constraints! Get freedomware:
  http://www.getgnulinux.org/

-- 
Gustavo Narea http://gustavonarea.net/.

Get rid of unethical constraints! Get freedomware:
http://www.getgnulinux.org/
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev


Re: [Repoze-dev] Question regarding repoze.who +sql / repoze.who.plugins.sa

2009-01-15 Thread Mathieu Drapeau



 I didn't understand this very well. The normal behavior is:

  -  when you visit a restricted area in your website, you'll get the login
 form and after you login, you'll get redirected to the restricted page
 above.
  - if you visit the login page voluntarily, then you'll get redirected to
 the
 home page after login.
  - if you visit the logout page, you'll get redirected to the previous
 page.

 Is this the behavior you've noticed?



Hi Gustavo,
I do not get redirected to the restricted page (ex. test.html), I do get
redirected to the same form again (ex. loginform.html) after entering a
valid user/pass. I do look if I am authenticated after I filled the form and
I do. Based on the logs, the authentication process seems to be called twice
and it is why the came_from is changed from test.html to loginform.html.

Hope it is clear.

Thank you,
Mathieu
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev


[Repoze-dev] bfg and google app engine

2009-01-15 Thread Junyong Pan
First I like bfg and wanna use it with google app engine.

I saw bfg is removing some zope 3 dependcies these days.

Any plan to make bfg will support google app engine now? What is the
remaining problems? Can we help to do that?

thanks.

Pan Junyong
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev


Re: [Repoze-dev] bfg and google app engine

2009-01-15 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Junyong Pan wrote:
 First I like bfg and wanna use it with google app engine.
 
 I saw bfg is removing some zope 3 dependcies these days.
 
 Any plan to make bfg will support google app engine now? What is the
 remaining problems? Can we help to do that?

Kapil Thangevalu has done some of the work to make it possible to do
minimal Zope3 apps on GAE.  He blogged about it:

 - http://blog.kapilt.com/2008/05/28/17/

 - http://blog.kapilt.com/2008/05/27/16/

and has the app running at:

 - http://zope3.appspot.com/

What would be helpful is to have somebody try to get a minimal BFG app
run on top of Kapil's forked packages probably using the GAE-emulation
environment, and tell us what breaks.  Once we know it is possible, then
packaging BFG and its full dependency set into a ZIP file would be the
next step.


Tres.
- --
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJb8z3+gerLs4ltQ4RArDeAKCTED3VTF7xwJ+86cPr0Xk/BxK7TgCfdtkO
pZpZ5yLv8LZcXXM2uPJP6Xk=
=EX5m
-END PGP SIGNATURE-
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev