<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">We have a working SSO configuration with Horizon. It’s been a while, but I think their SP metadata contained an encryption certificate and it wasn’t until, after getting frustrated, that I turned off encryption
that it began working. Not the first time a commercial SSO product provided an encryption cert while not actually supporting it, sadly.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">-- <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Ryan Rumbaugh<o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">users <users-bounces@shibboleth.net> on behalf of Tunturi Timo via users <users@shibboleth.net><br>
<b>Date: </b>Thursday, January 26, 2023 at 1:05 AM<br>
<b>To: </b>users@shibboleth.net <users@shibboleth.net><br>
<b>Cc: </b>Tunturi Timo <timo.tunturi@aalto.fi><br>
<b>Subject: </b>Re: IdP integrating with VMWare Horizon as an SP?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Non-NU Email<br>
<br>
On Tue, 2023-01-10 at 15:39 -1000, Baron Fujimoto via users wrote:<br>
> What we have seen is when they try to import our metadata, they get<br>
> some "Invalid static metadata" error, but unfortunately nothing more<br>
> specific than that.<br>
<br>
We had a problem with Horizon where it wouldn't load the IdP metadata<br>
if the metadata didn't have key use (signing/encryption) defined<br>
explicitly per key.<br>
<br>
-- Timo<br>
-- <br>
For Consortium Member technical support, see <a href="https://urldefense.com/v3/__https:/shibboleth.atlassian.net/wiki/x/ZYEpPw__;!!PvXuogZ4sRB2p-tU!D1O1WlPoyAyIc5seQP7j5abxlWAalB73JLTDSVeusJySUBR8ejq_0F8kmilLjEbPoHKUctZvliv_2tJZPPMNhw$">
https://urldefense.com/v3/__https://shibboleth.atlassian.net/wiki/x/ZYEpPw__;!!PvXuogZ4sRB2p-tU!D1O1WlPoyAyIc5seQP7j5abxlWAalB73JLTDSVeusJySUBR8ejq_0F8kmilLjEbPoHKUctZvliv_2tJZPPMNhw$</a>
<br>
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net<o:p></o:p></span></p>
</div>
</div>
</body>
</html>