Re: [Cosign-discuss] "requested v2 for v3 service"
There was a bug in the userfactor branch that Jorj Bauer at Penn was able to fix. Liam On Tue, Sep 2, 2014 at 6:09 PM, Phil Pishioneri wrote: > On 8/29/14 10:47 AM, Liam Hoekenga wrote: > >> The corresponding error in the apache error log on the cosign server is >> "requested v2 for v3 service". >> >> Don't all versions of the 3.x filter speak v3 of the protocol? >> > > I believe they do. > > -Phil > -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Cosign-discuss mailing list Cosign-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cosign-discuss
[Cosign-discuss] factor creation for userfactor stuff
I realize that the userfactor stuff hasn't been released yet, but I've got questions. I'd envisioned the userfactor checking the login id, checking it against some source listing users that had opted in to 2FA, and then it invoking the the appropriate factor. Is the username available to the userfactor (the script specified using the "userfactor" configuration directive in cosign.conf)? The duo_cosign factor has some code that suggests that it's aware of being invoked by userfactor. Do secondary factors need to be updated to know how to handle being invoked as userfactors? Liam -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ Cosign-discuss mailing list Cosign-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cosign-discuss
