shibboleth-dev - RE: Matching auth to attr request
Subject: Shibboleth Developers
List archive
- From: "Scott Cantor" <>
- To: "'Walter Hoehn'" <>, "'Alistair Young'" <>
- Cc: "'Shibboleth Dev Team'" <>
- Subject: RE: Matching auth to attr request
- Date: Tue, 22 Mar 2005 10:46:24 -0500
- Organization: The Ohio State University
> >> No. target specifies nothing you should depend on. The spec is clear
> >> on this
> >> now. I hope to make it a dummy value in 1.3 like it should have been
> >> before.
> > why not remove it altogether if it's not to be used?
>
> Compatibility with existing deployments.
Actually, it's more than that, SAML 1.1 requires a TARGET value. We'd have
to send something regardless.
2.0 does not require RelayState, so omitting it becomes possible in the
future.
-- Scott
- Matching auth to attr request, Alistair Young, 03/17/2005
- RE: Matching auth to attr request, Scott Cantor, 03/17/2005
- Re: Matching auth to attr request, Alistair Young, 03/22/2005
- Re: Matching auth to attr request, Walter Hoehn, 03/22/2005
- RE: Matching auth to attr request, Scott Cantor, 03/22/2005
- RE: Matching auth to attr request, Scott Cantor, 03/22/2005
- Re: Matching auth to attr request, Walter Hoehn, 03/22/2005
- Re: Matching auth to attr request, Alistair Young, 03/22/2005
- RE: Matching auth to attr request, Scott Cantor, 03/17/2005
Archive powered by MHonArc 2.6.16.