[Request for Feedback] Expiration policies and lifetime changes for PATs #141929
Replies: 4 comments 6 replies
-
I'm having some trouble creating a token without an expiration. In the org i've unchecked "Fine-grained personal access tokens must expire". |
Beta Was this translation helpful? Give feedback.
-
I'm trying to enable this policy in the enterprise. After enabling this option, if unexpected API call failures are discovered and the policy is temporarily disabled, will the call failures recur? |
Beta Was this translation helpful? Give feedback.
-
We would like to disable the classic PATs for our org, but unfortunately we need read Packages (maven) support only. Is there any option to limit a classic PAT for an org to allow only specific scopes and disable all other scopes? |
Beta Was this translation helpful? Give feedback.
-
import memoize from '@github/memoize' function getEnabledFeaturesSet(): Set { const featuresSet = export function getEnabledFeatures(): string[] { export function isFeatureEnabled(name: string): boolean { //exported to allow mocking in tests export {featureFlag} function isStorybook() { |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We've launched the ability to restrict PAT lifetimes if the PAT is going to be used against your organization or resource. As part of this change, we've also allowed fine-grained PATs to be created without an expiration.
The default policy for all orgs and enterprises retains the existing 366 day maximum for fine-grained PATs.
Please check out the changelog for more details, and let us know what you think!
Known issues
Beta Was this translation helpful? Give feedback.
All reactions