Perspective 8.1.45 – Custom Login with Ignition Authentication in the Background?

Hi everyone,

I'm currently working on an Ignition Perspective application (version 8.1.45) used on our manufacturing shop floor, and I'm looking for some guidance regarding authentication.

We're experiencing an issue with the default Ignition login screen. When the login page remains open for an extended period, it sometimes becomes unresponsive or the authentication process stops working properly.

This is a fairly common scenario in our environment. An operator may open the login screen, step away to perform another task, and then return to scan their employee badge. At that point, the login process no longer works, and they need to refresh the page before trying again.

Because of this, I'm considering implementing a custom login screen within our Perspective application, where operators could authenticate using their badge number or username, with a PIN if required.

However, I have a question about how this would integrate with Ignition's authentication system.

Is there a supported way to authenticate a user through a custom Perspective login screen while still establishing a valid Ignition authenticated session in the background?

We rely on Ignition's authenticated username for auditing, logging, and tracking operator actions, so I want to make sure we preserve that functionality rather than simply validating credentials in our application and storing the username in a custom session property.

Ideally, I'd like to:

  • Use our own login interface within Perspective.

  • Allow operators to authenticate using their badge number or username.

  • Establish a valid Ignition authentication context so the authenticated user is recognized by the platform.

  • Continue using the authenticated username for auditing and logging.

  • Avoid the issue where the default login screen stops working after being left open for several minutes.

Has anyone implemented something similar in Perspective 8.1.x? Is this possible using the existing authentication framework, or is there a recommended alternative approach?

Any suggestions or guidance would be greatly appreciated.

Thanks in advance!

The issue is leaving the IdP page open long enough for the token to expire, not that it just stops working because of a flaw.

You might can change your login scheme a bit where you turn off the auto-redirect option. This should make the user land on the sign-in page that does not timeout, then they would click the login button when ready.

There are more in-depth options like using a third-party IdP utilizing SAML, etc.

Depending on your setup, you might could use system.perspective.authenticationChallenge() too. It has an optional timeout argument.

Create your own SAML identity provider outside Ignition.

Otherwise, no.

We do this and it works very well. I wasn't involved in implementing it, we had the folks over kanoa help us implement it.