7.1

Table Of Contents
Option Action
Authenticatio
n type
Enter the authentication protocol that is supported by the RADIUS server. Either PAP, CHAP,
MSCHAP1, OR MSCHAP2.
Shared secret Enter the shared secret that is used between the RADIUS server and the VMware Identity Manager
service.
Server
timeout in
seconds
Enter the RADIUS server timeout in seconds, after which a retry is sent if the RADIUS server does
not respond.
Realm Prex (Optional) The user account location is called the realm.
If you specify a realm prex string, the string is placed at the beginning of the user name when the
name is sent to the RADIUS server. For example, if the user name is entered as jdoe and the realm
prex DOMAIN-A\ is specied, the user name DOMAIN-A\jdoe is sent to the RADIUS server. If
you do not congure these elds, only the user name that is entered is sent.
Realm Sux (Optional) If you specify a realm sux, the string is placed at end of the user name. For example, if
the sux is @myco.com, the username jdoe@myco.com is sent to the RADIUS server.
Login page
passphrase
hint
Enter the text string to display in the message on the user login page to direct users to enter the
correct Radius passcode. For example, if this eld is congured with AD password  and then
SMS passcode, the login page message would read Enter your AD password  and then SMS
passcode. The default text string is RADIUS Passcode.
5 You can enable a secondary RADIUS server for high availability.
Congure the secondary server as described in step 4.
6 Click Save.
What to do next
Add the RADIUS authentication method to the default access policy. Select Administration > Directories
Management > Policies and click Edit Default Policy to edit the default policy rules to add the RADIUS
authentication method to the rule in the correct authentication order.
Configuring a Certificate or Smart Card Adapter for Use with
Directories Management
You can congure x509 certicate authentication to allow clients to authenticate with certicates on their
desktop and mobile devices or to use a smart card adapter for authentication. Certicate-based
authentication is based on what the user has (the private key or smart card), and what the person knows
(the password to the private key or the smart-card PIN.) An X.509 certicate uses the public key
infrastructure (PKI) standard to verify that a public key contained within the certicate belongs to the user.
With smart card authentication, users connect the smart card with the computer and enter a PIN.
The smart card certicates are copied to the local certicate store on the user's computer. The certicates in
the local certicate store are available to all the browsers running on this user's computer, with some
exceptions, and therefore, are available to a Directories Management instance in the browser.
n
Using User Principal Name for Certicate Authentication on page 107
You can use certicate mapping in Active Directory. Certicate and smart card logins uses the user
principal name (UPN) from Active Directory to validate user accounts. The Active Directory accounts
of users aempting to authenticate in the Directories Management service must have a valid UPN that
corresponds to the UPN in the certicate.
n
Certicate Authority Required for Authentication on page 107
To enable logging in using certicate authentication, root certicates and intermediate certicates must
be uploaded to the Directories Management.
Configuring vRealize Automation
106 VMware, Inc.