Powered by

# Certificates & public keys

# Introduction

In cryptography, a public key certificate, also known as a digital certificate or identity certificate, is an electronic document used to prove the validity of a public key.

The certificate includes information about the key, information about the identity of its owner (called the subject), and the digital signature of an entity that has verified the certificate's contents (called the issuer).

If the signature is valid, and the software examining the certificate trusts the issuer, then it can use that key to communicate securely with the certificate's subject.

For more information, see Wikipedia's articles on X.509 and Public key certificates.

To be notified of any future updates to any of our certificates and/or keys, please sign up for automated notifications via our Platform updates page.

Platform updates
../../platform-updates/

# AS2 certificates

In AS2 transactions there are always two certificates involved for data signing and encryption; your trading partner certificate and your own system certificate.

The certificates involved depend on the direction of the communication (inbound or outbound) as well as the certificate activity (signing and/or encryption).

Download our trading partner certificates below.

# Pagero Online AS2 service

# Pagero Health Services AS2 service

# AS2Prod.pagerohealth.com

# AS2Prod.hbsolutions.de

# AS2Test.hbsolutions.de

# HTTP client certificates

In outbound HTTPS setups, where we are the client, we support mutual authentication in addition to basic authentication.

Mutual authentication or two-way authentication (not to be confused with two-factor authentication) refers to two parties authenticating each other at the same time in an authentication protocol. It is the default mode of authentication in some protocols (e.g. SSH) and optional in others (e.g. TLS).

Download our HTTP client certificates below.

# Pagero Online HTTP client certificate

  • Download: Pagero HTTP client certificate Current
  • Valid from: 2024-04-12
  • Valid to: 2025-05-14 1
  • Fingerprint MD5: 26:5F:F6:C6:59:5D:B5:21:89:1F:82:41:88:39:BC:4D
  • Fingerprint SHA1: 56:A3:DD:19:53:C1:30:E7:BD:F0:03:B2:A2:4C:19:6F:50:0C:8B:29

# OFTP2 certificates

In OFTP2 transactions there are always two certificates involved for data signing and encryption; your trading partner certificate and your own system certificate.

The certificates involved depend on the direction of the communication (inbound or outbound) as well as the certificate activity (signing and/or encryption).

Download our trading partner certificate below.

# Pagero Health Services Odette OFTP2 certificate

# SFTP public keys

SFTP public keys are used as an alternative authentication method for establishing secure connections.

Instead of authenticating with a password, the public key authentication method uses a pair of keys, one private and one public.

The private key is kept secret and is typically stored in the user’s home directory for safekeeping. As proof of owning the private key, the user reveals only their public key when making an SFTP connection.

Download our SFTP public keys in SSH2- and OpenSSH-format below.

# Pagero Online SFTP public key 2048 bit

# Pagero Online SFTP public key 4096 bit

  1. TLS/SSL certificate validity periods for certificates issued by certification authorities (CA's) are currently 398 days, or about 13 months. They were recently reduced by the CA/B Forum starting Sept. 1, 2020 in response to Apple’s announcement stating they would not accept certificates for two-year validity periods. Note: This does not necessarily affect self-signed trading partner certificates often used in AS2 setups though.↩↩

© Copyright 2024 Pagero. All rights reserved.