Feature Request: scoped access tokens per repository.

[jeacott1]

Feature Request: I would very much like to be able to create a scoped access token that targets named repositories instead of all tokens applying to all repositories.

ie: for a given hub-user/org account -> create new access token RW + repo-name(s)

this would enable me to share access tokens to specific repositories and not compromise the access of any others that happen to also exist.

[technicallyjosh]

👋🏼 Hey there thanks for the suggestion! We have been looking at more enhancements for scoped tokens and more scopes in general. This is definitely aligned with what we are looking at doing. 😄 I'll see what we can do to get this on our roadmap in the near future.

[ArunJRK-KM]

@technicallyjosh any update on this?

[fedorov]

Lacking the proper solution, the only workaround I could come up with is creating a designated Docker Hub account that would have access only to the specific Docker Hub repositories, and use that designated account for generating access tokens. Hope this can help someone else too!

[nikolaj33]

This would be a very nice functionality! While this can be done via third party software, I would like to be able to create a token for a single private repository via docker hub and have that privilege scoped within a single repository.

[donotcodeit]

So far no progress on this? It would be nice to have fine-grained security. Without the ability to create scoped tokens, the hub encourages organizations to make accounts per repository.

@technicallyjosh, please tell us if this feature is planned or will be in a backlog for a while