Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

3.3. Configuring Phone Home

The Phone Home feature in the Enterprise Security Client associates information within each smart card with information that points to distinct TPS servers and Enterprise Security Client UI pages. Whenever the Enterprise Security Client accesses a new smart card, it can connect to the TPS instance and retrieve the Phone Home information.
Phone Home retrieves and then caches this information; because the information is cached locally, the TPS subsystem does not have to be contacted each time a formatted smart card is inserted.
The information can be different for every key or token, which means that different TPS servers and enrollment URLs can be configured for different corporate or customer groups. Phone Home makes it possible to configure different TPS servers for different issuers or company units, without having to configure the Enterprise Security Client manually to locate the correct server and URL.

Note

In order for the TPS subsystem to utilize the Phone Home feature, Phone Home must be enabled in the TPS configuration file, as follows: 
op.format.userKey.issuerinfo.enable=true
op.format.userKey.issuerinfo.value=http://server.example.com
Copy to Clipboard Toggle word wrap

3.3.1. About Phone Home Profiles
Copier lien

The Enterprise Security Client is based on Gnome. When the Enterprise Security Client caches information for each token, the information is stored in the user's configuration file. The next time the Enterprise Security Client is launched, it retrieves the information from the configuration file instead of contacting the server again.
When a smart card is inserted and Phone Home is triggered, the Enterprise Security Client first checks the token for the Phone Home URL, which is the default URL the Enterprise Security Client uses to try connecting to the TPS.
If there is no Phone Home information on the token, users can specify the Phone Home URL value manually by clicking the Phone Home button in the Enterprise Security Client UI. See Section 3.3.2, “Setting the Phone Home URL”. 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.

3.3.2. Setting the Phone Home URL
Copier lien

The Enterprise Security Client needs to be configured to communicate with the TPS; this is done via the Phone Home URL. Formatted tokens (they can be formatted by the manufacturer or by your IT department) already have this URL set. If a token is unformatted, the Enterprise Security Client cannot find the Phone Home URL: such blank tokens require to define the URL manually.
The Phone Home button allows users to specify the Phone Home URL:
  1. Once a blank token is inserted, click the Phone Home button in the Enterprise Security Client UI to open a configuration dialog.
  2. In the TPS Config URI field, fill in the new TPS URL.
  3. Click OK to save. Once the new Phone Home URL is correctly configured, the rest of the information is retrieved and added to the Phone Home profile.
Phone Home URL Configuration
View larger image
Phone Home URL Configuration

Figure 3.2. Phone Home URL Configuration

3.3.3. Configuring the TPS to Use Phone Home
Copier lien

The Phone Home feature and the different type of information it uses only work when the TPS is properly configured to use Phone Home. If not, TPS ignores this feature. Phone Home is configured in the phoneHome.xml in the /var/lib/pki/pki-tomcat/tps/conf/ directory; this prints the Phone Home information to XML.
Example 3.1, “TPS Phone Home Configuration File” shows an example XML file used by the TPS subsystem to configure the Phone Home feature.

Example 3.1. TPS Phone Home Configuration File

<ServiceInfo><IssuerName>Example Corp</IssuerName>
    <Services>
        <Operation>http://server.example.com:7888/nk_service ## TPS server URL
        </Operation>
        <UI>http://server.example.com:7888/cgi_bin/esc.cgi   ## Optional
Enrollment UI
        </UI>
        <EnrolledTokenBrowserURL>http://www.test.url.com   ## Optional
enrolled token url
        </EnrolledTokenBrowserURL>
    </Services>
</ServiceInfo>
Copy to Clipboard Toggle word wrap
The TPS configuration URI is the URL of the TPS server which returns the rest of the Phone Home information to the Enterprise Security Client. An example of this URL is http://localhost:8443/tps/phoneHome; the URL can reference the machine name, fully-qualified domain name, or an IPv4 or IPv6 address, as appropriate. When the TPS configuration URI is accessed, the TPS server is prompted to return all of the Phone Home information to the Enterprise Security Client.
To test the URL of the Smart Card server, enter the address in the TPS Config URI field, and click Test URL.
If the server is successfully contacted, a message box indicates success. If the test connection fails, an error dialog appears.
Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat