|
Softpanorama |
||||||
| Contents | Bulletin | Scripting in shell and Perl | Network troubleshooting | History | Humor | |
| News | Certificates management | Troubleshooting HPOM agents | Documentation | HPOM 9 Env Variables | Agents | Agent directories |
| opcnode | opcagt | opcmon | opcragt | HPOM server Directories | ||
| History | Humor | Etc |
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:
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.
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.
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.
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.
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.
On completion, the components checked and their status along with the final result are displayed.
- certificate installed
- no certificate
- pending certificate request
- certificate request denied
- undefined (if Certificate Client can not be contacted)
The following exit values are returned:
ovcert -importcert -file <file>
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 root@sp79d.dmz2.firma.com:/
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, 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.
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 : C++ Humor : ARE YOU A BBS ADDICT? : Object oriented programmers of all nations : C Humor : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : 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 : The Most Comprehensive Collection of Editor-related Humor : Microsoft plans to buy Catholic Church : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor : Best Russian Programmer Humor : Russian Musical Humor : The Perl Purity Test : Politically Incorrect Humor : GPL-related Humor : OFM Humor : IDS Humor : Real Programmers Humor : Scripting Humor : Web Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor :
Copyright © 1996-2013 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Site uses AdSense so you need to be aware of Google privacy policy. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine. This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|
|
You can use PayPal to make a contribution, supporting hosting of this site with different providers to distribute and speed up access. Currently there are two functional mirrors: softpanorama.info (the fastest) and softpanorama.net. |
Disclaimer:
The statements, views and opinions presented on this web page are those of the author and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: May 02, 2013