# Allow custom formats for Subject claim in OIDC Token

**URL:** <https://forum.buildkite.community/t/allow-custom-formats-for-subject-claim-in-oidc-token/3725>\
**Category:** Features Requests\
**Created:** [June 4, 2024, 11:33pm UTC](https://forum.buildkite.community/t/allow-custom-formats-for-subject-claim-in-oidc-token/3725 "2024-06-04T23:33:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hobbseltoff](https://avatars.discourse-cdn.com/v4/letter/h/848f3c/32.png) [@hobbseltoff](https://forum.buildkite.community/u/hobbseltoff)\
**Post date:** [June 4, 2024, 11:33pm UTC](https://forum.buildkite.community/t/allow-custom-formats-for-subject-claim-in-oidc-token/3725/1 "2024-06-04T23:33:00Z")

</div>

Currently, when using the `oidc request-token` function of `buildkite-agent` the `sub` claim of the generated token contains a static format. This causes an issue when trying to use federated credentials with platforms that require exact matches of the claim and don’t support wildcards (like Azure).

It would be extremely helpful to be able to customize what fields the `sub` claim contains.

---

<div class="post-metadata">

**Author:** ![Priya](https://avatars.discourse-cdn.com/v4/letter/p/eada6e/32.png) [@Priya](https://forum.buildkite.community/u/Priya)\
**Post date:** [June 5, 2024, 2:06am UTC](https://forum.buildkite.community/t/allow-custom-formats-for-subject-claim-in-oidc-token/3725/2 "2024-06-05T02:06:47Z")

</div>

Hey Hobbseltoff 👋

Welcome to Buildkite community!

You’re right, currently the OIDC subject format is static. I’m raising this with our internal team as a feature request to investigate the impact associated with this change and advice on the priority.

Will keep you posted as soon as we hear from them!

Cheers,  
Priya