• Skip to primary navigation
  • Skip to main content
  • Skip to footer

Company · Blog · Newsletter · Events · Partner Program

Downloads Support
  • English
    • Deutsch
    • Polski
Login
Rublon

Rublon

Secure Remote Access

  • Product
    • Regulatory Compliance
    • Use Cases
    • Rublon MFA Reviews
    • Deployment Model
    • What is MFA?
    • Authentication Methods
    • Rublon Authenticator
    • Rublon App Shield
    • Rublon Identity Bridge
    • Rublon Endpoint Shield
    • Remembered Devices
    • Logs
    • Single Sign-On
    • Access Policies
    • Directory Sync
  • Solutions
    • MFA for Remote Desktop
    • MFA for Remote Access Software
    • MFA for Windows Logon
    • MFA for Linux
    • MFA for macOS
    • MFA for On-Premise Active Directory
    • MFA for LDAP
    • MFA for RADIUS
    • MFA for SAML
    • MFA for RemoteApp
    • MFA for Workgroup Accounts
    • MFA for Entra ID
    • MFA for Windows Server Core
  • Customers
  • Industries
    • Financial Services
    • Investment Funds
    • Retail
    • E-Commerce
    • Technology
    • Healthcare
    • Legal
    • Education
    • Government
    • Utilities
    • Manufacturing
  • Pricing
  • Docs
Contact us Free Trial

Configuring LDAPS on Rublon Authentication Proxy With Its Own Certificate

Rublon Authentication Proxy: LDAPS Without Exporting the Domain Controller’s Private Key

November 16, 2026 By Rublon Authors

When you use Rublon Authentication Proxy to add multi-factor authentication (MFA) to applications that authenticate against Active Directory over LDAPS, you need to configure certificates for the encrypted connections. If the domain controller already has an LDAPS certificate, it may seem that its certificate and private key must also be copied to the proxy. This creates an issue if the key is non-exportable or your organization does not allow it to leave the domain controller.

Rublon Authentication Proxy can use its own certificate and private key instead. This guide shows how to create that pair on the Rublon Auth Proxy server and configure certificate trust on both sides of the proxy. Applications can then use LDAPS with Rublon MFA while the domain controller’s private key stays on the domain controller.

How the Certificate Setup Works

The Rublon Authentication Proxy in LDAPS mode needs a certificate and private key. That pair identifies the proxy server, not the domain controller. The Active Directory private key stays on the domain controller and is not copied to the Auth Proxy machine.

There are two independent TLS connections:

  1. An application connects to the Rublon Authentication Proxy. The Auth Proxy presents its certificate and signs the handshake with its private key.
  2. The Rublon Authentication Proxy connects to the domain controller. The Auth Proxy checks the domain controller certificate using the public CA certificate. It does not use the domain controller’s private key.

The name in the Rublon Authentication Proxy certificate must be the name applications use to reach the proxy (for example, rap.company.local). The domain controller name belongs on the LDAPS certificate of the domain controller.

Note

This guide applies to Rublon Authentication Proxy 3.12.0 or later on Windows, which includes the Rublon Windows Certificate Export Helper.

What Not to Copy From the Domain Controller

Do not export these from the domain controller:

  • the private key of the LDAPS certificate,
  • the PFX file of that certificate,
  • the domain controller certificate as the proxy cert_path.

The only file needed from the domain controller side is the public certificate of the authority that signed the domain controller LDAPS certificate. If the domain controller certificate is trusted directly, copy only that public certificate, without the key.

1. Issue a Certificate on the Auth Proxy Server

The private key must be created on the machine where the Rublon Authentication Proxy runs. Both options below require a currently valid certificate, the Server Authentication EKU (OID 1.3.6.1.5.5.7.3.1), and a SAN that contains the DNS name used by LDAP clients.

Option 1: Request From an Internal CA (Preferred)

The key stays in the local computer store. Only a CSR is sent to the CA.

1. Save rap-ldaps.inf in $env:TEMP on the Rublon Auth Proxy server. Replace rap.company.local with the proxy DNS name:

[Version]
Signature = "$Windows NT$"

[NewRequest]
Subject = "CN=rap.company.local"
KeyAlgorithm = RSA
KeyLength = 2048
HashAlgorithm = SHA256
Exportable = TRUE
MachineKeySet = TRUE
ProviderName = "Microsoft Software Key Storage Provider"
RequestType = PKCS10

[Extensions]
2.5.29.17 = "{text}dns=rap.company.local"
2.5.29.37 = "{text}1.3.6.1.5.5.7.3.1"

Note

Exportable = TRUE is required. The Rublon Authentication Proxy loads the key into OpenSSL from a PEM file and cannot use a non-exportable key from the Windows certificate store.

2. In an elevated PowerShell session, run the following.

