ovcert - Command to check, request, or modify the certificate on the managed node

The ovcert command is used to manage certificates with the Certificate Client on an HTTPS-based node. You can execute tasks such as initiating a new certificate request to the Certificate Server, adding node certificates and importing the private keys, and adding certificates to the trusted root certificates.

ovcert -h|-help

Output of OVCERT help

Usage: ovcert -importcert -file [-pass ]
[-ovrg ]
ovcert -exportcert -file [-alias ] [-pass ]
[-ovrg ]
ovcert -importtrusted -file [-ovrg ]
ovcert -exporttrusted -file [-alias ]
[-ovrg ]
ovcert -certreq [-instkey [-pass ]]
ovcert -list [-ovrg ]
ovcert -remove [-f] [-ovrg ]
ovcert -certinfo [-ovrg ]
ovcert -check [-ovrg ]
ovcert -status
ovcert -updatetrusted
ovcert -version
ovcert [-h|-help]
Example usage (checking the status of the certificate):
ovcert -status
Status: Certificate is installed. 

ovcert -importcert -file <file> [-pass <passphrase>] [-ovrg <ov_resource_group>]

ovcert -exportcert -file <file> [-alias <alias>] [-pass <passphrase>] [-ovrg <ov_resource_group>]

ovcert -importtrusted -file <file> [-ovrg <ov_resource_group>]

ovcert -exporttrusted -file <file> [-alias <alias>] [-ovrg <ov_resource_group>]

ovcert -certreq [-instkey <file> [-pass <passphrase>]]

ovcert -list [-ovrg <ov_resource_group>]

ovcert -remove <alias> [-f] [-ovrg <ov_resource_group>]

ovcert -certinfo <alias> [-ovrg <ov_resource_group>]

ovcert -check

ovcert -status

ovcert -updatetrusted

ovcert -version

Parameters

The ovcert command incorporates the following options:

-h|-help

Displays usage help for the ovcert command options.

 

-importcert -file <file> [-pass <passphrase>] [-ovrg <ov_resource_group>]

Adds the certificate located in the file <file> (in PKCS12 format) as node certificate and imports the private key which must be located in the same file as the private key for the node. The pass phrase for protecting the exported data using encryption specified during creation of the data to import must be specified as parameter <passphrase>.

The optional <ov_resource_group> parameter can be specified to import an additional certificate on an HA system. As a result, the specified certificate will not be imported to the default location but to the HA default location for the specified package on the shared disk.

 

-exportcert -file <file> [-alias <alias>] [-pass <passphrase>] [-ovrg <ov_resource_group>]

Exports the currently installed node certificate together with its private key to the file system location specified as parameter <file> (in PKCS12 format). The pass phrase for protecting the exported data using encryption specified during creation of the data to import must be specified as parameter <passphrase>.

The optional <ov_resource_group> parameter can be specified to export an additional certificate on an HA system. As a result, not the default node certificate but the certificate installed for the specified HA package from the shared disk will be exported.

 

-importtrusted -file <file> [-ovrg <ov_resource_group>]

Adds the certificate located in the specified file (in PEM format) to the trusted root certificates.

The optional <ov_resource_group> parameter can be specified to import an additional root certificate on an HA system. As a result, the specified root certificates will not be imported to the default location but to the HA default location for the specified package on the shared disk.

 

