IDP 2.5.0 relying-party.xml file for Cisco WebEx?

Eric Wedaa Eric.Wedaa at marist.edu
Tue Nov 3 15:48:44 EST 2015


How did you configure your metadataProvider without editing relying-party.xml?

Errors: For instance https://wiki.shibboleth.net/confluence/display/SHIB2/IdPMetadataProvider says:
    <MetadataProvider xsi:type="FilesystemMetadataProvider"
                      id="InternalMetadata"
                      metadataFile="/path/to/my/metadata-internal.xml" />
But the error log says :
15:16:44.696 - ERROR [edu.internet2.middleware.shibboleth.common.config.BaseService:188] - Configuration was not loaded for shibboleth.RelyingPartyConfigurationManager service, error creating components.  The root cause of this error was: org.xml.sax.SAXParseException: cvc-elt.4.2: Cannot resolve 'FilesystemMetadataProvider' to a type definition for element 'metadata:MetadataProvider'.

So either I messed up something, or the docs are wrong.

Thanks1

>>Ericw

-----"users" <users-bounces at shibboleth.net> wrote: -----
To: users at shibboleth.net
From: Christopher Bongaarts 
Sent by: "users" 
Date: 11/03/2015 03:41PM
Subject: Re: IDP 2.5.0 relying-party.xml file for Cisco WebEx?

On 11/3/2015 2:35 PM, Eric Wedaa wrote:
>    Does anybody have a working relying-party.xml file for Shibboleth IDP 2.5.0 that works for Cisco WebEx?
>
>    I have beat my head against the wall and, while having found several webpages that claim to tell you how to do it, none of them have worked.  I can get my IDP to talk to Shibboleth SPs and testshib.  All my attempts have spewed tomcat errors telling me that my relying-party.xml file is wrong.

We did not have to make any changes to relying-party.xml to get WebEx 
working.

We did have to define a bunch of extra attributes, since they require 
non-standard attribute names, and autoprovisioning fails spectacularly 
if your given name attribute is empty or only consists of whitespace (we 
hard code a "-" as the WebEx given name for accounts that lack one, 
using a scripted attribute).

If your tomcat logs indicate relying-party errors, there should be an 
indication of what the problem is (if not in the Tomcat logs, in the 
Shibboleth idp-process.log).

-- 
%%  Christopher A. Bongaarts   %%  cab at umn.edu          %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


More information about the users mailing list