Hi,
In System Requirements for SBWS1.0 (http://msdn.microsoft.com/en-us/library/windowsazure/jj193011(v=azure.10).aspx), we see that a Multi-Node Farm Certificate requirement is a "domain" (wildcard) certificate (eg: *.example.com). This is simply not an option in our environment. We are left with an unsatisfactory situation where our sb:// endpoint is whichever of our nodes happens to be the last listed Subject Alternate in the x.509 certificate for the farm.
Am I missing something, is there a potential for a client-based workaround, and/or is there any likelihood of this being changed in the future? As it is, in order to reach a satisfactory, redundant solution, it would seem we either need to have a subdomain allocated for our application in each of its different instances, or have a wildcard domain certificate -- neither of which are even remotely likely.
Thanks!
In System Requirements for SBWS1.0 (http://msdn.microsoft.com/en-us/library/windowsazure/jj193011(v=azure.10).aspx), we see that a Multi-Node Farm Certificate requirement is a "domain" (wildcard) certificate (eg: *.example.com). This is simply not an option in our environment. We are left with an unsatisfactory situation where our sb:// endpoint is whichever of our nodes happens to be the last listed Subject Alternate in the x.509 certificate for the farm.
Am I missing something, is there a potential for a client-based workaround, and/or is there any likelihood of this being changed in the future? As it is, in order to reach a satisfactory, redundant solution, it would seem we either need to have a subdomain allocated for our application in each of its different instances, or have a wildcard domain certificate -- neither of which are even remotely likely.
Thanks!