Repository navigation
Document the managed identity token lifetime for Entra issuers - #773
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
masnwilliams
left a comment
There was a problem hiding this comment.
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
left a comment
There was a problem hiding this comment.
The custom OIDC cap now reads 48, matching the rest of the docs, and the step title and reference wording read well. LGTM.
Summary
Azure managed identity tokens have
expminusiatof 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.max_lifetime_secondsis 1 to 172,800, with 90,000 (25 hours) recommended for Azure managed identity, and the limits table says up to 172,800.