[TABS_R id=8782]
You are using ASDM to verify a VPN configuration made by another administrator on an ASA. Please click exhibit to examine the network configuration.
Exhibit:
A user accesses the VPN by typing https://203.0.113.1/BosonUsers in a browser’s location bar. How will the user be authenticated to the VPN? (Select the best answer.)
- by a RADIUS server
- by a TACACS+ server
- by HTTP credentials
- by the local database
- by a certificate
Explanation:
The user will be authenticated to the virtual private network (VPN) by the local database when the user accesses the VPN by typing https://203.0.113.1/BosonUsers in a browser’s location bar. In this scenario, the location BosonUsers is an alias for the Cisco Adaptive Security Appliance (ASA) connection profile named BosonVPN, as shown in the following exhibit:
By navigating to Configuration > Remote Access VPN > Clientless SSL VPN Access> Connection Profiles, you can also determine that the authentication method for the connection profile named BosonVPN is AAA(LOCAL), which indicates that users will be authenticated by using the local Authentication, Authorization, and Accounting (AAA) database instead of a AAA server or a certificate. Although multiple authentication methods can be configured for a single connection profile, in this scenario only the AAA(LOCAL)method is configured for the BosonVPN connection profile. If you were to select the BosonVPN connection profile, you could modify the way in which BosonVPN users authenticate to the VPN, as shown in the following exhibit:
[TABS_R id=8782]