# SSL trusted certificates for HTTPS

**URL:** <https://forum.sierrawireless.com/t/ssl-trusted-certificates-for-https/7135>\
**Category:** Open AT\
**Created:** [April 4, 2014, 7:20am UTC](https://forum.sierrawireless.com/t/ssl-trusted-certificates-for-https/7135 "2014-04-04T07:20:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mandy](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@mandy](https://forum.sierrawireless.com/u/mandy)\
**Post date:** [April 4, 2014, 7:20am UTC](https://forum.sierrawireless.com/t/ssl-trusted-certificates-for-https/7135/1 "2014-04-04T07:20:47Z")

</div>

I use HTTPS - initialization of SSL is made with wip\_SSLInit. I recognize that the duration of calling different pages varies - the time between creating the data channel with wip\_getFileOpts and the first event WIP\_CEV\_OPEN.  
Could it be that the SSL library has a certain number of SSL certificates, which are trusted? Where can I get a list of those certificates, which are trusted from OpenAT?

---

<div class="post-metadata">

**Author:** ![lotam](https://avatars.discourse-cdn.com/v4/letter/l/958977/32.png) [@lotam](https://forum.sierrawireless.com/u/lotam)\
**Post date:** [April 4, 2014, 5:07pm UTC](https://forum.sierrawireless.com/t/ssl-trusted-certificates-for-https/7135/2 "2014-04-04T17:07:44Z")

</div>

Hi,

Have you got the OpenAT Framework installed?  
If so, you should see the actual code for HTTPS sample, for example:

C:\Program Files\Sierra Wireless\Embedded Software\com.wavecom.openat.ide.spm.lib.plugin.model.Security.1.16.0.201206041340\_1.16.0.201206041340\resources\Security\samples\wipssl\_https\_client\src

Actually, we can specify the cert trusted by including them when we compile the source, there are no cert trusted by default ASAIK…

Hope it helps.

---

<div class="post-metadata">

**Author:** ![mandy](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@mandy](https://forum.sierrawireless.com/u/mandy)\
**Post date:** [April 7, 2014, 9:13am UTC](https://forum.sierrawireless.com/t/ssl-trusted-certificates-for-https/7135/3 "2014-04-07T09:13:55Z")

</div>

Thanks for reply.  
I know the example.

Then I ask myself why calling different https pages varies in time!!!

When I call Google it lasts 2 seconds between wip\_getFileOpts and WIP\_CEV\_OPEN. When I call the page of our company it lasts at least 40 seconds. In my internet browser I have to add the https page of our company to the trusted pages by hand, and Google is trusted automatically. So I thought OpenAT behaves the same.

---

<div class="post-metadata">

**Author:** ![davidc](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@davidc](https://forum.sierrawireless.com/u/davidc)\
**Post date:** [April 7, 2014, 10:39pm UTC](https://forum.sierrawireless.com/t/ssl-trusted-certificates-for-https/7135/4 "2014-04-07T22:39:13Z")

</div>

Hiya,

> [@mandy](#):
>
> In my internet browser I have to add the https page of our company to the trusted pages by hand

Sounds like you have a self-signed certificate on your internal server - which doesn’t have the trust chain required to install automatically. The google certificate will be signed by a trusted registrar and have a trust chain back to the registrar to prove that it’s valid.  
I wonder if the long connection times for your company certificate that you’re seeing OpenAT is to do with the way that the certificate trust chain is being traversed (and because it’s a self-signed certificate, there’s some sort of timeout being triggered before the response is being returned to you).

ciao, Dave