Skip to Content.
Sympa Menu

shibboleth-dev - Re: [Shib-Dev] Custom IdP Extension - example schema does not work

Subject: Shibboleth Developers

List archive

Re: [Shib-Dev] Custom IdP Extension - example schema does not work


Chronological Thread 
  • From: Jim Fox <>
  • To: "" <>
  • Subject: Re: [Shib-Dev] Custom IdP Extension - example schema does not work
  • Date: Thu, 11 Mar 2010 09:53:36 -0800 (PST)



I've used that guide several times. Although I see that my xsd files have explicit namespace declarations everywhere, and the default namespace is the profile handler's, i.e.,

<xsd:schema
targetNamespace="urn:mace:shibboleth:2.0:idp:ext:ecp:profile-handler"
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns="urn:mace:shibboleth:2.0:idp:profile-handler"
xmlns:idpprofile="urn:mace:shibboleth:2.0:idp:profile-handler"
xmlns:ecpprofile="urn:mace:shibboleth:2.0:idp:ext:ecp:profile-handler"
elementFormDefault="qualified">

<xsd:import namespace="urn:mace:shibboleth:2.0:idp:profile-handler"

schemaLocation="classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd"/>

and etc.


Don't remember if that was necessary though.

Jim


On Thu, 11 Mar 2010, Jan Peter Stotz wrote:

Date: Thu, 11 Mar 2010 08:01:51 -0800
From: Jan Peter Stotz
<>
To:
""

<>
Reply-To:
""

<>
Subject: [Shib-Dev] Custom IdP Extension - example schema does not work

Hi Shibboleth developers,

based on the IdP extension guide [1] I implemented a custom
LoginHandler. The main problem is that the presented schema files do not
work - to me it looks like a general problem so that I am asking myself
how the presented xsd [2] file could ever work.

When using this schema SAX throws the following exception:

Caused by: org.xml.sax.SAXParseException: src-import.3.2: An <import>
element information item that had no namespace attribute was found,
so the imported document cannot have a targetNamespace attribute.
However, the targetNamespace
'urn:mace:shibboleth:2.0:idp:profile-handler' was found in the
imported document.

As I understand it the "targetNamespace" SAX complains about is part of
the imported XML Schema file "shibboleth-2.0-idp-profile-handler.xsd".
That file is part of the IDP and therefore I can not change it, but the
example says I have to import it. From my point of view this problem is
unsolvable...

Has anybody successfully used the one of the example extensions with
shibboleth-idp-2.1.5? Do the examples really work?

Best Regards,
Jan

BTW: I would like to share my made experience by adding certain
information to the Shibboleth 2 Documentation Wiki - but I can not run
an IDP just for editing a wiki. Is there no simple approach for getting
an account?

[1] https://spaces.internet2.edu/display/SHIB2/IdPDevCustomExtension
[2]
https://spaces.internet2.edu/display/SHIB2/IdPDevExtLoginHandler#IdPDevExtLoginHandler-ExtensionSchema





Archive powered by MHonArc 2.6.16.

Top of Page