OPTIONS¶

/path/to/cert.pem

Gives the full path and filename to the PEM certificate for the given subscription, product, or system. This is required.

EXAMPLES¶

The statistics for an entitlement certificate show both the DER size and the number of content sets, among other information:

* Type (entitlement certificate)

* Version (of the certificate style); newer versions will be 3.x, with better performance for handling large content sets

* DER size, which gives the size of the certificate contents (not the size of the certificate file itself)

* Key size, for the associated key file, in bytes

* The total number of available content sets in the subscription

For example:

[root@server ~]# rct stat-cert /etc/pki/entitlement/2027912482659389239.pem
Type: Entitlement Certificate
Version: 1.0
DER size: 47555b
Subject Key ID size: 553b
Content sets: 100

While the size of the certificate is less of an issue for identity and product certificates (which are quite small), the stat-cert command can still be used to view the size and statistics of the certificates.

For a product certificate, the stat-cert command shows:

* Type (product certificate)

* Version (of the certificate style)

* DER size, which gives the size of the certificate contents (not the size of the certificate file itself)

For example:

[root@server ~]# rct stat-cert /etc/pki/product/69.pem
Type: Product Certificate
Version: 1.0
DER size: 1558b

For an identity certificate:

* Type (identity certificate)

* Version (of the certificate style)

* DER size, which gives the size of the certificate contents (not the size of the certificate file itself)

* Key size, for the associated key file, in bytes

For example:

[root@server ~]# rct stat-cert /etc/pki/consumer/cert.pem
Type: Identity Certificate
Version: 1.0
DER size: 1488b
Subject Key ID size: 20b

OPTIONS¶

/path/to/cert.pem

Gives the full path and filename to the PEM certificate for the given subscription, product, or system. This is required.

--no-content

Returns all of the certification information, order information, and product information, but excludes all of the Content sections, which significantly reduced the information printed to stdout. This is for an entitlement certificate only.

--no-products

Returns all of the certification information, order information, and content (repository) information, but excludes all of the Product sections, which significantly reduced the information printed to stdout. This is for an entitlement certificate only.

/path/to/cert.pem

Gives the full path and filename to the PEM certificate for the given subscription, product, or system.

OUTPUT¶

The command returns the most basic information about the certificate -- such as its directory path, its serial number and subject name, and its validity period (start and end dates) -- in the Certificate section:

* Path -- the filesystem location where the certificate is installed

* Version -- the certificate format version -- P * Serial -- the serial number for the certificate

* Start/End Date -- the validity period for the certificate

* Alt Name -- the subject alternative name, which uses the hostname of the system rather than the UUID (for identity certificates only)

The Subject DN of the certificate is in the Subject section.

For example, for the identity certificate:

[root@server ~]# rct cat-cert /etc/pki/consumer/cert.pem
+-------------------------------------------+


        Identity Certificate
+-------------------------------------------+
Certificate:


        Path: /etc/pki/consumer/cert.pem


        Version: 1.0


        Serial: 824613308750035399


        Start Date: 2012-11-09 16:20:22+00:00


        End Date: 2013-11-09 16:20:22+00:00


        Alt Name: server.example.com
Subject:


        CN: e94bc90e-44a1-4f8c-b6fc-0a3e9d6fac2b

A product certificate contains additional information in a Product section, which defines the information for the specific installed product, such as its name, product version, and any yum tags used for that product. For example:

(redacted)

The most information is contained in the entitlement certificate. Along with the Certificate and Subject, it also has a Product section that defines the product group that is covered by the subscription.

Then, it contains an Order section that details everything related to the purchase of the subscription (such as the contract number, service level, total quantity, quantities assigned to the system, and other details on the subscription).

A subscription for a product covers the version purchased and every previous version of the product. For example, when a subscription is purchased for EuroLinux 6.4, the subscription provides full access to all EL6 repositories, plus access to all EL5 repositories and then other included product content repositories, like Subscription Asset Manager. Every available content repository is listed in a Content section that contains the repository name, associated tags, its URL, and a notice on whether the yum repository is enabled by default. For example:

(redacted)

OPTIONS¶

--no-content

Excludes all of the Content Sets sections, which significantly reduces the information printed to stdout.

/path/to/consumer_export.zip

Gives the path and filename (by default, consumer_export.zip) for the manifest file on the local system. This is required.

EXAMPLES¶

The command pretty-prints all of the details about the manifest itself and the allocated subscriptions, products, and content.

(redacted)

OPTIONS¶

/path/to/consumer_export.zip

Gives the path and filename (by default, consumer_export.zip) for the manifest file on the local system. This is required.

--destination=PATH

Specifies an export directory to which to extract and save the contents of the manifest archive. If no destination is given, then the archive is extracted to the local directory.

--force, -f

Overwrites any existing archive files. If a manifest archive already exists in the specified location (for example, if the manifest has already been dumped once), then attempting to dump the manifest to the same location will fail. Using the --force option forces the dump operation to complete and overwrites the previous file.

EXAMPLES¶

This command simply extracts the manifest files to a given location (the working directory by default). The manifest itself contains multiple JSON files, with separate JSON files providing details on the manifest itself, each individual product, each individual subscription, and details for the specific, on-premise subscription management service.

For example:

[root@server ~]# rct dump-manifest --destination /export/archives/sam/manifest /tmp/consumer_export.zip
The manifest has been dumped to the /export/archives/sam/manifest directory.