There seems to be a lot of confusion concerning the new licensing methods. In the initial release (ML184.108.40.206 and MultiStore 220.127.116.11) there were a few problems with the licensing. These have been ironed out now, so if you are still having an issue with licensing after reading this and generating a proper license, UPDATE and REGENERATE the license again from your My Licenses page. If you cannot generate a proper license (cannot enter proper domain), submit a support ticket and we'll generate it for you.
The list of urls your license will work for when generating a BLANK license file:
The definitive list of urls your license will work for after entering proper production domain names:
In order for both www.mydomain.com AND mydomain.com to be licensed, the generated license url must contain the www. prefix.
In order for the license to work on your staging sub-domains, the name 'aspdotnetstorefront' is REQUIRED to be in the name as a prefix to .*.com, so you need to name your sub-domains something like:
When you access the Admin console Configuration - Store Maintenance - Domains from a production url, like https://www.mydomain.com/admin/signin.aspx then you will see green check-marks next to all the properly licensed production urls, AND urls using localhost, but NOT the staging sites (urls using aspdotnetstorefront.*.com).
When you access the Admin console from a STAGING url, like https://staging.aspdotnetstorefront.mydomain.com/admin/signin.aspx then you will see green check-marks next to all the properly licensed STAGING urls, but NOT localhost urls, OR the production sites.
When you access the Admin console from a localhost url, like http://localhost/mydomain/admin/signin.aspx then you will see green check-marks next to all the properly licensed production urls, AND localhost urls, but NOT the staging sites.
When you access the Admin console from an unlicensed url, like https://staging.mydomain.com/admin/signin.aspx then you will see NO green check-marks next to ANY sites, including the localhost, as the license just fails altogether.
Other concerns seem to be "I don't know what url to put yet for my production url."
You get to generate 2 license keys. If you don't know your live domain name yet, then create a BLANK key (do not enter a domain name). This is good for localhost and aspdotnetstorefront.*.com domains. The second time you generate a license, please enter your live domain names.
We are aware that mistakes or confusion can occur with this process, so please submit a support ticket if you are unable to generate a proper license file for your site(s), and we can generate one for you. We will require proper verification for your license of course.