Skip to Content.
Sympa Menu

shibboleth-dev - Re: authentication authority

Subject: Shibboleth Developers

List archive

Re: authentication authority


Chronological Thread 
  • From: Tom Scavo <>
  • To:
  • Subject: Re: authentication authority
  • Date: Fri, 14 Oct 2005 14:17:51 -0400
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kyRNkBbTEn5pOineTJdOo816h+i9d6c+NGmF9zd4Dk6Ez3FoeoX/gajldVH5Xx+/jWA+hWJOZUY2rlAbLBy9qPxWw6C6jCGnhDioUivL0XNr1HcTvWjmSfRA5hsGqc1o9Alde8JoWDf8c1f7/X5yEbpOS8x9fxvlhKvV3t0RO0I=

On 10/14/05, Brent Putman
<>
wrote:
>
> I think what Scott proposed, and what you are looking for, is very
> similar to what Chad presented at GridWorld/GGF last week. In a
> nutshell it involves using SAML 2.0 AuthnRequest and
> RequestedAuthnContext. See Chad's slides available here:
>
> http://www.ggf.org/GGF15/ggf_events_schedule_UserManagement.htm

Brent, thanks for the pointer. I was at Chad's excellent presentation
last week.

> We will probably be implementing something very similar for another
> non-Grid fat client-server oriented project (Sentinel) - yes, by
> non-spec-compliant backporting it to Shib 1.3 (that is, not compliant to
> SAML 1.1), and implementing an IdP handler which can process the
> AuthnRequest for various cred types (username/password, client cert,
> biometrics, etc) and issue an authentication assertion.

Cool.

> I actually think his proposal is very relevant to this entire thread.

Chad's proposal is based on WS-*, and as you probably know,
transport-level security is still the default in GT4. Message-level
security, although it's included in GT4, will remain mostly a research
topic until the standards have solidified and the performance issues
have been addressed.

One of our requirements is that GridShib MUST work with pre-WS GT4
deployments (which is most of them), which means we don't have the
luxury of SAML 2.0 and WS-*, at least for this first iteration of the
technology. So our use case is considerably more constrained than
yours.

Tom



Archive powered by MHonArc 2.6.16.

Top of Page