<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I'm sure there are some non-technical issues we can come up with
here, and I have already offered my standard "...join InCommon ...
it's good for all of us ... we will sponsor you..." plugs to them.<br>
My question to this list is: Are there any technical issues with
this scenario?<br>
<br>
From this vendors documentation:<br>
<blockquote>IRBManager automatically accepts IdPs published in the
InCommon Federation’s metadata list, and we can add other metadata
sources upon request. Our security metadata XML is available at
<a class="moz-txt-link-freetext" href="https://shibboleth.irbmanager.com/metadata.xml">https://shibboleth.irbmanager.com/metadata.xml</a>.<br>
</blockquote>
On the SP side, the SP is consuming InCommon metadata and therefore
can get our IDPs metadata given our entityID. <br>
On the IDP side, I consume their SP metadata directly (not via
InCommon) and the SP entityID.<br>
<br>
Not all configured yet, but this seems like it should work.<br>
Am I missing anything?<br>
<br>
Thanks,<br>
Dan<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title></title>
Dan Malone<br>
<font color="#999999">Lead Identity Management Architect<br>
Information Technology Services<br>
California Polytechnic State University<br>
San Luis Obispo, California<br>
<br>
Direct 805-756-6326<br>
<a class="moz-txt-link-abbreviated" href="mailto:dmalone@calpoly.edu">dmalone@calpoly.edu</a></font><br>
</div>
</body>
</html>