Skip to Content.
Sympa Menu

shibboleth-dev - Re: GridShib profile

Subject: Shibboleth Developers

List archive

Re: GridShib profile


Chronological Thread 
  • From: Tom Scavo <>
  • To: Scott Cantor <>
  • Cc: Shibboleth Development <>
  • Subject: Re: GridShib profile
  • Date: Thu, 10 Mar 2005 07:25:56 -0500
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=LkjFbLN7puIDVeY5bWVJp2lEmWxRYn41rtKLwDi+ueK74oNZFncrJ3kqVLnb0sDpm4i4GQ+NPa6PVjJksREUO9Ztk5iJxqu5rqXuqcLmm+/KSx9N4cdOFZ2NH3cz30XW8f1EAWjzavaTnKTroxnCVVb6KGxcFcqCDxNZmeXjfjU=

Doesn't the AA check the veracity of NameQualifier? I guess it
doesn't matter since none of the existing NameIdentifierMapping
implementations satisfy our use case (or so it seems). Are we going
to have to write our own?


On Wed, 9 Mar 2005 21:38:02 -0500, Scott Cantor
<>
wrote:
> My only real comment (aside from the ongoing metadata discussion hopefully
> resulting in a TC-approved extension) is the use of NameQualifier. I find it
> a fairly nasty source of interop headaches and we've been trying to
> de-emphasize it in Shibboleth, at least until 2.0 when it's a little more
> precisely defined.
>
> For an X.500 DN subject, I think I'd omit it or leave it "ignorable" to
> maximize interop with other SAML products. They seem to be pretty arbitrary
> about using it.
>
> -- Scott
>
>



Archive powered by MHonArc 2.6.16.

Top of Page