We have created our own RPM to install the Linux A2A client of a previous release of PAM. Now we see users migrating to Linux RHEL 8 and after the A2A client is installed and connected to PAM they get this error. The application has a test script they run and here are the results.
Calling PAM using 'alias' and 'cache'
PAMalias ==> XXXXX
PAMcache ==> true
/opt/cloakware/catech/cspmclient/bin/cspmclient: error while loading shared libraries: libidn.so.11: cannot open shared object file: No such file or directory
Return from PAM...
PAM return code ==>
PAM user-id ==>
PAM password ==>
I have had another user have this similar issue and here is their error.
We attempted and rec’d the following error:
$: ksh MyScripts.ksh Account true
/opt/cloakware/catech/cspmclient_v.4.12.3/bin/cspmclient:
error while loading shared libraries: libidn.so.11: cannot open shared object file: No such file or directory
Return Code:
User ID:
Password:
We took a look at /usr/lib64 directory and the soft link is “libidn2.so.0 -> libidn2.so.0.3.6”:
User@SERVER [/usr/lib64]
$: ls -lrt libidn*
lrwxrwxrwx. 1 root root 16 Jun 10 2019 libidn2.so.0 -> libidn2.so.0.3.6
-rwxr-xr-x. 1 root root 162224 Jun 10 2019 libidn2.so.0.3.6
Release : 4.1
The required library libidn.so.11 was not on the system
~]# find / -name libidn.so.11
When running the following command we found the proper RPM containing this file was not installed
~]# rpm -qa |grep libidn
libidn2-2.2.0-1.el8.x86_64
After installing libidn-1.34-5.el8.x86_64.rpm the file was found and issue resolved.
~]# find / -name libidn.so.11
/usr/lib64/libidn.so.11
~]# rpm -qa |grep libidn
libidn-1.34-5.el8.x86_64
libidn2-2.2.0-1.el8.x86_64