# Synchronize login across projects/sessions

**URL:** <https://forum.inductiveautomation.com/t/synchronize-login-across-projects-sessions/65855>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [October 31, 2022, 2:27am UTC](https://forum.inductiveautomation.com/t/synchronize-login-across-projects-sessions/65855 "2022-10-31T02:27:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jalal\_Elwazze](https://avatars.discourse-cdn.com/v4/letter/j/a88e4f/32.png) [@Jalal\_Elwazze](https://forum.inductiveautomation.com/u/Jalal_Elwazze)\
**Post date:** [October 31, 2022, 2:27am UTC](https://forum.inductiveautomation.com/t/synchronize-login-across-projects-sessions/65855/1 "2022-10-31T02:27:59Z")

</div>

Hi All,

I've been working on a perspective application that has been growing in size (single site with multiple facilities). I'm at a point where it would be convenient to start splitting it out into multiple sub-projects using inheritance.

The problem:

1. Users are authenticated against an ignition IDP from our site active directory user source.
2. When a user moves from one project to another they are required to re-authenticate. Since the user has no concept of projects they are left wondering why they have to sign in so many times.

The desired fix:

1. Have users sign in once from any project and propagate their authentication through every other project they click through.
2. Since I cannot set up a new identity provider to use SSO I am looking for a way to accomplish this using the active directory source.

Is this possible in perspective?

---

<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:** [October 31, 2022, 4:13pm UTC](https://forum.inductiveautomation.com/t/synchronize-login-across-projects-sessions/65855/2 "2022-10-31T16:13:18Z")

</div>

Disclaimer: I'm by no means an expert at IdP related stuff.

No, or at least not currently. At most you could have a 'sticky' session, where you would be redirected to login then immediately redirect back because the IdP "knows" you; this behavior is pretty fundamental to the way identity providers and federated identity works. Your login request is 'associated' with a particular resource, and once you succeed at authenticating, you are granted access to that one particular project.

Better tools around organization of project resources might be a more feasible option here than trying to change how IdPs work; even if we changed Ignition's IdP, it wouldn't help customers using third party IdPs.

---

<div class="post-metadata">

**Author:** ![slugrin](https://avatars.discourse-cdn.com/v4/letter/s/f14d63/32.png) [@slugrin](https://forum.inductiveautomation.com/u/slugrin)\
**Post date:** [January 7, 2026, 2:38pm UTC](https://forum.inductiveautomation.com/t/synchronize-login-across-projects-sessions/65855/3 "2026-01-07T14:38:31Z")

</div>

Hi, I'm trying to solve the same problem as you.  
I have several projects associated with the same gateway, but every time I switch projects, I have to log in again.  
Were you able to resolve it?  
Regards.