SSO Very Slow

[willk]

Hi All,

We are working on upgrading from 7.10 to 8.6 and implementing SSO, but have found that the link with the token takes ages to load. Generating the token link is quick and isn't an issue. However, loading that singlesignon link takes 15-16 seconds in nearly all cases. Our database is pretty large (about 1.6GB), but most of those are in the tblemails. Watching the mysql database shows no long queries and most connections sleeping while we wait for 15 seconds for the SSO to complete and redirect to the users profile page. It works 100%, but it's the call to redirect URL provided by CreateSsoToken (e.g. oauth\singlesignon.php?access_token=xxx) that takes 15 seconds.

We have done all the normal things, the connection to the DB is set to 127.0.0.1 rather than localhost, and works fine for normal logins (usually about 2 seconds), skip-name-resolve is turned on in MySQL, and performance of MySQL for both WHMCS on all other calls, and GFI Helpdesk work 100% without issue. It's just the SSO that is unusable. With the deprecation and removal of AutoAuth (which took about 3 seconds) we aren't sure how to go about upgrading and that's a major issue given WHMCS list 7.10 as EOL even though they still release urgent security patches if necessary.

Is there anyone else having this kind of issue?

Is anyone else using SSO?

Noting we are using CURL (not local API) to call SSO using the CreateSsoToken (https://developers.whmcs.com/api-reference/createssotoken/).

Thanks,
Will

[yggdrasil]

I used this on version 7 on a tiny database, and it takes around +30 seconds to even start loading. So yes, it's not your installation or server, but just how WHMCS works. Normally, it would take almost a minute for a user to log in using that WHMCS API call. Then again, WHMCS is not known to be fast or performance, and their API calls are certainly not fast to process either. It's not your server, it's the code.

Edited January 6, 2023 by yggdrasil