---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Generating an LDAP client certificate

# Generating an LDAP client certificate {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Generate an LDAP client certificate for mutual authentication using OpenSSL. The
final output is a PKCS#12 certificate stored within a Java keystore.

## Vorbereitungen

Role required: admin

## Warum und wann dieser Vorgang ausgeführt wird

See the [OpenSSL documentation](http://www.openssl.org/docs/) for more information about generating
certificates. These steps assume you have access to OpenSSL.

Enter these commands in a command line interface.

## Prozedur

1. Generate a self-signed client certificate.  
   For example, this command creates a client certificate test1-cert.crt based on the test1-key.key private key.  

       openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout test1-key.key -out test1-cert.crt

2. Convert both the certificate file and private key to PKCS#12 (a file with a .pfx or .p12 extension).  
   For example, this command converts the client certificate and private key to a PKCS#12 certificate called test1-certificate.pfx.  

       openssl pkcs12 -export -out test1-certificate.pfx -inkey test1-key.key -in test1-cert.crt

3. Generate the Java Key Store and import the pkcs12 file into it.  
   For example, this command imports the certificate to the test1.jks Java keystore.  

       keytool -importkeystore -srckeystore test1-certificate.pfx -srcstoretype PKCS12 -destkeystore test1.jks

4. [Upload the certificate](https://servicenow-prod.fluidtopics.net/l5Vgdu6SziVs2Hxvk9XltA "Add a certificate to the instance from the Certificates module.") in the keystore file (`test1.jks`) to the instance.  
   Hinweis:  
   If you are uploading to an on-premise instance using a certificate with
   the .jks extension and you receive an error saying "No valid certificate
   found to process the application upload", use a certificate with the
   .pfx extension instead.

## Nächste Maßnahme

[Uploading a certificate to an instance](https://servicenow-prod.fluidtopics.net/l5Vgdu6SziVs2Hxvk9XltA "Add a certificate to the instance from the Certificates module.")
* **[Generating a server certificate](https://servicenow-prod.fluidtopics.net/MgZ~FgJDvpzNQFP5btNtNA)**   
  You can use keytool to generate a new Java keystore file, create a certificate signing request (CSR), and import the private key, public certificate pair, and signed certificates into the keystore.

**Zugehörige Konzepte**   

* [Exploring Certificates](https://servicenow-prod.fluidtopics.net/6WXnJYGCfVdfF6_yk9APZg "Your instance requires certificates to establish secure connections and validate signatures.")  
**Zugehörige Tasks**   

* [Uploading a certificate to an instance](https://servicenow-prod.fluidtopics.net/l5Vgdu6SziVs2Hxvk9XltA "Add a certificate to the instance from the Certificates module.")