We are not actively pursuing LDAP/AD integration at the moment, however we are looking at making WHMCS OAuth2 compatible which will allow you to create authentication bridges to services like cPanel.
More details will be coming, so stay tuned at blog.whmcs.com.
15 Comments
Login to post a comment.
More details will be coming, so stay tuned at blog.whmcs.com.
This is done via LDAP, (a fully open standard), and it works great. Even without the 'group membership' integration aspect, a BASIC LDAP implementation would be extremely helpful.
I suspect the folks asking "WHY" have never worked in a business that uses Windows Server & Active Directory.
As for businesses being able to "develop their own workings for WHMCS" - as far as I am aware, the API that WHMCS exposes does not allow for this level of integration, and regardless of that, many quite small businesses use Active Directory.
RE: running AD, they may well be, but that wasnt my point, my point was they can afford to develop their own workings of whmcs. (or any system they choose for that matter).
We are not all that lucky of course.
Most AD integration work similar to oauth/openid in that it takes the "authentication" aspect of AAA and leaves authorization and accounting to the application. That would mean the roles, logging, etc is contained within whmcs, and authenticate the user against ad/ldap/radius. The module would not set the required credentials as you suggest, it would instead query ad each time for the password, just like radius auth.
Large comapnies have deeper pockets, yes, and nearly all of them use AD.
So if you want to do this:
either put together something for your current system to create the admin account, give a role etc on the whmcs installation via its API (see the documentation).
Or you create a module in whmcs that sets the required credentials when an admin is created in whmcs (see the hooks documentation), Either way is workable and i see no reason why this would be a whmcs issue or why it should become a feature. I would imagine the highest percentage of whmcs users are resellers that have absolutely no need for this.
Large companies/corporations have far deeper pockets to foot the cost of developing their own systems.
Two things we need it for:
security groups for whmcs management, ie groups in AD that would match to the security groups (admins, sales, support, custom). Make all members of the sales team in AD automatically have access to the sales role in whmcs.
we use ad/nps/radius with our clients as well, so intregation there would be great. Reading users out of AD would be ok, but creating users in AD would be the best.
I am willing to pay a small fee to see this in the 5.2 release!
As of today, we have logins for this system (AD ok or not):
WHMCS (AD No)
MODx (AD Yes)
MediaWiki (AD Yes)
Exchange mail (AD Yes)
Wordpress (AD Yes)
LiveZilla (AD No)
KeePass (AD Yes)
7 systems, 7 usernames, 7 password.
And here we only need 3 accounts, one of them only for out main system; WHCMS.
This would also allow the admin to centrally manage the users permissions. For example, in the event someone is terminated, the admin can easily terminate access to all systems for that user.
Another reason is to provide rights based on domain profiles, much like you do in WHMCS with Administrator Roles. The difference being that this would all be centrally managed and deployed from the domain.
Also, many corporate policies and network security policies force IT administrators to use Microsoft Active Directory for Authentication and would not allow an independently managed system for credentials, like WHMCS.