If there was no other way to lock things down some, yes. As it is you can set up HTTP AUTH, or Yubikey, and/or IP restrictions (even "tunneling" through a VPN that's whitelisted) and more. Them charging fees for *some* methods might not be appreciated, but you're not held hostage to those methods. Can't fault them for it in this case.
I am fairly new to the system / development of WHMCS and I was curious as to whether the location of a WHMCS installation could cause issues when it comes to setting up google, facebook, twitter integrations.
For example, if WHMCS is installed on someone's site as www.exampledomain.com/whmcs
Where the required credentials do not allow you to include /whmcs into the domain entrees, is this going to cause issues as you would only be able to include www.exampledomain.com
The reason I ask, is because I am currently working on a system installed in this fashion and it is the only reason I can possibly see causing me issues when trying to implement the sign-in integration functions available on WHMCS.
Thanks in advance for any response!