Shibboleth Developers

[Chad La Joie <>]

A namespace declaration looks like this:

xmlns:PREFIX="some:urn:or:url"

Then you use the declaration like this:

PREFIX:MyCustomType

So, assume a created namespace of "http://fraunhofer.de/idp/handler"; and
assume the custom type that you defined was "SmartCard" like you had.

You declare your namespace, usually at the top of the file, but really
any time before you use it is fine.  So, you'd do this:

<ProfileHandlerGroup
   xmlns="urn:mace:shibboleth:2.0:idp:profile-handler"
   xmlns:custom="http://fraunhofer.de/idp/handler";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="urn:mace:shibboleth:2.0:idp:profile-handler

classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd
                       http://fraunhofer.de/idp/handler
                       classpath:/schema/fraunhofer-custom-handler.xsd">


And then you'd use it as such:

<LoginHandler xsi:type="custom:SmartCard">
<AuthenticationMethod>urn:oasis:names:tc:SAML:2.0:ac:classes:unspecified</AuthenticationMethod>
</LoginHandler>

On 3/12/10 6:02 AM, Jan Peter Stotz wrote:
> Hi Chad,
> 
> could you just be so king and provide a small example. What name space
> to declare use and how to access it in the correspondent element is not
> trivial. From the example I would be able to answer all the outstanding
> questions myself.
> 
> Ciao Jan
> 
> Chad La Joie wrote:
>> Well, I told you what the problem was.  If you're sure that it's
>> something else there isn't a lot I can do to help you.
>>
>> The IdP loads all of its configuration in the same exact what that
>> extensions do.  If you look, there are no import statements in any of
>> those configuration files.  There are only namespace declarations, which
>> is what I said you needed.
> 

-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered