Managing Automatic Session Timeouts in PI Coresight (PI Vision)

Many organizations require session inactivity timeouts as part of their security policies. A common question from PI Coresight (now known as PI Vision) administrators is: Can we configure automatic session termination after a period of inactivity?

Current State: No Native Inactivity Timeout

As of now, PI Coresight does not natively support automatic session timeouts triggered by user inactivity. This means that, out of the box, Coresight will not automatically log out users who are idle for extended periods.

The Future: OpenID Connect and Identity Provider-Based Timeouts

OSIsoft is actively developing support for OpenID Connect (OIDC), a modern authentication protocol that enables claims-based authentication. Once this functionality is released, you’ll be able to:

• Integrate Coresight with enterprise identity providers, such as Active Directory Federation Services (ADFS), Azure Active Directory, or other OIDC-compatible platforms.
• Manage session timeout (and other security policies) directly in your identity provider settings, instead of in PI Coresight alone.

With OIDC-enabled authentication, your organization will gain more granular control over session duration, idle timeout, and logout policies — all enforced centrally and consistently across applications.

What Should You Do Now?

• Monitor OSIsoft’s Release Notes: Keep an eye on the official PI Vision release notes to know when OIDC support becomes available.
• Plan for Integration: If your organization already uses an OIDC-capable identity provider, plan for the eventual rollout by aligning your compliance and IT teams.
• Prepare for Configuration: Once released, updating Coresight to use OIDC will allow you to configure session timeout settings within your identity provider, ensuring your compliance requirements are met.

Summary Table

---

Configuring automatic inactivity timeouts in Coresight is on the roadmap via OpenID Connect support. In the meantime, stay current with OSIsoft’s development, and consider preparing your infrastructure for OIDC to take advantage of more secure and compliant authentication flows in the near future.