Skip to Content.
Sympa Menu

shibboleth-dev - Re: CryptoHandleGenerator

Subject: Shibboleth Developers

List archive

Re: CryptoHandleGenerator


Chronological Thread 
  • From: Tom Scavo <>
  • To: Walter Hoehn <>
  • Cc: Scott Cantor <>, Shibboleth Development <>, Von Welch <>
  • Subject: Re: CryptoHandleGenerator
  • Date: Thu, 17 Mar 2005 14:07:09 -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=gS06cMkAzvnneno/5n1YRybUvxVXoWBScQoTIWRBaPOdGXEwNTdwhs36aaxwNm9BKvR38RLYh/nT4O2+QEaHXbmwfL2C9PRkVbf1IvwHELHe4iTc8F42GWyvYdZnxyubkJWQSawLFjAOKr0j37DbriOSd713M3qJJCZNrEE5Mmc=

On Thu, 17 Mar 2005 12:51:10 -0600, Walter Hoehn
<>
wrote:
> There isn't anything in place that does this. I'm trying to imagine
> something generic that does it and isn't more complicated for a site
> than just writing a custom mapping according to their needs...

What about LionShare? LionShare will require the following
NameMapping element, I believe:

<!-- CryptoShibHandle -->
<NameMapping
xmlns="urn:mace:shibboleth:namemapper:1.0"
id="..."
format="urn:mace:shibboleth:1.0:nameIdentifier"
type="CryptoHandleGenerator"
handleTTL="1800"/>

Doesn't that preclude the following NameMapping element?

<!-- SharedMemoryShibHandle -->
<NameMapping
xmlns="urn:mace:shibboleth:namemapper:1.0"
id="..."
format="urn:mace:shibboleth:1.0:nameIdentifier"
type="SharedMemoryShibHandle"
handleTTL="1800"/>

If the NameMapper class invoked the two mappings in sequence
(SharedMemoryShibHandle, then CryptoShibHandle), wouldn't that solve
the problem?

> I might be wrong, but I don't envision this being a common use case.

Well, GridShib is a use case, it seems. GridShib wants to "own" the
X509SubjectName format, but surely there are deployments that are
currently using this format in other ways. Without some kind of
chained mapping, the two will not coexist.

Thanks,
Tom



Archive powered by MHonArc 2.6.16.

Top of Page