For an AD CS enterprise CA, add -attrib “CertificateTemplate:YOUR_TEMPLATE_NAME” to certreq -submit. Use the template name provided by your CA administrator, with Server Authentication, the proxy DNS name in the SAN, and private-key export allowed.

cd $env:TEMP
certreq -new .\rap-ldaps.inf .\rap-ldaps.req
certreq -submit .\rap-ldaps.req .\rap-ldaps.cer
certreq -accept .\rap-ldaps.cer

3. certreq -submit prints a request ID. If the CA requires manual approval, approve the request at the CA and then retrieve the certificate.

certreq -retrieve <RequestID> .\rap-ldaps.cer
certreq -accept .\rap-ldaps.cer

The certificate appears in Cert:\LocalMachine\My.

Option 2: a Self-Signed Certificate

Use this only when LDAP clients can receive this certificate into their trust store. Applications will not trust it on their own.

New-SelfSignedCertificate `
  -DnsName "rap.company.local" `
  -CertStoreLocation "Cert:\LocalMachine\My" `
  -KeyAlgorithm RSA `
  -KeyLength 2048 `
  -HashAlgorithm SHA256 `
  -KeyExportPolicy Exportable `
  -NotAfter (Get-Date).AddYears(2) `
  -TextExtension @("2.5.29.37={text}1.3.6.1.5.5.7.3.1")

2. Write the Certificate and Key as PEM

The next step is exporting the certificate located in Cert:\LocalMachine\My to PEM with the Rublon Windows Certificate Export Helper.

1. On the Rublon Authentication Proxy server, run the following in an elevated PowerShell session:

cd "C:\Program Files\Rublon Auth Proxy"
.\bin\rublon-certificate-export

2. Select the certificate issued on the Rublon Authentication Proxy server and enter the DNS name that clients use (in our example, rap.company.local). The Rublon Windows Certificate Export Helper tool rejects a CA certificate, a certificate without a private key, and a certificate that does not match the given name.

3. When prompted, set and confirm a password for the exported private key.

By default, Rublon Windows Certificate Export Helper writes:

  • config\certificates\ldap-proxy-certificate.pem
  • config\certificates\ldap-proxy-private-key.pem

Keep the private-key password you set in the Rublon Windows Certificate Export Helper. You will need it when configuring pkey_password in the Set config.yaml section below. The tool does not display this password.

To export an unencrypted private key instead, run the tool with --unencrypted-private-key and omit pkey_password from the configuration.

4. Grant the account running the RublonAuthProxy service read access to both generated files. Restrict the key directory to that account and to administrators.

3. Trust the Domain Controller Certificate

1. Copy the public CA certificate (or the public domain controller certificate, when that certificate is trusted directly) into:

C:\Program Files\Rublon Auth Proxy\config\ca_certs

The file must be PEM and use a .pem, .crt, or .cer extension. The Rublon Authentication Proxy skips files with any other extension. The PEM file must contain a -----BEGIN CERTIFICATE----- block.

2. On the certification authority server, save the public CA certificate without a key:

New-Item -ItemType Directory -Path C:\Temp -Force | Out-Null
certutil -ca.cert C:\Temp\domain-ca.cer
certutil -encode C:\Temp\domain-ca.cer C:\Temp\domain-ca.pem

The second certutil command converts the exported DER certificate to PEM. Copy domain-ca.pem to the Rublon Authentication Proxy’s CA certificate directory.

When the CA is not the domain controller, export that same CA certificate from Trusted Root Certification Authorities or from the chain of the domain controller LDAPS certificate, using Base-64 encoded X.509 format. Copy only the public file to the Rublon Authentication Proxy server.

4. Set config.yaml

transport_type on the LDAP source sets encryption in both directions: the Rublon Authentication Proxy listener and the Rublon Authentication Proxy connection to Active Directory. For LDAPS, set ssl. The port under proxy_servers is the port applications connect to. The port under auth_sources is the domain controller port.

Update the following sections in your existing config\config.yaml file. Keep the rublon section containing your System Token and Secret Key.

proxy_servers:
  - name: LDAP-Proxy
    type: LDAP
    ip: 0.0.0.0
    port: 636
    auth_source: LDAP_SOURCE_1
    auth_method: email
    cert_path: 'C:\Program Files\Rublon Auth Proxy\config\certificates\ldap-proxy-certificate.pem'
    pkey_path: 'C:\Program Files\Rublon Auth Proxy\config\certificates\ldap-proxy-private-key.pem'
    pkey_password: 'proxy_key_password'

auth_sources:
  - name: LDAP_SOURCE_1
    type: LDAP
    ip: dc01.company.local
    port: 636
    transport_type: ssl
    tls_verify_hostname: dc01.company.local
    ca_certs_dir_path: 'C:\Program Files\Rublon Auth Proxy\config\ca_certs'
    search_dn: 'DC=company,DC=local'
    access_user_dn: 'CN=svc-rap,OU=Service Accounts,DC=company,DC=local'
    access_user_password: 'service_account_password'

