Skip to Content.
Sympa Menu

mfa-interop - RE: Workday (was Re: [MFA-Interop] Agenda for the 2/18/2016 MFA Interoperability Profile Working Group call)

Subject: MFA Interop Working Group

List archive

RE: Workday (was Re: [MFA-Interop] Agenda for the 2/18/2016 MFA Interoperability Profile Working Group call)


Chronological Thread 
  • From: "Cantor, Scott" <>
  • To: Liam Hoekenga <>, "MFA Interoperability Profile Working Group" <>
  • Subject: RE: Workday (was Re: [MFA-Interop] Agenda for the 2/18/2016 MFA Interoperability Profile Working Group call)
  • Date: Thu, 18 Feb 2016 15:14:42 +0000
  • Accept-language: en-US
  • Authentication-results: spf=pass (sender IP is 164.107.81.222) smtp.mailfrom=osu.edu; incommon.org; dkim=none (message not signed) header.d=none;incommon.org; dmarc=bestguesspass action=none header.from=osu.edu;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:23
> I know that the Workday example is just an example, but it sets an
> unmaintainable precedent should it see implementation. I would rather see
> MFA triggered by a vendor-independent authentication context.

I think it needs to be "an arbitrary" authentication context, with the
deployer making that choice. Best case, it's "arbitrary context(s)" but that
may be asking too much, we know that as soon as you go from 1 to N the heads
of all recent college graduates in CS apparently blow up.

-- Scott


Archive powered by MHonArc 2.6.16.

Top of Page