AVEVA™ PI System™ Feedback Portal

Welcome to our new 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.

Add a new idea Subscribe
Status No Status
Product AVEVA™ Adapters
Categories General
Created by Gabriel Verreault
Created on Aug 16, 2022

RELATED IDEAS

Allow remote configuration

Adapters are currently only listening on localhost (127.0.0.1) causing them to be only accessible locally. For docker containers, they can only be accessed from within the container or directly on the host (with the --network host switch which results in not containerizing the container's networking) but they cannot be accessed for elsewhere (not able to bind them to 0.0.0.0) This makes adapter management very difficult in distributed environment.
  • Attach files
  • sahilp
    Reply
    |     Sep 9, 2022

    From a cyber secure by design perspective, this should be implemented natively within the Adapter itself, and not be managed by customer workarounds

    Workarounds are outside of the control of Aveva, and may be implemented by customers in non-ideal ways. The exploits of those workarounds may none-the-less damage Aveva reputation (undeservedly)

  • Gabriel Verreault
    Reply
    |     Aug 16, 2022
    Would require https://feedback.osisoft.com/forums/930280-pi-adapters/suggestions/43629426-support-https-instead-of-http-only to be completed first
  • Fred_EYRAUD
    Reply
    |     Aug 16, 2022
    Hello, We are testing PI Adapter on windows and have find a workaround by redirecting ports: netsh interface portproxy add v4tov4 listenport= listenaddress= connectport= connectaddress=127.0.0.1 This working fine for us.