shibboleth-dev - RE: release of authentication assertion
Subject: Shibboleth Developers
List archive
- From: "Scott Cantor" <>
- To: <>
- Subject: RE: release of authentication assertion
- Date: Fri, 22 Sep 2006 11:15:08 -0400
- Organization: The Ohio State University
> 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.
The fact that the old WAYF model makes using other protocols impossible
aside, no, there's no way to force it in 1.3 without changing the code, in
which case you just need to implement the trivial change of adding a "don't
allow unknown requests" option for POST.
-- Scott
- 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.