So, it happened. I've been using WHM and CPanel for years like everyone else, and someone has finally blown my damn mind. Here are the bullet points -- sweet jesus do I hope there are some creative souls out there! 
He installed the wildcard cert on example.com, and I thought that it would at least allow his users to use https at user1.example.com and user2.example.com. But it doesn't.
Is that because the CNAME records are pointing to a different CPanel account??
Anyone every tried to wildcard SSL a dynamically created set of subdomains?
Thanks!
*Mind Blown* (smoke)
- User has a WP site at example.com. That site is informational and needs no SSL.
- User requested a separate CPanel account at my.example.com because the WP redirection of example.com was interfering with the PHP system he was creating in terms of subdomains (see below).
- User's site at my.example.com hosts a multi-account php system.
- User's PHP system, when creating a new account, uses CPanel API to log into example.com and add a CNAME record, creating user1.example.com, user2.example.com, user3.example.com.
- Each of these dynamically created subdomains simply loads my.example.com but with a custom subdomain for his web app's users. I can see how the custom name could be a selling point for his customers.
- Now, the fun part. Are you ready? User buys a wildcard SSL cert from Comodo and tries to install it on two different CPanel accounts, citing that the cert was intended for *.example.com.
He installed the wildcard cert on example.com, and I thought that it would at least allow his users to use https at user1.example.com and user2.example.com. But it doesn't.
Is that because the CNAME records are pointing to a different CPanel account??
Anyone every tried to wildcard SSL a dynamically created set of subdomains?
Thanks!
*Mind Blown* (smoke)