Chris McDonough chr...@plope.com added the comment:
What you ended up doing is the recommended standard right now. Thanks for the
report.
--
status: chatting - resolved
__
Repoze Bugs b...@bugs.repoze.org
http://bugs.repoze.org/issue58
Raphael Slinckx r.slin...@whatever-company.com added the comment:
For the record here's what i had to do in my registration controller to login
the user after he signs up automatically (using TG2/pylons):
# Remember the user, removing the need to login
identity = {'repoze.who.userid':
Tres Seaver tsea...@agendaless.com added the comment:
I'm not sure why your registration controller can't just return the
'Set-Cookie' header itself, perhaps using whatever API the relevant
plugin implmentation exposes to compute the value.
If I *had* to get the header set via repoze.who, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raphael Slinckx wrote:
New submission from Raphael Slinckx r.slin...@whatever-company.com:
I can't find a way to setup identity programmatically.
I have a registration controller that creates a user in a database, when the
registration
