Skip to content

Document the managed identity token lifetime for Entra issuers - #773

Merged
rgarcia merged 2 commits into
mainfrom
hypeship/wif-managed-identity-lifetime
Nov 20, 2026
Merged

rgarcia merged 2 commits into
mainfrom
hypeship/wif-managed-identity-lifetime

Conversation

@rgarcia

@rgarcia rgarcia commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Azure managed identity tokens have exp minus iat of about 86,700 seconds, a little over 24 hours. The issuer limit was 24 hours, so managed identity could not be used at all. kernel/kernel#5637 raised the limit to 48 hours for every issuer type; it's deployed to production.

  • Microsoft Entra guide: the step is now titled "Adjust the issuer for cached or long-lived tokens" and tells managed identity users to set Maximum token lifetime (hours) to 25, explaining why every token is refused without it. The details list says the limit goes up to 48 hours.
  • Custom OIDC guide: the issuer field table gives the maximum as 48 hours instead of 24.
  • Reference: max_lifetime_seconds is 1 to 172,800, with 90,000 (25 hours) recommended for Azure managed identity, and the limits table says up to 172,800.

@mintlify

mintlify Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
Kernel 🟢 Ready View Preview Nov 20, 2026, 7:25 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@masnwilliams masnwilliams left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The numbers check out: managed identity tokens run about 86,700 s, so a 25 h limit (90,000 s) covers them, and the 172,800 s cap matches kernel/kernel#5637, which is now deployed to production.

Needs fixing

info/workload-identity/custom-oidc.mdx:34 still gives the old cap for the same issuer field:

The default is 1 hour and the maximum is 24.

The cap was raised for every issuer type, not just Entra. If this line stays, the docs say 24 here and 48 everywhere else. A custom OIDC user whose provider issues tokens longer than 24 hours would conclude they can't use KERNEL.

-| **Maximum token lifetime (hours)** | Tokens whose `exp` minus `iat` exceeds this are refused. The default is 1 hour and the maximum is 24. |
+| **Maximum token lifetime (hours)** | Tokens whose `exp` minus `iat` exceeds this are refused. The default is 1 hour and the maximum is 48. |

I checked the other workload identity pages, and this is the only other place that still states the old cap.

Optional

  • The step title "Allow token reuse if your workload caches tokens" doesn't hint at the new lifetime requirement, which applies to every managed identity user. Something like "Adjust the issuer for cached or long-lived tokens" would make it easier to find.
  • reference.mdx: "need at least 86,700" turns an approximate value into a hard minimum. "Set 90,000" would match the guide's 25 hours.

Approve once the custom-oidc.mdx line is updated.

@masnwilliams masnwilliams left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The custom OIDC cap now reads 48, matching the rest of the docs, and the step title and reference wording read well. LGTM.

@rgarcia
rgarcia merged commit 39af6cc into main Nov 20, 2026
3 checks passed
@rgarcia
rgarcia deleted the hypeship/wif-managed-identity-lifetime branch November 20, 2026 19:31

This branch was successfully deployed

1 active deployment
staging — c9de297d Deployed Nov 20, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants