Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
998 Views

Cannot connect to Intel Unite Organization with iOS

We have installed a complete demo Intel Unite Enterprise environment and we can use a Windows 10 client for presenting, this all works.

But when we want to use an iPhone iOS 12 with Intel Unite 4 app we can see our Intel Unite organization but we get a message "connection failed".

The iOS device gets its information from the landing page (name, server, orgID).

The phone does also not come up in the list of devices on the admin overview page of the enterprise server (we do see the Windows 10 laptop).

 

any help would be very much appreciated.

0 Kudos
7 Replies
Highlighted
Moderator
12 Views

Hello WOltl, Thank you for joining this Intel Community. Please check this information: A. Is the device connected to the corporate network? B. Corporate firewalls may not be allowing the connection to Intel Unite®. C. Are you able to provision the device? Wanner G. Intel Customer Support Technician Under Contract to Intel Corporation
0 Kudos
Highlighted
Beginner
12 Views

Hi,

 

yes it is connected to the corporate network

if i try it from a windows client (lapop, windows 10) connected to the same corporate network it works

i can go the the provision url ands the iphone gets the information with the orgid, name, etcetra.

 

0 Kudos
Highlighted
Moderator
12 Views

Hello WOltl, Thank you for your response. The issue reported could be caused by the certificate on the client. We will do further research and get back to you as soon as possible. Wanner G. Intel Customer Support Technician Under Contract to Intel Corporation
0 Kudos
Highlighted
Beginner
12 Views

Any luck with this issue? Having the exact same problem with an ipad.. Can see the organization and provisioning is good, but fails to connect. No issue with the certificate with Windows clients or with Chromebook.

 

Thanks for any insight,

Joel

0 Kudos
Highlighted
Moderator
12 Views

Hello all, To address this issue, we recommend creating an open certificate. Please follow these instructions to create an open ssl certificate. Assign this to your ISS environment (Binding), then try to connect again with your IOS device. Creating Self-Signed Certificates with OpenSSL: One of the easiest ways of creating a self-signed certificate is to use the OpenSSL command line toolthat is available on most platforms and installed by default on Mac OSX. First create a private key file: openssl genrsa -out myselfsigned.key 2048 Then create the self signed certificate: openssl req -new -x509 -sha256 -key myselfsigned.key -out myselfsigned.cer -days 365 -subj /CN=www.mysite.com You can use any filenames you like for the key and certificate (.cer) files. The /CN parameter needs to be set to the required hostname (e.g. for https://www.mysite.com in the example above). The daysparameter specifies the expiration date as days from today’s date. There’s even a site to do this if you don’t feel like downloading OpenSSL, but of course it’s more secure to do it yourself. On Apache servers the key and certificate file can be used directly in your SSL configuration. With IIS you need a PFX file so that you can import the certificate into the Server Certificates section of IIS. OpenSSL can create the PFX file for you as well: openssl pkcs12 -export -out myselfsigned.pfx -inkey myselfsigned.key -in myselfsigned.cer Consider Creating Your Own Certificate Authority (CA): One problem with self-signed certificates is that you’ll need to set up trust relationships for each certificate on each device. An alternative is to create your own Certificate Authority (CA) root certificate and then create certificates based on it. Instead of paying a commercial CA to create SSL certificates on your behalf, you are acting as your own CA. The advantage is that your custom CA certificate only has to be installed once on each device. The devices will then automatically trust any certificates you issue based on your root CA certificate. Creating the CA certificate is a simple two step process. First create a private key file as before: openssl genrsa -out myCA.key 2048 Then create the certificate: openssl req -x509 -sha256 -new -key myCA.key -out myCA.cer -days 730 -subj /CN="My Custom CA" The private key file (myCA.key) is only used when creating new SSL certificates. You can create as many certificates as you like based on this CA certificate. There’s an extra step involved because you have to create a CSR (Client Signing Request) as if you were purchasing a commercial SSL certificate. First you would create a private key: openssl genrsa -out mycert1.key 2048 and then create the CSR: openssl req -new -out mycert1.req -key mycert1.key -subj /CN=www2.mysite.com Then use the CSR to create the certificate: openssl x509 -req -sha256 -in mycert1.req -out mycert1.cer -CAkey myCA.key -CA myCA.cer -days 365 -CAcreateserial -CAserial serial The certificate created (mycert.cer) can be installed on a web server and accessed from any iOS device that already has the CA certificate installed. Wanner G. Intel Customer Support Technician Under Contract to Intel Corporation
0 Kudos
Highlighted
Moderator
12 Views

Hello all, Were you able to follow the steps recommended above? Wanner G. Intel Customer Support Technician Under Contract to Intel Corporation
0 Kudos
Highlighted
Moderator
12 Views

Hello all, If you have any further questions, we will be glad to help you. Wanner G. Intel Customer Support Technician Under Contract to Intel Corporation
0 Kudos