You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Login action not working in OpenNebula Tenants module for WHMCS, when cloud frontend use HTTPS. A client with a service active, when execute the Login button is not getting automatically authenticated and WHMCS throws error in authtentication. The error is inside /usr/share/one/whmcs/modules/servers/OpenNebulaTenants/app/libs/OpenNebulaTenantsAPI.php, or in a production enviroment, /var/www/whmcs/modules/servers/OpenNebulaTenants/app/libs/OpenNebulaTenantsAPI.php. The curl function is not taking in count the protocol for building the URL, and when you dont specify the protocol, is assumed HTTP by default. Thats why we are getting a permanent redirect on our cloud reverse proxy and the authentication token could not be gathered. Check the reverse proxy logs below:
When Login button is executed, should not redirect to the cloud frontend of the given service on the same tab. Instead, I would recommend to open a new tab with the cloud frontend URL. On this way the client wont loose the WHMCS tab and could access to others clouds where his account is active, without the need of reopen WHMCS on a new tab.
Details
Affected Component: [OpenNebula Tenant module]
Hypervisor: [KVM]
Version: [6.10.2]
Additional context
Add any other context about the problem here.
Progress Status
Code committed
Testing - QA
Documentation (Release notes - resolved issues, compatibility, known issues)
The text was updated successfully, but these errors were encountered:
Franco-Sparrow
changed the title
Login Action not working in OpenNebula Tenants module for WHMCS
Login Action not working in OpenNebula Tenants module for WHMCS [WORKAROUND INCLUDED]
Jan 28, 2025
Franco-Sparrow
changed the title
Login Action not working in OpenNebula Tenants module for WHMCS [WORKAROUND INCLUDED]
Login action not working in OpenNebula Tenants module for WHMCS [WORKAROUND INCLUDED]
Jan 28, 2025
Franco-Sparrow
changed the title
Login action not working in OpenNebula Tenants module for WHMCS [WORKAROUND INCLUDED]
Login action not working in OpenNebula Tenants module for WHMCS, when cloud use HTTPS [WORKAROUND INCLUDED]
Jan 28, 2025
Franco-Sparrow
changed the title
Login action not working in OpenNebula Tenants module for WHMCS, when cloud use HTTPS [WORKAROUND INCLUDED]
Login action not working in OpenNebula Tenants module for WHMCS, when FireEdge HTTPS [WORKAROUND INCLUDED]
Jan 28, 2025
Description
Login action not working in OpenNebula Tenants module for WHMCS, when cloud frontend use HTTPS. A client with a service active, when execute the Login button is not getting automatically authenticated and WHMCS throws error in authtentication. The error is inside
/usr/share/one/whmcs/modules/servers/OpenNebulaTenants/app/libs/OpenNebulaTenantsAPI.php
, or in a production enviroment,/var/www/whmcs/modules/servers/OpenNebulaTenants/app/libs/OpenNebulaTenantsAPI.php
. The curl function is not taking in count the protocol for building the URL, and when you dont specify the protocol, is assumed HTTP by default. Thats why we are getting a permanent redirect on our cloud reverse proxy and the authentication token could not be gathered. Check the reverse proxy logs below:We should be getting something like this:
To Reproduce
Expected behavior
After executed the Login button, the WHMCS should redirect to the cloud frontend without ask for authentication. The SSO should works.
Workaround
As all public cloud we have are using HTTPS, the following modification will just work if your frontend is using this secured protocol.
Edit
OpenNebulaTenantsAPI.php
:Change this:
To this:
Restart apache2:
Recommendation
When Login button is executed, should not redirect to the cloud frontend of the given service on the same tab. Instead, I would recommend to open a new tab with the cloud frontend URL. On this way the client wont loose the WHMCS tab and could access to others clouds where his account is active, without the need of reopen WHMCS on a new tab.
Details
Additional context
Add any other context about the problem here.
Progress Status
The text was updated successfully, but these errors were encountered: