Skip to Content.
Sympa Menu

shibboleth-dev - Re: Strawman AuthnRequest profile #2 (ignore previous)

Subject: Shibboleth Developers

List archive

Re: Strawman AuthnRequest profile #2 (ignore previous)


Chronological Thread 
  • From: Tom Scavo <>
  • To: Scott Cantor <>
  • Cc: Shibboleth Developers <>
  • Subject: Re: Strawman AuthnRequest profile #2 (ignore previous)
  • Date: Wed, 5 Jan 2005 17:27:23 -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=mrtcdkDYgEgbwzAaA4gkSGEy5CvQOGLj10/jtzSbH9+diXJmiXTTREANdK/zY2PAbByJyy7Q1mjiXNMPVc011lk4o3XOSmMXeTLr9lURbRCct3KNNFFwoBN1F54V7y/ojVZr3AmwHElvW/49uLmfmCCYL5BPLuPYIP/QLWwnqVE=
On Mon, 27 Dec 2004 18:01:21 -0500, Scott Cantor
<>
wrote:
>
> As a first cut, these are the obvious and self-evident bits:
>
> @ID
> @Version (fixed at 2.0 if we profile the 2.0 message)
> @IssueInstant (replaces the Shib time parameter, somewhat)
> @Destination (location of Shib SSO Service, aka HS)
> <Issuer> (replaces providerId parameter)
> <ds:Signature> (allows signing)

Oh, now I see why Destination is "obvious"...it is *required* when the
message is signed (with POST, e.g.). Okay, good. :-)

Thanks,
Tom

Archive powered by MHonArc 2.6.16.

Top of Page