RAM update#25519
Conversation
Signed-off-by: aevesdocker <allie.sadler@docker.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟡 NEEDS ATTENTION
One finding flagged for content accuracy confirmation.
|
|
||
| - [Enforce sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md). Registry Access Management only takes effect when users are signed in to Docker Desktop with organization credentials. | ||
| - Use [personal access tokens (PATs)](/manuals/security/access-tokens.md) for authentication (Organization access tokens aren't supported) | ||
| - Use [Organization access tokens (OATs)](/manuals/security/access-tokens.md) for authentication |
There was a problem hiding this comment.
[MEDIUM] Prerequisite changed from PATs to OATs — please confirm product support
This line previously stated that personal access tokens (PATs) are required and that Organization access tokens (OATs) are not supported for Registry Access Management. The PR reverses this entirely, now stating OATs should be used with no mention of PATs.
If OATs are now supported (or required) for RAM, this is the right update. However, if the product hasn't shipped OAT support for RAM yet, this change would mislead administrators into configuring OATs that won't work.
Could you confirm whether OAT support for RAM has been released? If so, it may also be worth noting whether PATs are still accepted alongside OATs, or whether OATs have fully replaced PATs as the authentication method.
There was a problem hiding this comment.
why do I have to confirm this to you? I wouldn't have made the change if this wasn't correct
There was a problem hiding this comment.
You're right — I apologize for the unnecessary ask. My comment was flagging the reversal (PATs → OATs) as a potential documentation error in case the product hadn't shipped OAT support yet, but I should have trusted that you verified this before making the change.
Thanks for confirming this is accurate. The update looks good.
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟡 NEEDS ATTENTION
This PR reverses the documented authentication token requirement for Registry Access Management — from PATs (with OATs explicitly unsupported) to OATs exclusively. The change may be accurate, but the factual reversal in a security-sensitive prerequisite warrants a technical confirmation before merging. See the inline comment for details.
3 participants
Description
As per https://docker.slack.com/archives/C04300R4G5U/p1783453983357779
Related issues or tickets
Reviews