Fine-grained PAT: target_name URL parameter visually pre-fills Resource Owner but token is created under personal account #188111
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.
-
Select Topic Area
Bug
Body
Hi team! 👋
I ran into an issue with the fine-grained PAT template URLs feature and wanted to share my findings — hopefully this helps!
If you know any workaround to get around this, I’d be glad to hear it.
Description
When navigating to the fine-grained PAT creation page with a pre-filled target_name parameter, the Resource Owner dropdown visually displays the specified organization, but the token is actually created under the personal account.
Steps to reproduce
Expected behavior
Token should be created with Resource Owner = <ORG_NAME>, matching the visual state of the dropdown.
Actual behavior
The target_name parameter updates the dropdown's visual/display state but does not initialize the underlying form state. The token is created under the personal account.
Workaround
After navigating via the prefill URL, manually re-select the organization in the Resource Owner dropdown (switch to another value, then back to the org). This forces the form state to sync with the visual state. Only then generate the token.
Environment
References
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#pre-filling-fine-grained-personal-access-token-details-using-url-parameters
Thanks for looking into this! Great feature overall — just this small hiccup with the pre-fill. ���
Beta Was this translation helpful? Give feedback.
All reactions