Advanced Authentication (AAf): Use Case: Workers will be on a ship or out of office for 1 – 6 months, and will need to be able to sign into Windows using; Prox Cards, PKI, TOTP, or Fingerprint. They’ll be using LDAP Passwords as the first factor. (According to the bottom of this page, this shouldn't be an issue) Also is there any way to set an expiration time let’s say 6 months or 100 logins before they must authenticate to network and refresh this cache? I know we can with Emergency Password just not sure we can do the same for cached credentials.

Votes

2 Use Case: Workers will be on a ship or out of office for 1 – 6 months, and will need to be able to sign into Windows using; Prox Cards, PKI, TOTP, or Fingerprint. They’ll be using LDAP Passwords as the first factor. (According to the bottom of this page, this shouldn't be an issue) Also is there any way to set an expiration time let’s say 6 months or 100 logins before they must authenticate to network and refresh this cache? I know we can with Emergency Password just not sure we can do the same for cached credentials.

by: Kevin P. | over a year ago | Configuration

We have this for NSL and would like to see same option for AA cached credentials

by: Kevin P. | over a year ago | Configuration

Sorry I clicked "Flagged" in error - trying to figure out how to display the entire description of the Use Case. It cuts off at "Also is there any way to set an" at all screen resolutions.

by: David S. | over a year ago
Please re-enter this request with a shorter title and full use case in the comments.

by: Troy D. | over a year ago
Kevin - please re-enter this request.

Troy

by: Troy D. | over a year ago