Skip to main content
Skip table of contents

LDAP Publisher

Introduction

EJBCA Publishers

Slide Deck: EJBCA Publishers

Overview: This part of the lab configures an LDAP publisher. If you wish to publish to an LDAP directory or Active directory instance (separate publisher), these are the types of information that would be required to setting up the publisher.

NOTE: the lab environment does not have a running LDAP directory, but setting up this publisher is needed when configuring the Multi-group publisher which is coming up.

Slide reference

Publisher queue options - this section is common to ALL publishers

LDAP specific publisher settings

LDAP specific publisher settings

LDAP specific publisher settings

Reminder you can visit the Accessing Your Environment page for details on how to connect to your Admin web portal

LDAP Publisher Configuration

  1. Open a browser and access your Admin Web Portal on the CA instance

  2. On the CA, click CA Functions >> Publishers

  3. In the Add Publisher field, enter LDAP Publisher and click Add

  4. In List of Publishers, select LDAP Publisher and click Edit Publisher

  5. In the Publisher Type list, select LDAP V3 Publisher

  6. In the Hostnames field, enter ca.primekey.training

  7. For the Port field, select the Plaintext Connection radio button.

  8. In the Base DN field, enter o=PRIMEKEY,c=SE

  9. In the Login DN field, enter cn=ejbca,o=PRIMEKEY,c=SE

  10. In the Login Password field, enter foo123

  11. In the Confirm Password field, repeat foo123

  12. In the LDAP location fields from certificate DN selection field, select:

    1. CN, Common name

    2. O, Organization

    3. C, Country

  13. For the Publisher Queue option No direct publishing, only use queue, check the Use checkbox.

  14. Click Save and Test Connection (the connection will fail since the LDAP-server is not installed). The following error will be displayed “Following error occurred when testing connection LDAP Publisher: Error binding to LDAP server. Connect Error.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.