# Redundancy and genuine certificates

**URL:** <https://forum.inductiveautomation.com/t/redundancy-and-genuine-certificates/2844>\
**Category:** Ignition\
**Created:** [April 5, 2011, 9:17pm UTC](https://forum.inductiveautomation.com/t/redundancy-and-genuine-certificates/2844 "2011-04-05T21:17:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![diat150](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@diat150](https://forum.inductiveautomation.com/u/diat150)\
**Post date:** [April 5, 2011, 9:17pm UTC](https://forum.inductiveautomation.com/t/redundancy-and-genuine-certificates/2844/1 "2011-04-05T21:17:27Z")

</div>

My customer has a question about the genuine SSL certificate on the backup server. Obviously you will need a second certificate and it will have a little bit different information on it, like IP addresses and names.

What happens if a user is logged on to the master application during a failure? They should swap over to the backup, but what happens if they have never downloaded the certificate from the backup server?

So I guess we need some clarification on what happens during the failover process if we are using SSL with genuine certificates.

---

<div class="post-metadata">

**Author:** ![diat150](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@diat150](https://forum.inductiveautomation.com/u/diat150)\
**Post date:** [April 7, 2011, 2:31pm UTC](https://forum.inductiveautomation.com/t/redundancy-and-genuine-certificates/2844/2 "2011-04-07T14:31:29Z")

</div>

I got my two servers up yesterday and was able to test this a little bit. It looks like a user will not be prompted to download the certificate from the backup server if they were connected to the master already when the failover occured. If a new client tries to connect while the master server is down, they will be prompted to download the certificate from the backup server.

---

<div class="post-metadata">

**Author:** ![jim\_lapratt](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@jim\_lapratt](https://forum.inductiveautomation.com/u/jim_lapratt)\
**Post date:** [April 7, 2011, 3:23pm UTC](https://forum.inductiveautomation.com/t/redundancy-and-genuine-certificates/2844/3 "2011-04-07T15:23:48Z")

</div>

That is good to know. ![:thumb_left:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/e26afb081ddde6df016df6ee49159cf56aaca688.gif ":thumb\_left:")

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [April 13, 2011, 2:22am UTC](https://forum.inductiveautomation.com/t/redundancy-and-genuine-certificates/2844/4 "2011-04-13T02:22:34Z")

</div>

Yeah the SSL cert prompting is part of the browser, so once the client is launched it does it behind the scenes.