Publishing certificates with multiple OU values
Originally Published: 2003-01-07
Last Modified: 2023-10-06
Article Number
Applies To
Sun Solaris 2.8
Microsoft Windows 2000
Issue
confirmEntry: unable to locate or add entry [CN=John Doe, OU=IT Dept, OU=Security, OU=Acme Class3 CA, O=Acme Inc., dc=cert,dc=acme, dc=com]
Cause
dc=cert,dc=acme, dc=com
O=Acme Inc.
OU=Acme Class3 CA
The external publishing of Keon Certificate Authority has been configured as follows:
Base DN: dc=cert,dc=acme, dc=com
Certificate DN: CN,OU,O
A bug in version 6.0.2 allowed certificates with multiple OU values to be published to this point; the bug has now been corrected in KCA 6.5, and the same publishing scheme will value the given error.
Resolution
Base DN: OU=Acme Class3 CA,O=Acme Inc.,dc=cert,dc=acme, dc=com
Certificate DN: CN
This will now mean that only the CN value is used from the certificate and will publish to the OU=Acme Class3 CA part of your tree.
Workaround
Related Articles
How to publish CA certificate and user certificate under the same OU ? Number of Views Articulate Reach 360 - SAML Relying Party Configuration - RSA Ready Implementation Guide Number of Views Leaver Rule–Deprovision is not moving Disabled Accounts to the Disabled OU in RSA Governance & Lifecycle Number of Views Articulate Reach 360 - RSA Ready Implementation Guide Number of Views Articulate Reach 360 - SCIM Client Configuration - RSA Ready Implementation Guide Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x
Don't see what you're looking for?
