Skip to Main Content
AVEVA™ Data Hub 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 Data Hub. For links to our other feedback portals, please see RESOURCES below.

Status Tell us more
Categories Security
Created by Guest
Created on Aug 18, 2022

PItoOCS installation should support Device Codes in addition to manual OCS login

As a PI System Administrator installing the PI to OCS agent, I need an alternate way to establish a secure connection instead of opening a web page and manually entering my credentials because our company bans java script or there is no web browser available on the machine. Because of this, I can never get the install kit to finish. Currently for a user or client to log in, either a clientid/secret or interactive user log in with an Identity Provider must be used in order to obtain a access token. We would like to use a device code to obtain an access token as an alternate to the other methods available.
  • ADMIN RESPONSE
    Aug 18, 2022
    We are interested in learning more about your use case and requirements for support of Device Codes for PI to OCS installation.
  • Attach files