StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I would set the cookie for the explicit domain as you have there because that maintains any security information within that specific domain's cookie. You can also add a non-encrypted cookie at the *.parent.com level that holds information about which domains have been authenticated. There is no real way to tie this together though without using maybe timestamps and having a logical connection between the applications (ie - sub2 has a session timeout of 20 minutes so if the domain + valid timestamp occur in the parent cookie it would be valid, however this is business logic).</p> <p>I'm not sure the reasoning behind the disconnect between domains, but you might actually prefer to have a single cookie that has encrypted text behind encrypted text. EG:</p> <p>1) Sub1 logs in, sets the parent.com cookie as valid. Sends a piece of user data to an authentication web service.</p> <p>2) The authentication service recognizes sub1 as the sender, encrypts the user data, and adds it to a custom cookie object.</p> <p>3) The custom cookie object constructs a composite string on a unique split character (or sequence) and makes it available to the service method.</p> <p>4) The service, using the forms encryption, encrypts the entire ticket and sends it back to the original login.</p> <p>That way each server would be able to unencrypt the global ticket, but each piece of data would be encrypted using a common algorithm but a server based salt. So if sub2 attempts to read the cookie data from sub1, it gets the encrypted version rather than raw data.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload