shibboleth-dev - Re: Matching auth to attr request
Subject: Shibboleth Developers
List archive
- From: Walter Hoehn <>
- To: Alistair Young <>
- Cc: "Scott Cantor" <>, "'Shibboleth Dev Team'" <>
- Subject: Re: Matching auth to attr request
- Date: Tue, 22 Mar 2005 09:24:32 -0600
On Mar 22, 2005, at 5:17 AM, Alistair Young wrote:
No. target specifies nothing you should depend on. The spec is clear on thiswhy not remove it altogether if it's not to be used?
now. I hope to make it a dummy value in 1.3 like it should have been before.
Compatibility with existing deployments.
does <Target> in arp.site.xml have any relation to the GET target? or is it used with providerId or NameQualifier? When deciding what attributes to release it can only go via providerId but you say it may not be set correctly, in which case it must be NameQualifier.
What would your advice be for specifying <Target> in a <Rule>?
No relation in Shib 1.2+. The <Requester/> element always matches against the providerId of the SP.
-Walter
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- 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.