Current situation: FME Flow’s Git integration relies on broad‑scope personal access tokens, which many security policies prohibit.
Why fine‑grained: Fine‑grained PATs were created to align access with what really matters—specific repositories, operations, and lifetimes—enforcing least‑privilege and reducing risk. This will make it easier to implement version control because current organizations like ours don’t allow broad scope.
Request: Add native support for GitHub fine‑grained PATs in FME Flow version control so teams can adopt it while meeting modern security policies.
Open
Support Fine‑Grained GitHub Access Tokens in FME Flow Version Control
+37
+14- Safer
Hi
Are you on GitHub.com or Enterprise Server? And does your security policy require token approval or a maximum token lifetime we'd need to accommodate?
Thanks for posting the idea—upvotes and use cases shared here help us prioritize.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.