Delete the default auth table mapping policy

Create auth table mapping policies that route users to specific resources

Create Resource Access policies that permit access to specific resources

Create Source Interface policies that route users to specific resources

By adding two separate connections in the connections dialog box

By adding two separate intranet Controllers under the configuration hierarchy

By adding one intranet Controller and one SA under the configuration hierarchy

By adding two URLs under a connection in the connections dialog box

Junos Pulse should be configured with location awareness rules configured.

Odyssey Access Client should be installed with Host Checker configured to check the client's location.

Junos Pulse should be configured with all components installed.

Agentless access should be enabled so that clients can connect to any service without concern for installing an agent.

EAP-MD5 is not supported by the Junos Pulse Access Control Service

EAP-MD5 requires passwords to be stored in an encrypted format.

EAP-MD5 requires passwords to be stored in a clear text format.

EAP-MD5 performs a real time hash of the handset's MAC address.

Dynamic auth table mapping is not enabled.

A successful authentication attempt will result in a new authentication table entry, which will be delivered only to the Junos enforcer protecting the network from which the user has authenticated.

To create a static auth table mapping, you must delete the default policy.

The default policy applies only to the factory-default role User.

Configure each user account in the auth server with the appropriate Odyssey Access Client preconfiguration files.

Configure the role-mapping rules with the appropriate Odyssey Access Client preconfiguration files.

Ensure that merge roles is selected in the role-mapping rules.

Ensure that the first role a user is mapped to is the role with the appropriate Odyssey Access Client preconfiguration file.