<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Here is the start of the encrypted assertion that worked from our 2.3.8 IDP to box.<br>
Some things that might be an issue from your IDP: sha1, aes-128 and rsa-oaep-mgf1p<br></blockquote></div><br>Mine looks pretty much identical (we are also 2.3.8 IdP) with aes-128 being the encryption method of the encrypted assertion. mine includes a signature prior to that which you may just be leaving off from your cut/paste, but otherwise is pretty identical. <br>
<br>I've got a few emails out to Box right now and am waiting their response about turning on support for an encrypted assertion from them. I did send them a sample assertion from this very same IdP against a different SP as part of filling out my federation questionnaire, but the question of encryption of the assertions never came up. We'll see what they say.<br>
<br>Thanks again for your help.<br><br>-Rob<br><br>-- <br><div>Robert W. Gorrell<br>Middleware Engineer, Identity and Access Management</div>
<div>University of NC at Greensboro<br>336-334-5954</div>