Upgrade Readiness Check fails with Custom binaries configured but not available in lib or bin

Products

• SITEMINDER

Issue/Introduction

Upgrading SiteMinder Policy Server to R12.8SP8 but the Upgrade Readiness Check fails with following error.

===================================================================== IMPORTANT: Upgrade Readiness Check ---------------------------------- The Upgrade Readiness utility has identified potential issues. Remove or upgrade (to a 64-bit version) the identified custom components after the upgrade completes. Starting the Policy Server without doing so will likely result in errors. See the documentation for more information about the utility. =================================================== Custom binaries configured but not available in lib or bin: =================================================== Binary Name: smsamplecustomauth Object Name: Sample_Custom_Auth Object Type: Authentication Scheme Object Path: AuthScheme[Sample_Custom_Auth] Binary Path: Couldn't find this binary in lib or bin Description: Couldn't determine the bitness

Cause

Policy Server "Upgrade Readiness Check" checks several things including the custom libraries.

It has identified a custom authentication scheme which indicates it is using "smsamplecustomauth" as the binary but this filename is not found in the bin(for windows) or lib(linux) folders.

As such, it is unable to determine if it is 32bit or 64bit library and fail to perform the Sample_Custom_Authupgrade.

Resolution

Do a Policy Export (XPSExport -xb policystore.xml) and do a text search for the Object Name (Sample_Custom_Auth)

Look for the section having this object name.

<Object Class="CA.SM::AuthScheme" Xid="CA.SM::AuthScheme@0d-00000001-1234-1234-00000000000000001" CreatedDateTime="2019-03-29T05:46:51" UpdatedBy="XPSDictionary::Import" UpdateMethod="Internal" ExportType="Replace">     <Property Name="CA.SM::AuthScheme.IPCheck">         <BooleanValue>false</BooleanValue>     </Property>     <Property Name="CA.SM::AuthScheme.PersistSessionVars">         <BooleanValue>false</BooleanValue>     </Property>     <Property Name="CA.SM::AuthScheme.IsRadius">         <BooleanValue>false</BooleanValue>     </Property>     <Property Name="CA.SM::AuthScheme.IgnorePwCheck">         <BooleanValue>false</BooleanValue>     </Property>     <Property Name="CA.SM::AuthScheme.AllowSaveCreds">         <BooleanValue>false</BooleanValue>     </Property>     <Property Name="CA.SM::AuthScheme.Type">         <NumberValue>15</NumberValue>     </Property>     <Property Name="CA.SM::AuthScheme.AllowAuthLevelOverride">         <BooleanValue>false</BooleanValue>     </Property>     <Property Name="CA.SM::AuthScheme.IsUsedbyAdmin">         <BooleanValue>true</BooleanValue>     </Property>     <Property Name="CA.SM::AuthScheme.Library">         <StringValue>smsamplecustomauth</StringValue>     </Property>     <Property Name="CA.SM::AuthScheme.Level">         <NumberValue>5</NumberValue>     </Property>     <Property Name="CA.SM::AuthScheme.IsTemplate">         <BooleanValue>false</BooleanValue>     </Property>     <Property Name="CA.SM::AuthScheme.Desc">         <StringValue>Directory username/password</StringValue>     </Property>     <Property Name="CA.SM::AuthScheme.Name">         <StringValue>Sample_Custom_Auth</StringValue>     </Property> </Object><!-- Xid="CA.SM::AuthScheme@0d-00000001-1234-1234-00000000000000001" -->

See if this object ID "0d-00000001-1234-1234-00000000000000001" is referenced anywhere to check if it is actually in use.

If there are no references found for this object then it would be safe to delete this object from AdminUI (or remove the object section from policystore.xml and reimport to overwrite the policy store).

 

If there are references to this Object ID then check the older or other existing environment to find this library and copy over to this Policy Server but must check with the developer and administrator why these files were missing as there could be some reason why they were removed.

Try the upgrade again.