# Switching to a different project without signing in again

**URL:** <https://forum.inductiveautomation.com/t/switching-to-a-different-project-without-signing-in-again/42626>\
**Category:** Ignition\
**Created:** [January 26, 2021, 5:22pm UTC](https://forum.inductiveautomation.com/t/switching-to-a-different-project-without-signing-in-again/42626 "2021-01-26T17:22:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chandler](https://avatars.discourse-cdn.com/v4/letter/c/e9a140/32.png) [@chandler](https://forum.inductiveautomation.com/u/chandler)\
**Post date:** [January 26, 2021, 5:22pm UTC](https://forum.inductiveautomation.com/t/switching-to-a-different-project-without-signing-in-again/42626/1 "2021-01-26T17:22:39Z")

</div>

Hi,

I am trying to navigation to a different perspective project by clicking a button in the current perspective project, but this requires you to sign in twice. Is there a way to navigate to a different project (potentially on a different gateway) without re-authenticating?

I have tried using the Menu Tree component with the URLs in the target property, as well as navigation events on buttons, but both require reauthentication.

Thanks

---

<div class="post-metadata">

**Author:** ![rcrownover](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rcrownover/32/17805_2.png) [@rcrownover](https://forum.inductiveautomation.com/u/rcrownover)\
**Post date:** [January 27, 2021, 3:22pm UTC](https://forum.inductiveautomation.com/t/switching-to-a-different-project-without-signing-in-again/42626/2 "2021-01-27T15:22:12Z")

</div>

I believe the **easiest** solution here is to use a federated identity provider. Then the authentication you provided for the session with project A would be used automatically for project B.

Our architectures only ever use a single Perspective project, and we separate them logically within that project to mitigate this kind of issue (among others). So others may already have some “hacks” that could get you there. At the end of the day, my _guess_ is that there’s an inherent security design decision baked into you not being able to do this easily (if at all) without using federated identity.

If you think about it, if a user opens a page from 2 different Perspective projects (even on the same gateway) they’re going to have 2 sessions, because each project will have its own session properties, etc… Authentication gets you authentication for a session. So when you navigate from `gatewayurl.com/../../projectA/page1` to `gatewayurl.com/../../projectB/page1` you’re creating a new session, which will always require authentication. Unless you use an identity provider. They may still need to click a “login” button, but no user/password entry.