Chapter 3. Using the Enterprise Security Client
If no Phone Home information is stored on the token and there is no global Phone Home parameter,
the user is prompted for the Phone Home URL when a smart card is inserted, as shown in
"Prompt for Phone Home
is formatted. In this case, the company supplies the specific Phone Home URL for the user. After the
user submits the URL, the format process adds the rest of the information to the Phone Home profile.
The format process is not any different for the user.
Figure 3.2. Prompt for Phone Home Information
3.3.3. Adding Phone Home Information to a Token Manually
The Phone Home information can be manually put on a token in one of two ways:
• The preferred method is that the information is burned onto the token at the factory. When the
tokens are ordered from the manufacturer, the company should also supply detailed information on
how the tokens should be configured when shipped.
• If tokens are blank, the company IT department can supply the information when formatting small
groups of tokens.
The following information is used by the Phone Home feature for each smart card in the ~/.redhat/
esc/alphanumeric_string.default/prefs.js file:
• The TPS server and port. For example:
"esc.key.token_ID.tps.url" = "http://server.example.com:7888/nk_service"
• The TPS enrollment interface URL. For example:
18
Information". The other information is supplied and stored when the token
Figure 3.2,
Need help?
Do you have a question about the CERTIFICATE SYSTEM 8.0 - MANAGING SMART CARDS WITH THE ENTERPRISE SECURITY CLIENT 1-23-2010 and is the answer not in the manual?
Questions and answers