Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c86ca23f8a016cd6ed6fe90013, userName='null'}
JIRAIDAUTHTP-548
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c86ca23f8a016cd6ed6fe90013, userName='null'}

The certificate list shows all certificates available on the system. The following certificate types are supported:

  • HTTPS—Self-signed or generated by Certificate Authority (CA). Used for secure connections.
  • CA Certificate—Used to sign other certificates.
  • VoIP Traversal Server—Used by a VoIP Traversal server.
  • VoIP Traversal Client—Used by a VoIP Traversal client.
Info
titleNote

Refer to Configuring VoIP Settings for more information about VoIP Traversal.

A certificate entry can be a standard certificate or a Certificate Signing Request (CSR). CSRs cannot be used for normal operation and can only be downloaded for CA signing. Once the CA has signed the CSR, the resulting certificate can be added to the system and used.

For each entry, the certificate (or certificate signing request) as well as the corresponding key can be downloaded. If no key is available for a given certificate, the key download field is empty. Refer to Download a Certificate or key File.