Secure GitLab CI/CD workflows using OIDC JWT on a DevSecOps platform

This post introduces the evolution of JWT support in GitLab CI/CD, moving from initial JWT (V1) for Hashicorp Vault integration to OIDC JWT (V2) for broader cloud provider integration, and finally to a production-ready OIDC token. It details the opt-in mechanism for JWT token usage to minimize exposure and the importance of the audience claim for security. The post also announces breaking changes and backward compatibility plans leading up to GitLab 16.0, where only the secured OIDC token will be available. It provides guidance on configuring pipelines to use the `id_token` keyword and enabling the 'Limit JSON Web Token (JWT) access' setting.