You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 13
Next »
The Public Key Infrastructure (PKI) provides a common set of infrastructure features supporting public key and certificate-based authentication based on the RSA public/private key pairs and X.509 digital certificates.Certificate Types
Local-Internal Certificates
In previous
Unable to show "metadata-from": No such page "_space_variables"
versions, the RSA key pairs and Certificate Signing Request (CSR) for Unable to show "metadata-from": No such page "_space_variables"
platforms were generated on an external workstation. The CSR was then submitted to a Certificate Authority, and the resulting certificate was received back from the CA, copied onto the workstation, and combined with the private key in a PKCS#12 file which was used to install the key pair and certificate onto the Unable to show "metadata-from": No such page "_space_variables"
.The
Unable to show "metadata-from": No such page "_space_variables"
application can now generate and install RSA key pairs and generate Certificate Signing Request (CSR) on the Unable to show "metadata-from": No such page "_space_variables"
system itself. The certificate request is sent to a CA, and the issued certificate is then installed on the Unable to show "metadata-from": No such page "_space_variables"
. The local-internal certificate option simplifies the certificates and keys managing process and also provides more security since the private key never leaves the Unable to show "metadata-from": No such page "_space_variables"
. For steps to configure local-internal certificates, see Generating PKI Certificates.
Certificate file format: PEM
Local Certificates
Local certificates are credentials belonging to the local system itself, which it presents to peers in order to prove its identity. You must download local certificate files to the system before installing the certificates.
Certificate file format: PKCS#12
Remote Certificates
Remote certificates are credentials belonging to Certificate Authorities (CA). The copies of these certificates are installed in the
Unable to show "metadata-from": No such page "_space_variables"
because they are part of a chain of certificates the local system will present to peers, or because the corresponding CAs are trust anchors for the local system. Certificates belonging to non-CA remote systems should also be installed as trust anchors in this manner.The Certificate Authority (CA) certificates and trusted remote certificates contain public key certificates; they do not contain the private keys. The CA certificates and remote certificates are Distinguished Encoding Rules (DER) format files; a method for encoding a data object (such as an X.509 certificate) which uses a digital signature to bind together a public key with an identity.
Certificate file format: DER
Command Syntax
Set Command Syntax
% set system security pki certificate <certificate name>
fileName <1-255 characters>
passPhrase <pass phrase>
state <disabled | enabled>
type <local | local-internal | remote>
% show system security pki
% delete system security pki
Request Command Syntax
% request system security
eventLogValidation
deleteUserPrivateKey
generateDefaultKeys
setUserPrivateKey <uniqueUserPrivateKeyName> <userPrivateKey>
showPublicKey <default/user>
generateSipHeaderEncryptionKeys
pki
certificate <certificate name>
generateCSR
csrSub (max 255 chars)
keySize (ketSize1K | keySize2K)
subjectAlternativeDnsName (0-512 chars)
importCert certContent (max 4096 chars)
retrieveCertContent
uploadCertificate
Command Parameters
Set Parameters
set system security Parameters
Parameter | Description |
---|
certificate
| <certificate name> – The collection of certificates configured on the SBC.
|
fileName
| <filename > – Certificate content filename in the format: - Local-Internal: PEM
- Local: PKCS#12
- Remote: DER
|
passPhrase
| Specifies the pass-phrase to decrypt RSA private key in PKCS#12 file. Note: The passPhrase is limited to 23 characters. |
state
| Administration state of this certificate. Options are: disabled – Prohibits the PKI certificate from being used by the Unable to show "metadata-from": No such page "_space_variables" for authenticating remote peers (when this is a remote certificate) OR presenting its own identity (in case of a local or local-internal certificate).enabled – Certificate can be used by Unable to show "metadata-from": No such page "_space_variables" for authentication purposes.
The certificate must first be installed on the Unable to show "metadata-from": No such page "_space_variables" before enabling it.
|
type
| Specifies the certificate type – CA (remote) certificate or local certificate. Options are: local – Certificate belongs to (has as its subject) the local system itself; the key pair and CSR were generated elsewhere.local-internal – Certificate belongs to (has as its subject) the local system itself; the key pair and CSR were generated on this machine.remote – Certificate belongs to (has as its subject) a remote entity such as a CA or peer device.
|
Request Parameters
request system security Parameters
Parameter | Description |
---|
eventLogValidation | deleteUserPrivateKey – Delete an existing user-submitted private key. When the key is removed the SBC will revert back to using its default private key. generateDefaultKeys – Requests the generation of a new default SBC-generated private key pair. setUserPrivateKey <uniqueUserPrivateKeyName> <userPrivateKey> – Configures the user-submitted private key. The private key is encrypted in CDB using existing CDB encryption methods. The user-submitted private key is only available internally. The key is encrypted and hidden, thus not displayable, once configured in CDB. showPublicKey <user/default> – Access the public key associated with the chosen private key. |
generateSipHeaderEncryptionKeys
| Use this command to generate header encryption keys. A "Success" or "Failure" indication is returned. The SBC then adds the key-Id to each encrypted header based on which key is selected as the correct key for decryption. The SBC stores up to two sets of keys at any given time. There is no limit to the number of times this command may be executed. Additionally, there is no specific time delay required before reissuing the command. NOTE: Generating new keys too frequently may lead to a situation where the SBC receives a request with an expired key-id (i.e. the current header encryption key is over-written due to the new key generation) causing unsuccessful decryption of headers. This may lead to call failures any calls caught in the transition to the new key-id. |
pki | PKI certification configuration details. certificate <certificateName> – The name for a collection of certificates configured on SBC.generateCSR – Use this parameter to generate CSR (Certificate Signing Request).csrSub – CSR subject name (max 255 chars). Place the parameter value within quotation marks if a string contains a space.
keySize – Size of the key to generate private key via openssl command.
subjectAlternativeDnsName – Alternative DNS subject name(s). Multiple alternative names can be specified using "," (comma) separator. (0-512 chars). Example: "nj.example.com, in.example.com, uk.example.com, ca.example.com, tx.example.com"
importCert certContent – Import PEM format certificate (max 4096 characters). Note: When issuing this command, the SBC enables multi-line mode automatically. To exit multi-line mode you must press Ctrl+D manually.retrieveCertContent – Retrieve content of an existing PKI certificate (local, local-internal and remote).
uploadCertificate – Upload a pk12 certificate.
|
Command Example
To display security management configuration:
% show system security pki certificate
certificate testSBCCert {
state enabled;
fileName sonuscert.pem
type local-internal;
}
certificate defaultSBCCert {
state enabled;
fileName sonuscert.p12;
passPhrase $3$KFfiuJ0Lifk=;
type local;
}