# Configurable OIDC Provider **URL:** \ **Category:** Features Requests\ **Created:** [April 16, 2025, 6:08pm UTC](https://forum.buildkite.community/t/configurable-oidc-provider/4348 "2025-04-16T18:08:45Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![amarquez](https://avatars.discourse-cdn.com/v4/letter/a/59ef9b/32.png) [@amarquez](https://forum.buildkite.community/u/amarquez)\ **Post date:** [April 16, 2025, 6:08pm UTC](https://forum.buildkite.community/t/configurable-oidc-provider/4348/1 "2025-04-16T18:08:45Z")
### Proposed Change We suggest introducing the capability to configure the OIDC provider used for generating Buildkite OIDC tokens. This change aims to mirror the flexibility provided by Terraform Enterprise, which allows users to [setup and configure their own AWS OIDC Identity provider](https://developer.hashicorp.com/terraform/enterprise/workspaces/dynamic-provider-credentials/aws-configuration#configure-aws). ### Rationale for the Change Currently, all Buildkite customers rely on the same OIDC provider. This commonality increases the risk of incorrectly configured IAM role trust relationships that do not enforce organization-specific constraints, making it possible for any Buildkite customer to assume such roles erroneously. While it’s conceivable to incorporate condition logic within your trust policy to scrutinize data from the OIDC claims — particularly the `organization_id` — to mitigate this security loophole, the approach isn’t foolproof. Specifically, if multiple individuals are permitted to define IAM roles and trust policies, there’s a risk that the necessary conditional logic might be overlooked. ---
**Author:** ![ivanna](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/ivanna/32/1410_2.png) [@ivanna](https://forum.buildkite.community/u/ivanna)\ **Post date:** [April 16, 2025, 9:53pm UTC](https://forum.buildkite.community/t/configurable-oidc-provider/4348/2 "2025-04-16T21:53:43Z")
Hey! Thanks for the feedback. Based on the suggestions above and the internal chat we have shared the feedback request with the product folks ! Thank you !