Unable to define custom login/logout handlers

[GoogleCodeExporter]

The default login and logout handlers in 
http://code.google.com/p/typhoonae/source/browse/src/typhoonae/__init__.py?r=rel
ease-
0.1.0b1#51 are blocking any custom handlers with the same url.

Original issue reported on code.google.com by tobias.r...@gmail.com on 29 Nov 2009 at 3:41

[GoogleCodeExporter]

Fixed in the trunk. It is now possible to use a custom login/logout handler by 
simply adding the following 
URL handlers to your app.yaml file.

- url: /_ah/login
  script: login.py

- url: /_ah/logout
  script: login.py

It is also possible now to configure different login and logout URLs by using 
apptool with these options --
login_url=/my_login_url --logout_url=/my_logout_url. Make sure then that you 
have the appropriate URLs in 
your URL handler definitions above.

Original comment by tobias.r...@gmail.com on 22 Mar 2010 at 3:24

• Changed state: Started

[GoogleCodeExporter]

Editing app.yaml for Typhoon-specific doesn't sit well with me, I think there 
is too 
much of a possibility of there being conflicts with GAE or other app-engine 
'emulators'.

Personally, I would like to see a typhoon.yaml (or something) containing 
configuration 
specific to an app and how it works with Typhoon. I think that specifying 
alternative 
login handlers would be well-suited to be in such a configuration file.

Original comment by Noah.Mci...@gmail.com on 29 Mar 2010 at 11:17

[GoogleCodeExporter]

Good point. I'll see if an apptool option passed to the fcgiserver 
configuration would fix this.

Original comment by tobias.r...@gmail.com on 29 Mar 2010 at 2:14

[GoogleCodeExporter]

Included in the 0.1.4 release. We need to open another issue for the custom 
TyphoonAE configuration 
(typhoonae.yaml).

Original comment by tobias.r...@gmail.com on 26 Apr 2010 at 2:56

• Changed state: Fixed