# Will SSO be enabled with 8.3?

**URL:** <https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065>\
**Category:** Ignition 8.3 Early Access\
**Created:** [July 29, 2025, 1:22pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065 "2025-07-29T13:22:02Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brent\_Wassell](https://avatars.discourse-cdn.com/v4/letter/b/f17d59/32.png) [@Brent\_Wassell](https://forum.inductiveautomation.com/u/Brent_Wassell)\
**Post date:** [July 29, 2025, 1:22pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/1 "2025-07-29T13:22:02Z")

</div>

Is this vulnerability fixed? [Active Directory SSO Disabled for 8.1.17 & 7.9.20 – Inductive Automation Help Center](https://support.inductiveautomation.com/hc/en-us/articles/5979279808397-Active-Directory-SSO-Disabled-for-8-1-17-7-9-20)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [July 29, 2025, 1:25pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/2 "2025-07-29T13:25:07Z")

</div>

No.

---

<div class="post-metadata">

**Author:** ![Brent\_Wassell](https://avatars.discourse-cdn.com/v4/letter/b/f17d59/32.png) [@Brent\_Wassell](https://forum.inductiveautomation.com/u/Brent_Wassell)\
**Post date:** [July 29, 2025, 1:26pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/3 "2025-07-29T13:26:36Z")

</div>

What is the recommended way to handle logins for large companies that use SSO for _everything else_ ?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [July 29, 2025, 1:31pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/4 "2025-07-29T13:31:57Z")

</div>

Identity Providers provide SSO and they seem to be the future at most large/enterprise companies we work with.

---

<div class="post-metadata">

**Author:** ![diamond](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@diamond](https://forum.inductiveautomation.com/u/diamond)\
**Post date:** [July 29, 2025, 1:34pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/5 "2025-07-29T13:34:57Z")

</div>

We use Azure SAML SSO

---

<div class="post-metadata">

**Author:** ![mquinn](https://avatars.discourse-cdn.com/v4/letter/m/cab0a1/32.png) [@mquinn](https://forum.inductiveautomation.com/u/mquinn)\
**Post date:** [July 29, 2025, 1:37pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/6 "2025-07-29T13:37:29Z")

</div>

> [@Kevin.Herron](#):
>
> Identity Providers provide SSO and they seem to be the future at most large/enterprise companies we work with.

Will there be a way to provide a local usersource as failover or a selectable alternative in the event of a internet outage and Azure/Okta/whatever isn't available?

---

<div class="post-metadata">

**Author:** ![Brad\_Fischer](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/brad_fischer/32/84857_2.png) [@Brad\_Fischer](https://forum.inductiveautomation.com/u/Brad_Fischer)\
**Post date:** [July 29, 2025, 1:39pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/7 "2025-07-29T13:39:42Z")

</div>

Implementing a local IdP like Keycloak would provide this. Keycloak can be configured to support an external IdP (Azure / Okta / Duo) as well as one hosted by Keycloak itself.

---

<div class="post-metadata">

**Author:** ![Thomas\_Goetz1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/thomas_goetz1/32/68071_2.png) [@Thomas\_Goetz1](https://forum.inductiveautomation.com/u/Thomas_Goetz1)\
**Post date:** [July 29, 2025, 1:39pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/8 "2025-07-29T13:39:43Z")

</div>

There are external ways to handle this by utilizing an IDP that can broker IDPs, like Keycloak.

---

<div class="post-metadata">

**Author:** ![mquinn](https://avatars.discourse-cdn.com/v4/letter/m/cab0a1/32.png) [@mquinn](https://forum.inductiveautomation.com/u/mquinn)\
**Post date:** [July 29, 2025, 1:43pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/9 "2025-07-29T13:43:44Z")

</div>

Sure, but it'd be really nice to not have to create another highly available system to proxy sso requests at each of our sites. Especially since Ignition has a local user database already integrated. It could do something like what Proxmox does:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/b/2bab79d5903761782ee213360910385b0abd634c.png)  
Where you can just select which of the available login sources you want to use.

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [July 29, 2025, 1:48pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/10 "2025-07-29T13:48:49Z")

</div>

What I'd personally like to see with the built-in IdP is MFA using TOTP codes. (Could do it with email, but I'm not a fan of using email/SMS for MFA)

---

<div class="post-metadata">

**Author:** ![diamond](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@diamond](https://forum.inductiveautomation.com/u/diamond)\
**Post date:** [July 29, 2025, 1:56pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/11 "2025-07-29T13:56:49Z")

</div>

This is very interesting, thank you. It does introduce some complexity to the infrastructure due to the additional dependency. It would have been great if Ignition included this functionality by default.

Btw, adding Kerberos as IdP could be the solution since it happens on premise.

---

<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:** [July 29, 2025, 2:03pm UTC](https://forum.inductiveautomation.com/t/will-sso-be-enabled-with-8-3/109065/12 "2025-07-29T14:03:20Z")

</div>

> [@diamond](#):
>
> Ignition included this functionality by default.

On the contrary, I **like** that IA leaves standardized behaviors to standardized implementations.