-exporttrusted -file <file> [-alias <alias>] [-ovrg <ov_resource_group>

Exports the trusted certificate to the file system location specified as parameter <file> (in PEM format). The pass phrase for protecting the exported data using encryption specified during creation of the data to import must be specified as parameter <passphrase>.

The optional <ov_resource_group> parameter can be specified to export an additional certificate on an HA system. As a result, not the default node certificate but the certificate installed for the specified HA package from the shared disk will be exported.

 

-certreq [-instkey <file> [-pass <passphrase>]]

Initiates a new certificate request that is sent to the Certificate Server.

The optional parameters <file> and <passphrase> can be used to initiate a certificate request that will be based on the installation key that is contained in the specified file. Such an installation key file can be generated with the ovcm tool on the certificate server.

The installation key can be used to authenticate the node on the certificate server. Therefore, such a request may be granted automatically without human interaction.

 

-list [-ovrg <ov_resource_group>]

Displays the aliases of the installed certificates andtrusted certificates.

 

-certinfo <alias> [-ovrg <ov_resource_group>]

Displays information such as serial number, issuer, subject, and fingerprint for the certificate specified by <alias>.

 

-remove <alias> [-ovrg <ov_resource_group>]

Removes the certificate specified by <alias>.

 

-check

Checks whether all prerequisites for SSL communication are fulfilled, such as assigned OvCoreId, installed and valid certificate and private key, and installed and valid trusted certificate.

On completion, the components checked and their status along with the final result are displayed.

 

-status

Contacts the Certificate Client and displays the current certificate status, which can one of the following possible values:

- certificate installed

- no certificate

- pending certificate request

- certificate request denied

- undefined (if Certificate Client can not be contacted)

 

-updatetrusted

Retrieves the currently trusted certificates from the Certificate Server and installs them as trusted certificates on the node.

 

-version

Returns the version of the tool (the component version).

The following exit values are returned:

• 0 All steps were successful.
• 1 One or more steps were not successful.

Examples

To import the certificate, private key, and trusted certificates located in the file <file> to the system's key store:

ovcert -importcert -file <file>

To add the certificate(s) located in <file> to the trusted certificates:

ovcert -importtrusted -file <file>

To create a certificate file on the server

opccsacm -issue -name sp79d.dmz2.firma.com -file /tmp/sp79d.cert -pass xyz1234

To copy it to the node:

scp /tmp/sp79d.cert [email protected]:/

To import certificate from a file on the node

export PATH=$PATH:/opt/OV/bin
/opt/OV/bin/ovcert -importcert -file sp79d.cert -pass xyz1234
 

   opcnode -list_id node_name=sp79d.dmz2.firma.com
   opcnode -chg_id node_name=sp79d.dmz2.firma.com id=8e475c38-8fb4-754b-0680-946436ccb281
to check
   opcnode -list_id node_name=sp79d.dmz2.firma.com

Create certificate

  opcragt -status sp79d.dmz2.firma.com

Restore certificate

ovcert -importcert -file /sp78d.cert -pass xyz1234

See also Undefined certificate state

To install the certificates manually

To install the certificates manually, follow these steps:

a. Set the installation type to MANUAL by entering the following command:

$ ovconfchg -ns sec.cm.client -set "CERTIFICATE_DEPLOYMENT_TYPE" "MANUAL"

b. Check if ovcoreid is set by entering the following command:

$ ovcoreid -show

If ovcoreid is not set, the following message will be displayed:

INFO: No OvCoreId is set.

c. If ovcoreid is not set, create the ovcoreid by entering the following

command:

$ ovcoreid -create

An error message "ERROR: No input stream" will be displayed that can be ignored.

d. To check whether the settings are correct, run ovconfget command

For example,

[sec.cm.client]

CERTIFICATE_DEPLOYMENT_TYPE=MANUAL

[sec.core]

CORE_ID=fc200278-8f86-751f-0e73-cbd79be7b384

[sec.core.auth]

MANAGER=my.mgmt.srvr.com

MANAGER_ID=970qedsd-4212-7564-1234-qwn6kuu2d07

e. Log in to the Operations Manager Server on UNIX as a root user and

add the "coreid" of  Unix managed node manually to the Operations

Manager Server by entering the following command:

#/opt/OV/bin/OpC/utils/opcnode -chg_id node_name=node id=coreid_of_the_node

For example,

#/opt/OV/bin/OpC/utils/opcnode -chg_id node_name=

test.in.hp.com id= fc200278-8f899-701f-0e73-cbd79be7b384

f. Create a signed certificate and the corresponding private key for a specific managed node manually using the opccsacm command line tool. You must provide a password to encrypt the created data.

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019