<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 20, 2016 at 9:56 AM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
</span>I see nothing there indicating the SP is doing anything wrong, which is why nothing's been done to the code. I can't change what Tomcat does with the data its given. If it's assuming an encoding that's not correct, then it's going to break things, but that would be true of real headers from the client too.<br>
<span class="gmail-"><br></span></blockquote><div><br></div><div>I'm not suggesting this is a bug in Shibboleth. <br><br>It seems to me, its more like Tomcat is following the spec and its having this unpleasant side effect in a certain Shibboleth use case.</div><div><br></div><div>Basically, my data is UTF-8. When I step thru the Tomcat code, Tomcat's ByteChunk coverts it to ISO-8859-1 <br><br>Nothing I've tried to override this has had any effect.<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">
> Is the solution appropriate for data delivered as attributes?<br>
<br>
</span>No idea but whatever that's doing isn't about where the data is actually being pulled from.<br><span class="gmail-HOEnZb"><font color="#888888"><br>
</font></span></blockquote></div><br></div><div class="gmail_extra">The solution comes from the second link. I see it posted it incorrectly added a correction just before I got your reply.</div><div class="gmail_extra"><br></div><div class="gmail_extra"><span style="font-size:12.8px">The correct url is </span><a href="https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPAttributeAccess" target="_blank" style="font-size:12.8px">https://wiki.shibboleth.net/<wbr>confluence/display/SHIB2/<wbr>NativeSPAttributeAccess</a> and in the Java link it says use:<br></div><div class="gmail_extra"><pre style="margin-top:10px;margin-bottom:0px;padding:0px;font-family:confluenceinstalledfont,monospace;color:rgb(51,51,51);font-size:14px">String value= request.getHeader("givenName");
value= new String( value.getBytes("ISO-8859-1"), "UTF-8");</pre><pre style="margin-top:10px;margin-bottom:0px;padding:0px;font-family:confluenceinstalledfont,monospace;color:rgb(51,51,51);font-size:14px"><br></pre><pre style="margin-top:10px;margin-bottom:0px;padding:0px;font-family:confluenceinstalledfont,monospace;color:rgb(51,51,51);font-size:14px">In my case I'll have to use request.getAttribute("givenName"); because my data is delivered via attributes.</pre><pre style="margin-top:10px;margin-bottom:0px;padding:0px;font-family:confluenceinstalledfont,monospace;color:rgb(51,51,51);font-size:14px"><br></pre></div></div>