HP Integrity rx2800 System Management Homepage User Guide - Page 40

Local Server Certificate Category, Apply, Settings, Remove

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 40 highlights

6. Click Add to add the configurations. 7. Click Apply to apply the configurations. To remove IP addresses from the list: 1. Select Settings from the menu. 2. In the System Management Homepage box, click the Security link. 3. Click the IP Restricted Login link. 4. Select the check box beside the IP addresses you want to remove. 5. Click Remove. 6. Click Apply to apply the configurations. Local Server Certificate Category The Local Server Certificate link enables you to use certificates that are not generated by HP. 1 Organization (O) 4 Create 7 Alternative Names The name of the organization. Create the certificate request. Valid server name list. 2 Organizational Unit (OU). 5 PKCS #7 Information 8 Create The name of the unit within the PKCS #7 fields filled. organization requesting the certificate. 3 Alternative Name 6 Import Import the signed certificate. Re-create the certificate adding the given alternative names. If you use the following process, the self-signed certificate that was generated by the HP SMH is replaced with one issued by a certificate authority (CA). • The first step of the process is to cause the HP SMH to create a Certificate Request (PKCS #10). This request uses the original private key associated with the self-signed certificate and generates data for the certificate request. The private key never leaves the server during this process. • After the Public Key Infrastructure PKCS #10 data is created, the next step is to send it to a certificate authority. Follow your company policies for sending secure requests for and receiving secure certificates. • After the certificate authority returns the PKCS #7 data, the final step is to import this into HP SMH. • After the PKCS #7 data is imported, the original \hp\sslshare\cert.pem certificate file for Windows, /opt/hpsmh/sslshare/cert.pem file for HP-UX, and /opt/hp/sslshare/cert.pem (/etc/opt/hp/sslshare/cert.pem in HP SMH 2.1.3 and later on Linux x86 and x86-64) is overwritten with the system certificate from the PKCS #7 data envelope. The same private key is used 40 The Settings Page

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
6.
Click
Add
to add the configurations.
7.
Click
Apply
to apply the configurations.
To remove IP addresses from the list:
1.
Select
Settings
from the menu.
2.
In the
System Management Homepage
box, click the
Security
link.
3.
Click the
IP Restricted Login
link.
4.
Select the check box beside the IP addresses you want to remove.
5.
Click
Remove
.
6.
Click
Apply
to apply the configurations.
Local Server Certificate Category
The
Local Server Certificate
link enables you to use
certificates
that are not generated by HP.
7
4
1
Alternative Names
Valid server name list.
Create
Create the certificate request.
Organization (O)
The name of the organization.
2
8
5
Organizational Unit (OU)
.
The name of the unit within the
organization requesting the
certificate.
Create
Re-create the certificate adding the
given alternative names.
PKCS #7 Information
PKCS #7 fields filled.
6
Import
Import the signed certificate.
3
Alternative Name
If you use the following process, the
self-signed certificate
that was generated by the HP SMH is replaced
with one issued by a
certificate authority
(CA).
•
The first step of the process is to cause the HP SMH to create a
Certificate Request (PKCS #10)
. This
request uses the original private key associated with the self-signed certificate and generates data for
the certificate request. The private key never leaves the server during this process.
•
After the Public Key Infrastructure
PKCS #10
data is created, the next step is to send it to a certificate
authority. Follow your company policies for sending secure requests for and receiving secure certificates.
•
After the certificate authority returns the
PKCS #7
data, the final step is to import this into HP SMH.
•
After the
PKCS #7
data is imported, the original
\hp\sslshare\cert.pem
certificate file for Windows,
/opt/hpsmh/sslshare/cert.pem
file for HP-UX, and
/opt/hp/sslshare/cert.pem
(
/etc/opt/hp/sslshare/cert.pem
in HP SMH 2.1.3 and later on Linux x86 and x86-64) is
overwritten with the system certificate from the
PKCS #7
data envelope. The same private key is used
40
The Settings Page