# Passing customer headers through an auth flow

**URL:** <https://devforum.okta.com/t/passing-customer-headers-through-an-auth-flow/32062>\
**Category:** OAuth/OIDC\
**Tags:** spring, java\
**Created:** [February 20, 2025, 4:00pm UTC](https://devforum.okta.com/t/passing-customer-headers-through-an-auth-flow/32062 "2025-02-20T16:00:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![stevemaring](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/stevemaring/32/5548_2.png) [@stevemaring](https://devforum.okta.com/u/stevemaring)\
**Post date:** [February 20, 2025, 4:00pm UTC](https://devforum.okta.com/t/passing-customer-headers-through-an-auth-flow/32062/1 "2025-02-20T16:00:48Z")

</div>

I am using okta-spring-boot-starter 3.0.7 with spring-boot-starter-parent 3.4.2. The auth works fine.

However, we would like to do a blue/green deployment within our application to test release candidates prior to switching them to be the live deployment. In order to effect the test, we need either a query-param or a request header value to make it through the Okta OCID login. For instance, if the original request, prior to authentication, has a request header of zone=blue then we process the request on the blue zone servers. We would then save that zone choice in the session and ensure each subsequent request contains that header.

So, my questions are:

1. Is there a way to pass a customer request header through the auth flow?
2. Is there a better way to achieve our goal?

Our deployment is in AWS.

---

<div class="post-metadata">

**Author:** ![stevemaring](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/stevemaring/32/5548_2.png) [@stevemaring](https://devforum.okta.com/u/stevemaring)\
**Post date:** [February 21, 2025, 12:27pm UTC](https://devforum.okta.com/t/passing-customer-headers-through-an-auth-flow/32062/2 "2025-02-21T12:27:05Z")

</div>

I just noticed that query params on the original request seem to be making it through the auth flow. I will try to process the query params within the AWS ALB and see how that goes.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/oktadev/original/1X/589c4c5f80de422d01f47cee7185a7fb8227835c.png) [@system](https://devforum.okta.com/u/system)\
**Post date:** [March 23, 2025, 12:27pm UTC](https://devforum.okta.com/t/passing-customer-headers-through-an-auth-flow/32062/3 "2025-03-23T12:27:16Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.