On 8 February 2012 17:18, Ryan Hurst <[email protected]> wrote:
> Steve, > > Thank you. > > I actually contributed to RFC 3709 and I believe made Windows the first > platform to support it, that said the branding element I am referring to in > this case is different. > > When designing a user experience one picks colors, typefaces, layout and > workflow; for example consider Coke "red" and type typical Coke typography; > if the authentication experience is not consistent with the design goals of > a site adoption will only happen when security is seen more important that > design and ease of use. > > As long as that is the case in this world of consumerization of IT I don't > expect client certificates to be used outside of closed communities. > Client certs do not need to interfere with the branding experience. For example, http://www.browserauth.net/ shows how to use them without touching the site's ability to fully control the user experience. > > Ryan > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On > Behalf Of Stephen Kent > Sent: Wednesday, February 08, 2012 8:57 AM > To: Ryan Hurst > Cc: 'Joe St Sauver'; [email protected] > Subject: Re: [therightkey] Client Certificate Usability (was RE: Will the > real RPF please stand up?) > > Ryan, > > That's a good list of additional problems associated with widespread use of > client certs. > > Note that re the "branding" issue, there is a cert extension that allows > for > logos to be embedded in certs, although the focus for this is really server > vs. client certs. > > Steve > _______________________________________________ > therightkey mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/therightkey > > _______________________________________________ > therightkey mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/therightkey > >
_______________________________________________ therightkey mailing list [email protected] https://www.ietf.org/mailman/listinfo/therightkey
