# IDP token expires but designer remains connected/authenticated

**URL:** <https://forum.inductiveautomation.com/t/idp-token-expires-but-designer-remains-connected-authenticated/114831>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [April 1, 2026, 2:11pm UTC](https://forum.inductiveautomation.com/t/idp-token-expires-but-designer-remains-connected-authenticated/114831 "2026-04-01T14:11:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![hunterdg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hunterdg/32/67774_2.png) [@hunterdg](https://forum.inductiveautomation.com/u/hunterdg)\
**Post date:** [April 1, 2026, 2:11pm UTC](https://forum.inductiveautomation.com/t/idp-token-expires-but-designer-remains-connected-authenticated/114831/1 "2026-04-01T14:11:49Z")

</div>

Having an issue where perspective and gateway web page auth sessions silently timeout after some time until manually refreshed (presumably an IDP-specific issue). The only obvious symptoms are that data stops updating (perspective sessions) or a gateway web page browser tab goes to sleep/must re-auth when resumed. We're working on fixing this...

**However** Designer does not suffer from this problem. Just curious what the underlying mechanism might be that allows Designer to remain authenticated.

---

<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:** [April 1, 2026, 9:04pm UTC](https://forum.inductiveautomation.com/t/idp-token-expires-but-designer-remains-connected-authenticated/114831/2 "2026-04-01T21:04:43Z")

</div>

The designer itself is not a browser. Your browsers are likely to blame.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 1, 2026, 9:16pm UTC](https://forum.inductiveautomation.com/t/idp-token-expires-but-designer-remains-connected-authenticated/114831/3 "2026-04-01T21:16:49Z")

</div>

I read this differently - the designer is in the wrong and browsers are correct.

The likely answer is that the designer was built under a lot of assumptions from the "user source" model of the world that may not have been re-examined.  
Is this in 8.1 or 8.3? 8.3 has some significant changes to how the designer/Vision client keep their session bookkeeping on the gateway.

---

<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:** [April 1, 2026, 9:40pm UTC](https://forum.inductiveautomation.com/t/idp-token-expires-but-designer-remains-connected-authenticated/114831/4 "2026-04-01T21:40:40Z")

</div>

Ah, right there in the title. An expired token **should** disconnect.

---

<div class="post-metadata">

**Author:** ![hunterdg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hunterdg/32/67774_2.png) [@hunterdg](https://forum.inductiveautomation.com/u/hunterdg)\
**Post date:** [April 1, 2026, 10:14pm UTC](https://forum.inductiveautomation.com/t/idp-token-expires-but-designer-remains-connected-authenticated/114831/5 "2026-04-01T22:14:24Z")

</div>

yes, perhaps I could've clarified, we're working to fix the browser/workstation silent timeouts (presumably in Azure Entra IDP - client has agressive 12-hour timeouts in for regular 365 stuff, assuming even more agressive for SCADA), but I'd assume Designer _ **should** _ also be affected.

Ignition 8.1.48 - I figure as you suggest it's more likely by accident than design, but curious nontheless/thought worthy of posting.