Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status No status
Categories Notifications
Created by Guest
Created on Aug 20, 2022

Allow additional authentication types for web service delivery endpoints in PI Notifications

Allow for additional authentication types to be added for web service delivery endpoints. Currently, the only available options are Windows, Anonymous, and Basic.
  • Attach files
  • glassro0
    Reply
    |
    Sep 25, 2024

    My company is also requiring OAuth / Bearer authentication for PI Notification API calls.

  • Alejandro Molano
    Reply
    |
    Jan 24, 2024

    This is a very popular integration method between PI and ServiceNow, providing OAUTH authentication (or other modern and secure alternatives) is critical considering some cybersecurity teams are not allowing basic authentication in their organizations.

  • MichaelG
    Reply
    |
    Sep 25, 2023

    claims based authentication using tokens

  • Kenneth Barber
    Reply
    |
    Aug 20, 2022
    What additional authentication types did you have in mind?
  • Guest
    Reply
    |
    Aug 20, 2022
    Hi @Kenneth Barber, I have tech support case 00883545 where the customer was hoping to use Bearer authentication for the web service delivery endpoint. The Notifications service would need to request a token from an external token generator and supply it in the authentication headers. This could be useful for communicating with modern REST APIs that require more secure authentication.