PI Server

← User Feedback for OSIsoft Products and Services

Welcome to the PI Server feedback page!

We created this forum to hear your ideas, feature suggestions and feedback on PI Server. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.

Please note that your ideas and comments posted here are visible to all other users.

For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.

How can we improve the PI Server?

Enter your idea

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

Enable headers for SOAP and REST Web Service Notifications

The feature added in 2017 R2 was for authentication of the SOAP payload, not for managing headers within the payload. PI remains unusable as a secure source of data for Maximo without it because you can't configure a MAXAUTH header.

There's no way to configure headers for Notification Rules associated with a PI AF Services v2017 SP1 Elements with a SOAP or REST Web Service Endpoint. Authenticated web services, such as our company's Maximo's meter data inbound service requires a MAXAUTH header with a base64-encrypted username:password string. As a result, you can't use PI as a source of data for Maximo's condition-based maintenance triggers and automated asset meter reading updates, if Maximo uses authentication on its web services. That's a fairly common scenario with a high rate of return on the PI-Maximo integration efforts for a lot of customers.

The feature added in 2017 R2 was for authentication of the SOAP payload, not for managing headers within the payload. PI remains unusable as a secure source of data for Maximo without it because you can't configure a MAXAUTH header.

There's no way to configure headers for Notification Rules associated with a PI AF Services v2017 SP1 Elements with a SOAP or REST Web Service Endpoint. Authenticated web services, such as our company's Maximo's meter data inbound service requires a MAXAUTH header with a base64-encrypted username:password string. As a result, you can't use PI as a source of data for…

22 votes

Sign in
prestine
Sign in with OSIsoft
Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

4 comments · Notifications · Flag idea as inappropriate… · Delete… · Admin →

STARTED / IN DEVELOPMENT · AdminStephen Kwan (Product Manager, OSIsoft) responded

HTTP headers for REST web service delivery end point was added in the PI AF 2018 SP2 release.

HTTP headers for SOAP web service delivery end point is currently in the backlog only.

Don't see your idea?

PI Server

How can we improve the PI Server?

Enable headers for SOAP and REST Web Service Notifications

Feedback

PI Server

Feedback and Knowledge Base

Searching…

Give feedback

OSIsoft

Your password has been reset