A number of the vettor certificates for the RA seem to have disappeared since upgraded the CA.
Originally Published: 2008-06-12
Article Number
Applies To
Keon Registration Authority 6.5.1
Sun Solaris 2.8
Issue
A number of the vettor certificates for the RA no longer appearing after the target CA was upgraded
admin-type field is "vettor1; .NET CLR 1.1.4322)" instead of "vettor"
Cause
Resolution
On the target CA perform these steps :
1) Create an LDIF file of the database using the re-index process from the documentation.
2) Edit the LDIF file and do a search/replace on the bad values for admin-type from "vettor1; NET CLR 1.1.43222)" to "vettor".
3) Finish the re-index procedure.
4) Synchronize your KRA with the target KCA.
All vettors will now be present.
Workaround
Related Articles
The replication connection from local site [] to [] is abnormal since the last change was sent 5Number of Views Adaptiveauthentication- Db2 deadlocks can stop responding due to large number of records sin RSASESSION RSATRANSACTIOn an… 49Number of Views How to do automatic vetting of certificate requests for Sentry RA 7Number of Views RSA Governance & Lifecycle Recipes: Chart - AD Days Since Last Logon 14Number of Views Forescout 8.0 - RADIUSwith CAS Configuration - RSA Ready SecurID Access Implementation Guide 4Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?