My client has a wildcard certificate *.thierdomain.com that they are using for half a dozen of production web sites.
For each of theses sites there are duplicates in several environments, dev, qa, pre-prod, etc.
Up until now other environments than prod did not have a SSL certificate at all as there were no https specific functionality. So the sites ran only over http (within corporate network) for non-prod, and https only for prod.
Now we are adding some functionality that I'd like to test over both http and https in a single environment.
I would usually use self-signed certs for that, but this client has a wildcard certificate already available. It would be so easy just get this cert installed on other environments web servers.
Are there any negative security implications of that?