Apache Relay Server for Afaria 7: https problem

[Former Member]

Hi all,

  i'm starting using Afaria 7 with Sybase Relay Server for encrease security.

We have Afaria 7 sp1 installed in local network and only one Sybase Relay Server 12.0.1 on Apache2.2.12 that communicate with Afaria.

Our Android devices can communicate with Relay Server with "client_security = off" option, so http on port 80. Problem is that the same Android devices can't even communicate with Relay Server with "client_security = on" (https, port 443). Afaria app client display a poor-verbose "Server not found" error; we checked DNS and communication problems: Afaria client can find Relay Server but can't initiate connection with.

Apache configuration seems ok, but we have a self-signed certificate for testing purpoises.

Does Afaria app client can authenticate with a self-signed certificate on Relay Server?

Thanks for your time,

Roberto

[former_member10452 · Accepted solution]

Hi Roberto,

Please make sure that you use correct FQDN in your self-signed certificate. If you are accessing with hostname then cert should be issued to hostname.

Also, i would like to know that request is going to Afaria at all or not through Relay server. I hope it's not going and your device reject relay server URL itself?

Regards,

Abhishek Joshi

[Former Member · Accepted solution]

Hi Abhishek,

   my device can't communicate to relay server with "Server not found" error when i can find my device in Apache access logs..

I'm going to try correct FQDN in my self-signed certificate, thanks.

Regards,

Roberto

[shival_tailor · Accepted solution]

Hi Roberto,

That should be good to go then, once you resolve the warning message by correcting FQDN in your certificate.

The security warning can be resolved in a browser by clicking over but cannot on the mobile device by application as the shortened URL gest resolved in background and if there is a warning state then the process cannot get through.

Regards,

Shival

[Former Member · Accepted solution]

Hi Shival, Abhishek

    problem was non-FQDN certificate, and non standard https port. We used 8443 port in an our test machine. Although it was specified in the Afaria client, it was unable to connect still with FQDN certificate.

We switched to default 443 ports and now it works.

Many thanks,

Roberto

[shival_tailor]

Hi Roberto,

How is your external address setup? Is it tied up with a DNS or an IP? Are you able to launch default web page, 'It works!' with HTTPS?

Regards,

Shival

[Former Member]

Hi Shival,

   our external address is tied up with DNS and i'm able to access to HTTPS default web page with web browser. An HTTP configuration (with "client_security = off") works correctly.

Obviously i got security warning because self-signed certificate. Maybe problem is that Afaria client doesn't support self-signed certificate?

Regards,

Roberto