# OIDC: Passing some kind of state to the OpenID IDP

**URL:** <https://devforum.okta.com/t/oidc-passing-some-kind-of-state-to-the-openid-idp/20812>\
**Category:** Questions\
**Created:** [May 30, 2022, 11:05am UTC](https://devforum.okta.com/t/oidc-passing-some-kind-of-state-to-the-openid-idp/20812 "2022-05-30T11:05:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hc289](https://avatars.discourse-cdn.com/v4/letter/h/e68b1a/32.png) [@hc289](https://devforum.okta.com/u/hc289)\
**Post date:** [May 30, 2022, 11:05am UTC](https://devforum.okta.com/t/oidc-passing-some-kind-of-state-to-the-openid-idp/20812/1 "2022-05-30T11:05:09Z")

</div>

Hi all,

I have a situation where my app (The RP) wants to pass a value to the IDP as part of the authentication request. So instead of just saying in the oauth request (for example):

```auto
idp=idp123&response_type=token

```

I want to be able to say

```auto
idp=idp123&response_type=token&my_special_field=JWTContentsHere

```

And I want Okta to forward that on to the IDP. I notice that it randomises `state` and `nonce` before passing them on.

I feel like this might be what RelayState does in SAML - I’m looking for the OIDC equivalent.

The best I’ve found so far is to throw my JWT into `login_hint` - any downsides to that? I self-develop the OID IDP in this case so it’s not an out of the box solution. I know that sounds like horror but it’s necessary for the niche flow I’m working on, trust me 😉

Cheers,

HC

---

<div class="post-metadata">

**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\
**Post date:** [February 12, 2024, 7:48pm UTC](https://devforum.okta.com/t/oidc-passing-some-kind-of-state-to-the-openid-idp/20812/2 "2024-02-12T19:48:44Z")

</div>