"http://www.test.example.com"
The Phone Home feature and the different type of information used by it only work when the
TPS has been properly configured to use Phone Home. If the TPS is not configured for Phone
Home, then this feature is ignored.
Example 4.1, “TPS Phone Home Configuration File”
shows
an example XML file used by the TPS subsystem to configure the Phone Home feature.
<ServiceInfo><IssuerName>Example Corp</IssuerName>
<Services>
<Operation>http://tps.example.com:12443/nk_service ## TPS server URL
</Operation>
<UI>http://tps.example.com:12443/cgi_bin/esc.cgi
## Optional
Enrollment UI
</UI>
<EnrolledTokenBrowserURL>http://www.test.url.com
## Optional
enrolled token url
</EnrolledTokenBrowserURL%gt;
</Services>
</ServiceInfo>
Example 4.1. TPS Phone Home Configuration File
Phone Home is triggered automatically when a security token is inserted into a machine. The
system immediately attempts to read the Phone Home URL from the token and to contact the
TPS server.
If no Phone Home information is stored on the token, the the user is prompted for the Phone
Home URL, as shown in
Figure 4.1, “Prompt for Phone Home Information”
. The other
information is supplied and stored when the token 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.
Phone Home
23
Summary of Contents for CERTIFICATE SYSTEM ENTERPRISE - SECURITY GUIDE
Page 2: ...Red Hat Certificate System Enterprise Security Client Guide ...
Page 4: ...Red Hat Certificate System Enterprise Security Client Guide ...
Page 6: ...vi ...
Page 10: ...4 ...
Page 12: ...6 ...
Page 18: ...Figure 3 5 Beginning Installation Chapter 3 Installation 12 ...
Page 26: ...20 ...
Page 59: ...Index 53 ...
Page 60: ...54 ...
