Possible bug in admin / reseller / client domain allocation
We have hit on a possible bug, or combination of bugs. I know there is a bug tracker, but wanted to post here first in case we are missing something or others came across this.
We have resellers and clients setup in ISPConfig 184.108.40.206 on Debian Lenny.
Log in as admin, set up a reseller, set up a domain and assign the domain to a reseller. Then log in as reseller, click on sites, websites, domain, and click on the stats tab. This gives us an error:
The website domain is then no longer available to the reseller logged in.
Logging back in as admin reveals that the domain is now apparently owned by a different client. This is rather worrying.
So, reviewing the ispconfig database ( dbispconfig in our case) shows that that all web domains created by the admin user have the sys_userid of 1 (the admin user). Is this right?
We think that when the domain is assigned to the client, the domain should perhaps inherit the sys_userid of the new client. So when we set the sys_userid to that of the new client, the domain pops back into the client's control panel, and the client can then view the stats tab.
Further investigation shows that this behaviour is only exhibited when the web domain is assigned to a reseller, not to a non-reseller client. When the domain assigned to the reseller is accessed, and the stats tab is clicked, we get the error mentioned and the value for the sys_groupid in the web_domain table is changed.
Is this behaviour repeatable by anyone else?
Has something happened to our data to result in inconsistency?
Is somewhere we can see a description of the database schema and how the various sys_userid, sys_groupid, client_id should be interacting?