shibboleth-dev - Re: release of authentication assertion
Subject: Shibboleth Developers
List archive
- From: Velpi <>
- To:
- Subject: Re: release of authentication assertion
- Date: Fri, 22 Sep 2006 17:00:01 +0200
I know there are a number of technical considerations to this and haven't completely thought through how this would actually be implemented, but I wanted to bring it up anyway. Has anyone else ever had similar concerns? Does this seem like a reasonable concern? Does this sound like something that may be more easily addressed in Shib2 with the planned changes to the ARP structure?
We have exactly the same concerns at K.U.Leuven. The artifact protocol requires an SP to have an entry in the metadata for any statement to be released, so maybe there can be found an easy solution in that area: if it's possible to force all/unauthenticated providers to use the artifact protocol then that issue could be solved easily in a Shib1.3 environment.
-- Velpi
- release of authentication assertion, Will Norris, 09/21/2006
- RE: release of authentication assertion, Scott Cantor, 09/21/2006
- Re: release of authentication assertion, Walter Hoehn, 09/21/2006
- Re: release of authentication assertion, Thomas Lenggenhager, 09/22/2006
- RE: release of authentication assertion, Scott Cantor, 09/22/2006
- Re: release of authentication assertion, Velpi, 09/22/2006
- RE: release of authentication assertion, Scott Cantor, 09/22/2006
- Re: release of authentication assertion, Brendan Bellina, 09/22/2006
- RE: release of authentication assertion, Scott Cantor, 09/22/2006
- Re: release of authentication assertion, Brendan Bellina, 09/22/2006
- RE: release of authentication assertion, Scott Cantor, 09/22/2006
- RE: release of authentication assertion, Scott Cantor, 09/21/2006
Archive powered by MHonArc 2.6.16.