Shibboleth Developers

["Tom Scavo" <>]

On 3/5/06, Scott Cantor 
<>
 wrote:
> > The qualifier attribute is optional.
>
> It's also deprecated for those formats.

Hmm, I missed the phrase "SHOULD be omitted" in SAML2 core.

> > where can I get the authoritative,
> > deployment-wide domain (scope) attribute?
>
> The plugin API would probably have to expose that piece of data so that it
> could be supplied at runtime from the back end, and then you could define a
> default value to use. So it looks about like the smartScope attribute. It
> might be reasonable to extract that into a single setting to avoid the
> duplication. Or one might even be able to use an XML entity to define it
> once and just reuse it in the various XML files and the code wouldn't change
> at all.

Sounds like another Shib 2.0 feature :-) but since I'm working with
Shib 1.3, here's what I'll do:

- I'll make the NameMapping/@qualifier attribute optional.  If it's
omitted, I'll use idp.getProviderId() in the plugin, which is what I'm
doing now.

- I'll make the NameMapping/@template and NameMapping/@regex
attributes required.

If you add a default domain (scope) in Shib 2.0, you can relax the
above requirement.

Tom

PS. Let me know if you'd like me to create a bugzilla for the default
domain feature.