I now use Fedora 34 these days.

pranav@fedora ~> cd /etc/ld.so.conf.d/
pranav@fedora ~> sudo touch vmware-authdlauncher.conf
[sudo] password for pranav:
pranav@fedora /etc/ld.so.conf.d> ls
libiscsi-x86_64.conf                 tix-x86_64.conf
pipewire-jack-x86_64.conf      vmware-authdlauncher.conf
pranav@fedora ~> cat /etc/ld.so.conf.d/vmware-authdlauncher.conf
#pranav did this
#linking libssl and libcrypto
/usr/lib/vmware/lib/libssl.so.1.0.2
/usr/lib/vmware/lib/libcryto.so.1.0.2
pranav@fedora ~> sudo ldconfig
[sudo] password for pranav:
 
And when I wanted to verify whether it worked or not, well it didn't because as you can see:

pranav@fedora ~> ldd /usr/sbin/vmware-authdlauncher
linux-vdso.so.1 (0x00007ffe7836d000)
librt.so.1 => /lib64/librt.so.1 (0x00007faa6ddc1000)
libssl.so.1.0.2 => /usr/lib/vmware/lib/libssl.so.1.0.2/libssl.so.1.0.2 (0x00007faa6db50000)
libcrypto.so.1.0.2 => not found
libdl.so.2 => /lib64/libdl.so.2 (0x00007faa6db49000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007faa6db2e000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007faa6db0d000)
libc.so.6 => /lib64/libc.so.6 (0x00007faa6d93c000)
/lib64/ld-linux-x86-64.so.2 (0x00007faa6e0e9000)
libcrypto.so.1.0.2 => not found
pranav@fedora ~>

And I wonder why it didn't worked for me. And it showed libcryto.so error twice!
I even restarted the distro to see whether I will get an error or not. Got the new error. At least it doesn't mention libssl anymore.

@petra_zThank you petra. I finally figure out what might have went wrong. I left a word "p" when I write libcrypto.so.1.0.2. That was a dumb mistake.

Anyway, thanks a lot.