Establishing secure connection

Before your application can communicate with the SingleView B2B API Suite, a secure communication channel must be established using mutual TLS (mTLS). This process ensures that both the client application and the SingleView platform authenticate each other, providing a trusted and encrypted connection for all API requests.

As part of the onboarding process, the SingleView technical team validates your certificates and assists with the certificate exchange required to establish secure connectivity.

Certificate Validation

To ensure compatibility with the platform, the SingleView technical team performs a comprehensive review of the certificates provided by your organization.

The validation process includes:

• Confirming that the certificate uses the RSA algorithm.
• Verifying the key size:
• • 4096-bit RSA (recommended)
  • 2048-bit RSA (supported)
• Validating that the certificate is provided in .p12 or .pfx format and contains:
• • A valid RSA private key
  • A corresponding certificate
• Determining whether the certificate is CA-signed or self-signed.
• Reviewing the certificate bundle to identify the certificate that will be used for request signing.

Security Assessment

Before enabling connectivity, the technical team performs a security assessment to ensure the client environment supports the platform's security requirements.

This assessment includes:

• Verifying support for mutual TLS (mTLS) using the client's Certificate Signing Request (CSR) and the CA-signed certificate.
• Confirming which client certificate will be configured and used for authentication and request signing.
• Ensuring that the certificate configuration aligns with the platform's security standards.

Certificate Exchange Process

Follow the steps below to establish a secure connection with the SingleView platform.

Step 1: Submit Your Certificate Signing Request (CSR)

Generate a Certificate Signing Request (CSR) from your environment and send it to the SingleView technical team via email.

The CSR should be sent to info@onesingleview.com

The CSR is used to generate a client certificate that will be trusted by the SingleView platform.

Step 2: Receive Your Signed Certificate

Upon receiving your CSR, the SingleView technical team signs the certificate using the SingleView Root Certificate Authority (CA).

The signed certificate is then securely shared with your organization for implementation.

Step 3: Configure Mutual TLS

Install the signed client certificate alongside the corresponding private key in your application or gateway.

During the TLS handshake:

• Your application presents the signed client certificate.
• The private key is used to prove certificate ownership.
• The SingleView platform validates the certificate before accepting the connection.

Once mutual authentication is successful, a secure TLS session is established, allowing your application to communicate with the SingleView APIs.