Validity of OIDC token is too short for meaningful usage of Identity Federation #190629
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Configuration
Discussion Details
We’re currently evaluating the use of GitHub’s OIDC provider for identity federation with SAP Cloud Identity Services.
One issue we’ve run into is that the JWT token issued by GitHub appears to have a lifetime of only ~5 minutes. This short expiry seems to carry through SAP Cloud Identity Services as well, and it’s causing failures in workflows that run longer than that duration.
Related issues:
cloudfoundry/terraform-provider-cloudfoundry#469
SAP/terraform-provider-btp#1450
Is the JWT token lifetime configurable? For reference, GitLab allows customising ID token duration:
https://docs.gitlab.com/administration/auth/oidc/#configure-a-custom-duration-for-id-tokens
Right now, the short TTL is a blocker for many of our use cases, so we’re looking for a way to extend the token validity or otherwise handle longer-running workflows.
Beta Was this translation helpful? Give feedback.
All reactions