transformers - 💡(How to fix) Fix Orgs should be able to agree to 3rd party use agreements so their members can access 3rd party models [4 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
huggingface/transformers#44955Fetched 2026-04-08 01:21:34
View on GitHub
Comments
4
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
commented ×4labeled ×1
RAW_BUFFERClick to expand / collapse

Feature request

for CI / CD the only way to get a sane workflow is to make a fake single user that the whole company uses to access the 3rd party resources. This undercuts your enterprise options and the idea that all users should log in as themselves. I know it's probably some legal hangup, but as is you are undercutting your enterprise offerings and your security.

Motivation

I want to have my org be able to use hugging face in our CI/CD platforms. but I can't ask all our users to sign in and agree to a constantly increasing number of agreements. So instead I make a fake account that everyone shares. This is bad for you and me.

Your contribution

I would use your product if you made it. I would pay money for the team or enterprise for this feature, where currently there is no incentive to do that.

extent analysis

Fix Plan

To address the issue, we can implement a service account feature for CI/CD workflows. This will allow organizations to create a single, shared account for accessing 3rd party resources without compromising security.

Implementation Steps

  • Create a new service account type in the user management system
  • Assign a unique token to each service account for authentication
  • Update the CI/CD workflow to use the service account token for accessing 3rd party resources
  • Implement role-based access control to restrict service account permissions

Example Code

# Create a service account
service_account = {
    'id': 'ci-cd-service-account',
    'token': 'unique-token',
    'permissions': ['read', 'write']
}

# Use the service account token in the CI/CD workflow
import requests
headers = {
    'Authorization': f'Bearer {service_account["token"]}'
}
response = requests.get('https://example.com/3rd-party-resource', headers=headers)

Verification

To verify that the fix worked, test the CI/CD workflow with the service account token and ensure that it can access the 3rd party resources without requiring individual user authentication.

Extra Tips

  • Use a secure method to store and manage service account tokens
  • Limit service account permissions to the minimum required for the CI/CD workflow
  • Monitor service account activity for any suspicious behavior

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

transformers - 💡(How to fix) Fix Orgs should be able to agree to 3rd party use agreements so their members can access 3rd party models [4 comments, 2 participants]