HTTP-POST vs. ECP

[Leif Johansson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/16/2012 08:29 PM, Douglas E. Engert wrote:
> 
> 
> On 7/14/2012 2:23 PM, Cantor, Scott wrote:
>> On Jul 14, 2012, at 9:11 AM, "Tom Scavo" <trscavo at gmail.com>
>> wrote:
>> 
>>> On Fri, Jul 13, 2012 at 5:55 PM, Cantor, Scott
>>> <cantor.2 at osu.edu> wrote:
>>>> 
>>>> In practice, you see basic-auth and client TLS as the main
>>>> options (and we all laugh at the client TLS thing, but it's
>>>> more or less free on the IdP end to support it).
>>> 
>>> I'm up for a good laugh, can you elaborate about client TLS in
>>> this case?
>> 
>> I just meant all the things that "support" client TLS neatly
>> ignore the part where it's undeployable for ordinary users.
>> 
> 
> It woks nice with Windows AD and Auto Enroll certificates, and
> works with Smart Cards, but then again these require the admin to
> set things up.

Right. Thats what a tightly controlled enterprise environment looks like
today. Problem is if you want to live in a consumer-oriented world or in
a post-AD-enterprise.

	Cheers Leif


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAEXfEACgkQ8Jx8FtbMZndlXgCcDcz9zMdCifCe9EHkN2V3v6DF
eZIAn3Hn1U1E6HCe9rji56I4DWVX+hAL
=Wvya
-----END PGP SIGNATURE-----