<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>RE: incorporating opensso metadata and extended metadata xml files into shibboleth SP</TITLE>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>On 8/19/12 3:00 PM, "csross" <<a href="/user/SendEmail.jtp?type=node&node=7581375&i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>> wrote:<BR>
><BR>
>I have to talk to a new IDP with a new SP on my shib 2.4.3 solaris<BR>
>server.<BR>
>I believe the IDP is opensso and the administrator does not have any<BR>
>experience with shibboleth as they never had any SPs running it. They sent<BR>
>me a metadata.xml file which I specified identified in the shibboleth2.xml<BR>
>file. They also sent me an extended metadata.xml file which has a number<BR>
>of<BR>
>Attritribute name= and value. These look nothing like what is in the<BR>
>attribute-map.xml file I use for other IDPs I contact but they run<BR>
>Shibboleth.<BR>
<BR>
>>>The SP doesn't use any of that particular information in metadata.<BR>
<BR>
>>>Obviously the attributes they're sending do have to be mapped but that<BR>
doesn't involve the metadata.<BR>
<BR>
Thank you. Has anyone done this, manually created a mapping for attributes passed from another SSO-ipd into a format shibboleth understands please? If there is a doc on this, I would greatly appreciate the link. I know it depends on what attribute they are sending, etc, but a generic example would be great.<BR>
<BR>
<BR>
>A lot of sites I researched mentioned NameIDFormat and I see these in the<BR>
>metadata.xml and extended-metadata.xml, but again it is in an unfamilar<BR>
>format. Is there any relation to the entries in attritbute-map?<BR>
<BR>
>>>No.<BR>
<BR>
>Does anyone have any idea how to incorporate this into Shibboleth please?<BR>
<BR>
>>>You don't need to.<BR>
<BR>
-- Scott<BR>
<BR>
--<BR>
To unsubscribe from this list send an email to <a href="/user/SendEmail.jtp?type=node&node=7581375&i=1" target="_top" rel="nofollow" link="external">[hidden email]</a><BR>
<BR>
<BR>
<BR>
<BR>
_______________________________________________<BR>
If you reply to this email, your message will be added to the discussion below:<BR>
<A HREF="http://shibboleth.1660669.n2.nabble.com/incorporating-opensso-metadata-and-extended-metadata-xml-files-into-shibboleth-SP-tp7581372p7581374.html" target="_top" rel="nofollow" link="external">http://shibboleth.1660669.n2.nabble.com/incorporating-opensso-metadata-and-extended-metadata-xml-files-into-shibboleth-SP-tp7581372p7581374.html</A><BR>
<BR>
To unsubscribe from incorporating opensso metadata and extended metadata xml files into shibboleth SP, visit <A HREF="" target="_top" rel="nofollow" link="external">
</FONT>
</P>
<br/><hr align="left" width="300" />
View this message in context: <a href="http://shibboleth.1660669.n2.nabble.com/incorporating-opensso-metadata-and-extended-metadata-xml-files-into-shibboleth-SP-tp7581372p7581375.html">RE: incorporating opensso metadata and extended metadata xml files into shibboleth SP</a><br/>
Sent from the <a href="http://shibboleth.1660669.n2.nabble.com/Shibboleth-Users-f1660767.html">Shibboleth - Users mailing list archive</a> at Nabble.com.<br/>