# Canary Security with Ignition

**URL:** <https://forum.inductiveautomation.com/t/canary-security-with-ignition/81790>\
**Category:** 3rd Party Modules\
**Tags:** security\
**Created:** [November 12, 2023, 2:15am UTC](https://forum.inductiveautomation.com/t/canary-security-with-ignition/81790 "2023-11-12T02:15:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carel\_de\_Jager](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carel_de_jager/32/50760_2.png) [@Carel\_de\_Jager](https://forum.inductiveautomation.com/u/Carel_de_Jager)\
**Post date:** [November 12, 2023, 2:15am UTC](https://forum.inductiveautomation.com/t/canary-security-with-ignition/81790/1 "2023-11-12T02:15:18Z")

</div>

Hi

I'm just wondering if there is anything special, I need to do when reading Canary trends into Ignition Trend components when security in Canary is activated.  
It was working fine before I activate security. Axiom works fine with the new security.  
I did change the port in the Canary Ignition module to the default https.  
I'm using the same logon and password which works for me in Axiom.

---

<div class="post-metadata">

**Author:** ![Carel\_de\_Jager](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carel_de_jager/32/50760_2.png) [@Carel\_de\_Jager](https://forum.inductiveautomation.com/u/Carel_de_Jager)\
**Post date:** [November 21, 2023, 6:55am UTC](https://forum.inductiveautomation.com/t/canary-security-with-ignition/81790/2 "2023-11-21T06:55:57Z")

</div>

I got the security between Canary Historian / Axiom and Ignition working through the default secured port.  
Happy to help if somebody needs assistance in the future.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 21, 2023, 12:46pm UTC](https://forum.inductiveautomation.com/t/canary-security-with-ignition/81790/3 "2023-11-21T12:46:27Z")

</div>

Please summarize your solution for future readers... since you are apparently the local expert. 😀

---

<div class="post-metadata">

**Author:** ![David\_Rodriguez](https://avatars.discourse-cdn.com/v4/letter/d/b5e925/32.png) [@David\_Rodriguez](https://forum.inductiveautomation.com/u/David_Rodriguez)\
**Post date:** [February 28, 2025, 9:31am UTC](https://forum.inductiveautomation.com/t/canary-security-with-ignition/81790/4 "2025-02-28T09:31:33Z")

</div>

Hi Carel would you be so kind to assist us? Which port did you use for HTTPS?

---

<div class="post-metadata">

**Author:** ![michaeelphillips](https://avatars.discourse-cdn.com/v4/letter/m/cc9497/32.png) [@michaeelphillips](https://forum.inductiveautomation.com/u/michaeelphillips)\
**Post date:** [June 9, 2025, 1:37pm UTC](https://forum.inductiveautomation.com/t/canary-security-with-ignition/81790/5 "2025-06-09T13:37:50Z")

</div>

When Canary security is enabled, Ignition may require more than just changing the HTTPS port. Make sure Ignition trusts Canary’s SSL certificate, if it’s self-signed, you need to import it manually.