Computing session multi-factor authentication
A computing device includes a memory and a processor configured to cooperate with the memory to receive a connection lease and a token from a client device, with the token being generated responsive to the client device completing multi-factor authentication (MFA) with a provider of MFA. The processor further verifies, responsive to unavailability of the provider of MFA, that the client device has previously performed MFA based upon the token, and connect the client device to a computing session with use of the connection lease and responsive to the verification that the client device has performed MFA.
1. A computing device comprising:
a memory and a processor configured to cooperate with the memory to:
receive a connection lease and a token from a client device, the token being generated responsive to the client device completing Multi-Factor Authentication (MFA) with a provider of MFA in compliance with an MFA policy;
verify, responsive to unavailability of the provider of MFA, that the client device has previously performed MFA based upon the token and a secondary information, wherein the secondary information is selected from an IP address for a prior successful MFA, a latency associated with communications with the client device, or a combination thereof;
change a level of access associated with a computing session responsive to an identity provider being offline; and
connect the client device to the computing session with use of the connection lease and responsive to the verification that the client device has performed MFA, wherein the connecting comprises selecting an appropriate policy tier from a plurality of tiers of the MFA policy based on a user context.
2. The computing device of claim 1 wherein the connection lease includes data about the MFA; and wherein the processor is further configured to verify that the token is valid based upon the data, and connect the client device to the computing session also responsive to verification of the token being valid.
3. The computing device of claim 1 wherein the processor verifies that the client device has performed MFA for external connections outside of a network.
4. The computing device of claim 1 wherein the token has an expiration, and wherein the processor requests MFA authentication from the MFA provider prior to the expiration of the token.
5. The computing device of claim 4 wherein the processor is further configured to delay the MFA authentication request responsive to an identity provider being offline and extend the connection to the computing session during the delay.
6. The computing device of claim 1 wherein the MFA comprises generating a Time-based One-time Password (TOTP) based upon a key, and wherein the processor is further configured to receive the key and verify that the client device has performed MFA based upon the key.
7. A method comprising:
at a computing device,
receiving a connection lease and a token from a client device, the token being generated responsive to the client device completing Multi-Factor Authentication (MFA) with a provider of MFA in compliance with an MFA policy;
verifying, responsive to unavailability of the provider of MFA, that the client device has previously performed MFA based upon the token and a secondary information, wherein the secondary information is selected from an IP address for a prior successful MFA, a latency associated with communications with the client device, or a combination thereof;
changing a level of access associated with a computing session responsive to an identity provider being offline; and
connecting the client device to the computing session with use of the connection lease and responsive to the verification that the client device has performed MFA, wherein the connecting comprises selecting an appropriate policy tier from a plurality of tiers of the MFA policy based on a user context.
8. The method of claim 7 wherein the connection lease includes data about the MFA; wherein verifying further comprises verifying that the token is valid based upon the data; and wherein connecting further comprises connecting the client device to the computing session also responsive to verification of the token being valid.
9. The method of claim 7 wherein verifying comprises verifying that the client device has performed MFA for external connections outside of a network.
10. The method of claim 7 wherein the token has an expiration, and further comprising, at the computing device, requesting MFA authentication from the MFA provider prior to the expiration of the token.
11. The method of claim 7 wherein the MFA comprises generating a Time-based One-time Password (TOTP) based upon a key, and further comprising, at the computing device, receiving the key and verifying that the client device has performed MFA based upon the key.
12. A non-transitory computer-readable medium having computer-executable instructions for causing a computing device to perform steps comprising:
receiving a connection lease and a token from a client device, the token being generated responsive to the client device completing Multi-Factor Authentication (MFA) with a provider of MFA in compliance with an MFA policy;
verifying, responsive to unavailability of the provider of MFA, that the client device has previously performed MFA based upon the token and a secondary information, wherein the secondary information is selected from an IP address for a prior successful MFA, a latency associated with communications with the client device, or a combination thereof;
changing a level of access associated with a computing session responsive to an identity provider being offline; and
connecting the client device to the computing session with use of the connection lease and responsive to the verification that the client device has performed MFA, wherein the connecting comprises selecting an appropriate policy tier from a plurality of tiers of the MFA policy based on a user context.
13. The non-transitory computer-readable medium of claim 12 wherein the connection lease includes data about the MFA; wherein verifying further comprises verifying that the token is valid based upon the data; and wherein connecting further comprises connecting the client device to the computing session also responsive to verification of the token being valid.
14. The non-transitory computer-readable medium of claim 12 wherein verifying comprises verifying that the client device has performed MFA for external connections outside of a network.
15. The non-transitory computer-readable medium of claim 12 wherein the token has an expiration, and further having computer-executable instructions for causing the computing device to request MFA authentication from the MFA provider prior to the expiration of the token.
16. The non-transitory computer-readable medium of claim 12 wherein the MFA comprises generating a Time-based One-time Password (TOTP) based upon a key, and further having computer-executable instructions for causing the computing device to receive the key and verify that the client device has performed MFA based upon the key.