shibboleth-dev - Re: attribute queries

Subject: Shibboleth Developers

List archive

Re: attribute queries

From: Tom Scavo <>
To: Scott Cantor <>
Cc: Walter Hoehn <>, Shibboleth Development <>
Subject: Re: attribute queries
Date: Mon, 28 Mar 2005 18:35:50 -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=gln9UVSegdd6K3RlYQF2Zebrksx5dlvkmljTNt6MiInX9iDYWPAHTbEROJTHVSxmTmor4qDpgcSd6iBI5ggtMNGy46RQlimnWyqAHy9GB/zNEJY0WHpMqulmorEk0T32YEjr5ZJDWi3GueG78cn8Fy9e60xqz2o7Xi9AHf+FbTc=

On Mon, 28 Mar 2005 12:10:13 -0500, Scott Cantor
<>
wrote:
>
> We define Resource to be "requester". Issuer for all intents and purposes.
> Since that only accomodates system entity names and not generally people at
> the moment (maybe XRIs will change all that), the LionShare plan was to
> avoid overloading it and use a fixed value or just omit it and use an HTTP
> header, I don't really remember what was decided.

Doesn't a separate AA endpoint also solve the problem? A dedicated
LionShare (or GridShib) endpoint would also address your earlier
concern about firewalls, wouldn't it?

Tom

RE: attribute queries, (continued)
- RE: attribute queries, Frank Siebenlist, 03/29/2005
  - RE: attribute queries, Scott Cantor, 03/29/2005
    - Re: attribute queries, Frank Siebenlist, 03/30/2005
      - RE: attribute queries, Scott Cantor, 03/30/2005
        
        Re: attribute queries, Frank Siebenlist, 03/30/2005
        
        RE: attribute queries, Scott Cantor, 03/30/2005
        
        Re: attribute queries, Tom Scavo, 03/30/2005
        RE: attribute queries, Scott Cantor, 03/30/2005

List archive

Re: attribute queries