Session headers

Introduction

In a customer environment quite often extra HTTP headers are sent with each initial request. These headers contain context information, such as the social security number (BSN) of the user. By enabling custom headers it is possible to receive headers, send them and possibly use them in the profile by a new service AQ_GetHeaders.

To be able to process custom headers they have to be saved/stored in the configuration. Only then it is possible to sending them to another systems you are calling. This functionality is possible for both SOAP and REST.

Picture

In the next figure we depict the functionality.

The box rectangle is the Blueriq runtime. It is possible to call such runtime by a flow, a BAA(R)S or a Function Flow. When sending headers you are able to send them to a system based on SOAP or REST. Note that the Function Flow is working via REST. By using the AQ_GetHeader it is possible to receive information from the header and use it in the profile.

Static headers

It is also possible to configure headers as static key-value pairs for both SOAP and REST. These headers can be configured globally for all SOAP and REST requests, or on a per-connection basis.

Configuration

To configure custom headers, please refer to Custom HTTP headers setup.