On 2012-3-27 21:39, Chris McDonough wrote:
On Tue, 2012-03-27 at 12:18 -0700, Jason wrote:
I would like the auth ticket authentication policy to also set the
wild card domain for domains one level up from the current domain. For
example: An application running on the domain x.y.foo.com would have
".y.foo.com" set as the domain for one of the cookies. I'm using this
to allow app01.mydomain.com and app02.mydomain.com to use the same
auth ticket cookie for authentication. Currently I am also using a
similarly patched repoze.who so that this works across old Pylons
applications and new Pyramid apps, but I couldn't figure out how to
send a patch to the repoze.who project that would only apply to
repoze.who version 1.
[..]
If its unlikely to be accepted, I would like to know so that I can
create a new auth ticket authentication policy instead.
Yeah I fear a reliance on that package is not in the cards for Pyramid
right now. I also fear that the cookie helper is already a little out
of control right now with cookie options and I'm loath to add more to it
without trying to reconcile all of them.
I'ld agree. I'm guessing it's also pretty trivial to wrap the standard
auth ticket class to do this in your own code.
Wichert.
--
Wichert Akkerman <wich...@wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
