Proposal: Personal Access Tokens (PAT)

[rossigee]

Summary

Proposes Personal Access Tokens (PAT) as a modern, self-service authentication mechanism for Harbor. PATs provide named, time-limited credentials with audit trails, enabling secure CI/CD integration and programmatic access.

Features

• Self-service token management: Users create, list, update, and delete their own tokens
• Time-limited credentials: Configurable expiration (days or never-expire)
• Audit trail: Track token creation, updates, and usage via last_used_at
• Scoped permissions: Project-level scope enforcement
• Secure hashing: PBKDF2-SHA256 with per-token salt
• Backward compatible: Automatic migration of legacy OIDC CLI secrets

Related Work

• Upstream proposal: goharbor/community#287
• Implementation PR: container-registry/harbor-next#495
• Token format: hbr_pat_ + 32-character random secret
• Replaces legacy CLI token system with modern alternatives

---

Summary by cubic

Adds a proposal for Personal Access Tokens (PAT) that enable self-service, time-limited, auditable credentials for Harbor’s API and Docker login via Basic Auth. Defines the hbr_pat_ token format, deny-by-default project scoping, versioned PBKDF2-SHA256 hashing (v1:sha256:100000:salt:hash) with configurable iterations, a personal_access_token table (with update_time trigger and secret VARCHAR(255)), clarified audit logging vs last_used_at, and legacy OIDC CLI secret migration on first use.

^{Written for commit 2f90e0d. Summary will update on new commits.}

[coderabbitai]

Warning

Review limit reached

@rossigee, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 17 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bbd53db4-f21b-4a62-ae55-2a43bac80d1c

📥 Commits

Reviewing files that changed from the base of the PR and between 6ed942a and 2f90e0d.

📒 Files selected for processing (1)

• proposals/personal-access-tokens.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

✨ Simplify code

• Create PR with simplified code

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[gitar-bot]

Gitar is working

_Gitar

[cubic-dev-ai]

All reported issues were addressed

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>