Choose the BEST reason why.

You find that Users are not prompted for authentication when they access their Web servers, even though you
have created an HTTP rule via User Authentication. Choose the BEST reason why.

You find that Users are not prompted for authentication when they access their Web servers, even though you
have created an HTTP rule via User Authentication. Choose the BEST reason why.

A.
You checked the cache password on desktop option in Global Properties.

B.
Another rule that accepts HTTP without authentication exists in the Rule Base.

C.
You have forgotten to place the User Authentication Rule before the Stealth Rule.

D.
Users must use the SecuRemote Client, to use the User Authentication Rule.



Leave a Reply 2

Your email address will not be published. Required fields are marked *


aa

aa

Password Caching

When the timeout expires, the user will be asked to authenticate again. If password-caching is enabled, clients will supply the cached password automatically and the authentication will take place transparently to the user. In other words, the user will not be aware that re-authentication has taken place.

Password caching is possible only for multiple-use passwords. If the user’s authentication scheme implement one-time passwords (for example, SecurID), then passwords cannot be cached, and the user will be asked to re-authenticate when the authentication time-out expires. For these schemes, this feature should not be implemented.

To configure password caching:

From Menu, select Global Properties.
From the navigation tree, click Remote Access > Endpoint Security VPN.
In Enable password caching, select an option.
If Password caching is enabled, in Cache password for, select the amount of minutes it is cached for.

mailto

mailto

Password Caching

When the timeout expires, the user will be asked to authenticate again. If password-caching is enabled, clients will supply the cached password automatically and the authentication will take place transparently to the user. In other words, the user will not be aware that re-authentication has taken place.

Password caching is possible only for multiple-use passwords. If the user’s authentication scheme implement one-time passwords (for example, SecurID), then passwords cannot be cached, and the user will be asked to re-authenticate when the authentication time-out expires. For these schemes, this feature should not be implemented.

https://sc1.checkpoint.com/documents/R80.10/SmartConsole_OLH/EN/html_frameset.htm?topic=QqnKn-PHQBc1DgFFVLLmfA2