Resolves Issue #441: Permit URL parameters in place of required Headers

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

• [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this introduce a breaking change?

• [NO]

What is the current behavior?

Current OSDU-Auth enforces the following Headers to be included in GCZ Provider requests:

• data-partition-id
• Authorization

While this pattern is a seamless 1-to-1 mapping with requirements from OSDU security, it blocks compatibility with clients (like ArcGIS Online, or ArcGIS Enterprise Portal) that have limited control over customizing Headers for an attached Feature Service (like GCZ).

What is the new/expected behavior?

Extend auth support into the URL Parameters, accepting and converting the required values into the required headers for OSDU.

Acceptance Criteria

• Optional access_token and data_partition_id URL query parameters are supported by the Provider.
• If Headers are missing from an incoming request, the URL parameters are scanned as a second measure to identify required values.
• If both Headers and URL Parameters are set, Headers take precedence.
• Documentation updated to outline optional URL Parameter support.

Have you added/updated Unit Tests and Integration Tests?

No

Any other useful information