Josh Martin
shared this idea
9 months ago
3
Votes
Login to Vote
Currently in Chromium based browsers the WHMCS Connect utility for accessing WHM servers only functions on servers that share a root domain with WHMCS itself. WHM on other domains cannot be accessed due to how Chromium handles cross-site authentication tokens. You get stuck in a login loop where the authentication never completes. This is regardless of whether you use the root password or an API token.
For example, if my WHMCS installation is at clients.domain.com, I could use WHMCS to connect to WHM on server1.domain.com, but not vps.someotherdomain.com.
The login to cPanel function for specific accounts on these same servers does work, however, and those are opened in another tab vs. loading in a frame. If the WHMCS Connect module could work the same way I think it would overcome this issue. This would be very helpful for companies like us who host and manage many client VPS's.
For example, if my WHMCS installation is at clients.domain.com, I could use WHMCS to connect to WHM on server1.domain.com, but not vps.someotherdomain.com.
The login to cPanel function for specific accounts on these same servers does work, however, and those are opened in another tab vs. loading in a frame. If the WHMCS Connect module could work the same way I think it would overcome this issue. This would be very helpful for companies like us who host and manage many client VPS's.
1 Comment
Login to post a comment.
Thanks for your suggestion. The reason for this behaviour is a change in the handling of the SameSite cookie attribute in Chromium browsers.
In some Chromium based browsers you can disable the "SameSite by default cookies" option in the browser settings, which will enable WHMCS Connect to operate.