pkey_password is a secret. With global.secret_source: plain it is stored in the file in clear text. With another secret_source, supply it in the form that source requires.

Do not set client_cert_path or client_pkey_path. Those fields are for certificate authentication of the Rublon Authentication Proxy as a client to AD. They do not replace the proxy server certificate. Ordinary LDAPS does not need them.

For STARTTLS, when applications stay on port 389 and upgrade to TLS afterwards:

  • set port: 389 on the proxy,
  • set port: 389 and transport_type: starttls on the source,
  • cert_path and pkey_path are still required, as they are for ssl.

Every LDAP source attached to one proxy must use the same transport_type.

5. Trust on the Application Side

The application connects to rap.company.local:636, not to the domain controller. It must trust the CA that signed the Rublon Authentication Proxy certificate. With a certificate from the organization CA, that trust is usually already present. With a self-signed certificate, install the public ldap-proxy-certificate.pem on the client.

The name that the application uses must be in the SAN of the Rublon Authentication Proxy certificate. A connection by IP address requires that address in the SAN as IP:.

6. Restart and Check

1. Restart the Rublon Authentication Proxy service:

net stop RublonAuthProxy
net start RublonAuthProxy

2. Check the log file in the logs directory. The first message below confirms that the LDAPS listener has started. The remaining entries describe errors or warnings and their possible causes:

  • Started listening on …:636 — the proxy LDAPS listener is up,
  • Failed to load the private key — wrong path, PEM format, or wrong pkey_password,
  • cert_path and pkey_path are both needed — one of the paths is missing for ssl or starttls,
  • Invalid SSL configuration — the certificate and the key are not a pair,
  • a warning about the CA directory — the Rublon Authentication Proxy did not find a public certificate with which to check the domain controller.

3. Check the domain controller from the Rublon Authentication Proxy server without using its private key. When OpenSSL is installed, this command shows the domain controller LDAPS certificate:

openssl s_client -connect dc01.company.local:636 -servername dc01.company.local -CAfile "C:\Program Files\Rublon Auth Proxy\config\ca_certs\domain-ca.pem"

Verify return code: 0 means the public CA stored for Rublon Authentication Proxy matches the domain controller certificate.

Related Posts

Rublon Authentication Proxy – Documentation

Configuring the Rublon Authentication Proxy as an LDAP Proxy Server

Exporting a Windows Certificate for Rublon Authentication Proxy

How to set up LDAPS certificates in the Rublon Authentication Proxy?

Filed Under: Blog

Try Rublon MFA for Free
Start your 30-day Rublon MFA Trial to secure your employees using multi-factor authentication.
No Credit Card Required
Rublon 5 star reviews on Gartner Peer Insights

Footer

Product

  • Regulatory Compliance
  • Rublon MFA Reviews
  • Use Cases
  • Deployment Model
  • What is MFA?
  • User Experience
  • Authentication Methods
  • Rublon Authenticator
  • Rublon App Shield
  • Rublon Identity Bridge
  • Rublon Endpoint Shield
  • Remembered Devices
  • Logs
  • Single Sign-On
  • Access Policies
  • Directory Sync

Solutions

  • MFA for Remote Desktop
  • MFA for Windows Logon
  • MFA for Remote Access Software
  • MFA for Linux
  • MFA for macOS
  • MFA for On-Premise Active Directory
  • MFA for LDAP
  • MFA for RADIUS
  • MFA for SAML
  • MFA for RemoteApp
  • MFA for Workgroup Accounts
  • MFA for Entra ID
  • MFA for Windows Server Core

Secure Your Entire Infrastructure With Ease!

Experience Rublon MFA
Free for 30 Days!

Free Trial
No Credit Card Required

Need Assistance?

Ready to Buy?

We're Here to Help!

Contact

Industries

  • Financial Services
  • Investment Funds
  • Retail
  • E-Commerce
  • Technology
  • Healthcare
  • Legal
  • Education
  • Government
  • Utilities
  • Manufacturing

Documentation

  • 2FA for Windows & RDP
  • 2FA for RDS
  • 2FA for RD Gateway
  • 2FA for RD Web Access
  • 2FA for SSH
  • 2FA for macOS
  • 2FA for OpenVPN
  • 2FA for SonicWall VPN
  • 2FA for Cisco VPN
  • 2FA for Office 365

Support

  • Knowledge Base
  • FAQ
  • System Status

About

  • About Us
  • AI Info
  • Blog
  • Events
  • Careers
  • Co-funded by the European Union
  • Contact Us

  • Facebook
  • GitHub
  • LinkedIn
  • Twitter
  • YouTube

© 2026 Rublon · Imprint · Legal & Privacy · Security