# Ignition in iframe - auth

**URL:** <https://forum.inductiveautomation.com/t/ignition-in-iframe-auth/103866>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [March 19, 2025, 7:52am UTC](https://forum.inductiveautomation.com/t/ignition-in-iframe-auth/103866 "2025-03-19T07:52:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin\_ignition](https://avatars.discourse-cdn.com/v4/letter/m/bcef8e/32.png) [@martin\_ignition](https://forum.inductiveautomation.com/u/martin_ignition)\
**Post date:** [March 19, 2025, 7:52am UTC](https://forum.inductiveautomation.com/t/ignition-in-iframe-auth/103866/1 "2025-03-19T07:52:51Z")

</div>

Hello,

we are (planning to) embed perspective views in iframes i our webpages. We are using entra/openid for authentication.  
Ideally, the user should not have to log in again in the iframe, but use the entra "session" of the parent.

This works, when ignition shares a hostname with the website, when all the headers are set correctly, when cookie policies are set correctly in the client's browser and when the moon is visible on a cool morning in spring.

Do you see any other way to "transport" the user authentication? Is it possible to write an endpoint via webdev that accepts the entra token and creates a perspective session, for example?

Alternatively, is it possible to accept roles as query params in perspective screens and set these roles for the currently logged in user? That way we could write a proxy that transforms the token into query params.

Best regards, Martin

---

<div class="post-metadata">

**Author:** ![martin\_ignition](https://avatars.discourse-cdn.com/v4/letter/m/bcef8e/32.png) [@martin\_ignition](https://forum.inductiveautomation.com/u/martin_ignition)\
**Post date:** [March 19, 2025, 3:30pm UTC](https://forum.inductiveautomation.com/t/ignition-in-iframe-auth/103866/2 "2025-03-19T15:30:50Z")

</div>

I've just found the [LinuxAuthentication-module](https://github.com/IgnitionModuleDevelopmentCommunity/LinuxAuthentication/tree/master).

Would it be possible to do something similar? I.e. instead of the login screen, check whether a certain cookie is set and use that cookie (which will be an auth token) to treat it as a user source?