[an error occurred while processing the directive]

	cosign-discuss at umich.edu
	general discussion of cosign development and deployment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cosign Multi-factor Authentication Spec

To: "Carson, Cassandra" <clcarson@xxxxxxxxxxxx>
Subject: Re: Cosign Multi-factor Authentication Spec
From: Wesley Craig <wes@xxxxxxxxx>
Date: Tue, 11 Oct 2005 16:09:38 -0400
Cc: "Meyer, Seth" <smeyer@xxxxxxxxxxxx>, "Linderman, Mark" <mlinderm@xxxxxxxxxxxx>, "cosign-discuss Discussion" <cosign-discuss@xxxxxxxxx>, <mais.twofact.tech@xxxxxxxxx>, "Dandamudi, Bindu" <bdandamu@xxxxxxxxxxxx>, "Thomas, Katarina" <kkit@xxxxxxxxxxxx>
In-reply-to: <27AE62311E924149926D0A0B86ED54870127D237@bf-it-equinox02.bf.umich.edu>
References: <27AE62311E924149926D0A0B86ED54870127D237@bf-it-equinox02.bf.umich.edu>

On 11 Oct 2005, at 12:08, Carson, Cassandra wrote:

Just to be sure....Will this also work in reverse? Meaning the user visited henonprodop, but provided their token and then went to heprodop. Since the cookie had the second factor, they would be accepted at heprodop and not be prompted to provide the token again.

Yes, that's exactly right.

:wes

References:
- RE: Cosign Multi-factor Authentication Spec
  - From: Carson, Cassandra

Prev by Date: RE: Cosign Multi-factor Authentication Spec
Next by Date: RE: Cosign Multi-factor Authentication Spec
Previous by thread: RE: Cosign Multi-factor Authentication Spec
Next by thread: RE: Cosign Multi-factor Authentication Spec
Index(es):
- Date
- Thread

[an error occurred while processing the directive]