<div>Good point. A simpler solution could be also named session variable (cookies) pool's. So I could assign session parameters to some kind of "hosts family". Right now I don't see a clear example where you'd like to share the cookies among different sites. It's peculiar since, as you've said, the browser will never do that in a normal way. It is not clear this behaviour from documentation. From a agnostic point of view it looks like a security issue but with a quick workaround creating new applications.</div>
<div> </div>
<div>Thanks again for your helpful comments.</div>
<div> </div>
<div>Eduardo.</div>
<div> </div>
<div> <br><br></div>
<div class="gmail_quote">On Mon, Sep 12, 2011 at 11:02 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">On 9/12/11 4:59 PM, "Eduardo Fernandes" <<a href="mailto:edufer@gmail.com">edufer@gmail.com</a>> wrote:<br>>I'll try it out. So I need a new application for each customer. Your idea<br>
>is clear. I supposed that the session cache would share entries only for<br>>the hosts/alias in the same site.<br><br></div>One of the possible future directions for 3.0 is to auto-generate certain<br>kinds of overrides in some way, that being an obvious example.<br>
<div>
<div></div>
<div class="h5"><br>-- Scott<br><br>--<br>To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br></div></div></blockquote></div><br>