01-08-2013 10:26 AM
I am trying to install the Mobile Fusion in my lab to test e present the results to my boss... I dont have a URL domain, because wont have any access from the Internet, so i dont have a certificate too... Its possible to install the Universal Device Service and the Mobile Fusion without the URL domain e a valid certificate?
01-08-2013 10:30 AM
01-09-2013 10:23 AM - edited 01-09-2013 10:26 AM
All communication with the UDS server is done over SSL. So whether or not your users are coming in over the internet or not is irrelevent. Android devices don't care about if the certificate is trusted or not so you can use an internal CA to generate your certificate and then just ignore the warnings when activating.
Since you won't have a public DNS for this you would just use the FQDN of the server for the subject/SAN of the cert.
01-28-2013 01:36 PM - edited 01-28-2013 01:38 PM
I still can not install the UDS....
I created a CA and installed the root certificate on the machine...
Created and signed the user certificate using the FQDN and exported to .p12 and got the message:
"The setup application cannot validate the SSL certificate that you specified. You must verify the location and password of the SSL certificate."
01-28-2013 01:38 PM - edited 01-28-2013 03:37 PM
What is the subject/SAN of your certificate. If you didn't choose to make it a webserver cert on the CA the subject will be an email address rather than the FQDN of the server.
01-29-2013 09:31 AM
I can't view that since it has a password on it.
You can view the info in IIS on the computer you completed the CSR on. Open IIS and click on the servername and then select Server Certificates. Double-click the certficate and go to the details tab. Both the Subject and the SAN are available here. One of these must be the intended public DNS of your Communication website
01-29-2013 10:07 AM - edited 01-29-2013 10:18 AM
Very Sorry... CPqD12345
Thats the problem, I dont have public DNS or external access... I'm using a internal network on my lab for the tests... IP range: 192.168.5.0/24
01-29-2013 10:29 AM - edited 01-29-2013 10:31 AM
The SAN of your cert looks to just be host name of the machine and not the FQDN.
Also was this issued by an enterprise certificate authority? It looks like a self-signed certiicate because I don't see any root cert attached to it. If the root certificate isn't trusted it will fail. When i import it into IE and look at the certfication path it shows:
This certificate has an invalid digital signature.
I do tend to use my internal FQDN in testing since I don't need public access to test.