users are forever changing machines or using Internet cafes, libraries, etc to connect to the Internet. How does BrowserKey handle this?
Because BrowserKey is based on client machine authentication, it is intended for use on client machines owned/administered by the end-user on which they can install software. We recommend creating an intentional “backdoor” to your site that only relies on traditional web-based username and password “user authentication” (bypassing the BrowserKey system), and that you supply information relative to this “backdoor” only to end-users who require the ability to connect from random client machines that they do not own/administer. You may wish to require that your customers/end-users purchase a special (probably more expensive) license for the right to access this “backdoor.
Because BrowserKey is based on client machine authentication, it is intended for use on client machines owned/administered by the end-user on which they can install software. We recommend creating an intentional “backdoor” to your site that only relies on traditional web-based username and password “user authentication” (bypassing the BrowserKey system), and that you supply information relative to this “backdoor” only to end-users who require the ability to connect from random client machines that they do not own/administer.
Related Questions
- If I use an internet server to connect two machines that are pretty close together (say on different subnets of the same network), won that cause a lot of delay?
- Is it really worth learning Dvorak given that friend/libraries/internet cafes all use QWERTY?
- Can off-site users connect to ACUMEN over the internet?
