<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<br>
<div>
<div>On Mar 13, 2014, at 9:38 PM, Sharma, Dattathreya <<a href="mailto:datta@ucla.edu">datta@ucla.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div style="font-size: 12pt; background-color: rgb(255, 255, 255); font-family: Calibri, Arial, Helvetica, sans-serif; position: static; z-index: auto;">
<div style="margin-top: 0px; margin-bottom: 0px;">We have to upgrade to Java 7 this year and I am looking at replacing Terracotta. The db plugin seems like a viable solution for us.<br>
</div>
<div style="margin-top: 0px; margin-bottom: 0px;">The wiki states that "The storage service does not persist the login context information to the database. You must use session affinity during the login process".</div>
<div style="margin-top: 0px; margin-bottom: 0px;">Isn't login context stored in the cookie? If the user authenticates and returns to a different node it should work just fine right?</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>As Scott stated, session is kept via cookie that can be pulled from the DB back service on any node. During the actual login though, the cookie (and data) used to provide the state is not persisted to the DB, hence the affinity/sticky requirement.</div>
<br>
<blockquote type="cite">
<div style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div style="font-size: 12pt; background-color: rgb(255, 255, 255); font-family: Calibri, Arial, Helvetica, sans-serif; position: relative; z-index: 0;">
<div style="margin-top: 0px; margin-bottom: 0px;">If the database is unavailable, will the back channel attribute query fail (if it goes to a different node) ?</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>The plugin persists objects that Shibboleth requests be put into the "session storage partition". Shib divides the storage service into logical units, "session" being one of them. So anything stored in the "session" partition is persisted to the DB. That
said, I've never used back channel attribute query (only attribute push), so testing it was not on my list (or even on my thought radar).</div>
<div><br>
</div>
<br>
<blockquote type="cite">
<div style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div style="font-size: 12pt; background-color: rgb(255, 255, 255); font-family: Calibri, Arial, Helvetica, sans-serif; position: relative; z-index: 0;">
<div style="margin-top: 0px; margin-bottom: 0px;">With this plugin, will there be any interruption to the service if I take a node offline? I understood that, at the most user may loose SSO session and have to sign-in again.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Anyone in mid-cycle of login to that node will be affected. Likely getting a Shibboleth error screen and having to start their request again.</div>
<div><br>
</div>
<div>Paul</div>
<div><br>
</div>
</div>
<div apple-content-edited="true">Paul Hethmon<br>
Chief Software Architect<br>
<a href="mailto:paul.hethmon@clareitysecurity.com">paul.hethmon@clareitysecurity.com</a><br>
<br>
</div>
<br>
</body>
</html>