Enable authentication headers for SOAP and REST Web Service Notifications
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.
This is in PI Server 2017 R2, available now on https://techsupport.osisoft.com/
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.
The request isn't specific to Maximo - enabling a standard HTTP authorization in the SOAP header will allow Maxmio's web service to accept the payload.
Mike Zboray commented
Note that in 2017 R2 we are planning on including basic authentication via the standard HTTP Authorization header. The specific ask here (a custom header for authentication that is understood only by Maximo) will have to wait for a future version.
This feature is very much needed. We need to be able to specify the Message Header from PI Notifications when calling with POST a REST web service