Missing auth token when using external data sources

[maurice-freitag]

We're using external data sources. The OPAL clients get their initial config from the server, which redirects them to our service. The initial request to our service correctly contains the auth token (received via /token request to the OPAL server) in the query string. For every subsequent request, i.e. for loading the initial data and after trigger data updates, the clients don't seem to send their token to the data source service, neither in the query string, nor as authorization headers.

Are we missing any configuration options that could enable this? Is this fixed in a newer version?

OPAL version

• Version: [0.6.0]