News for hackers. Stuff that matters.
Re:Launch HN: Alter (YC S25) – Access control for multi-user... by ShalomDembe on Wednesday October 28, 2026 @04:25AM (#50270621)
The shared-API-key failure mode here is classic: once the agent “acts as” the same credential, authorization becomes binary (“does the key work?”) instead of contextual (“is this user allowed to do this action?”). The hard parts aren’t authentication—they’re policy enforcement and provenance.

A few things to sanity-check / ask about in any solution:

1. *Where is authorization enforced?* If the CRM/billing side only sees one API key identity, then the enforcement has to happen before requests leave your system (an authorization gateway), not “inside the agent” at best-effort level.

2. *Do you achieve least privilege per user?* Ideally: user-specific tokens (scoped OAuth, per-user API tokens, or a token exchange that mints short-lived credentials with constrained scopes). If not possible, you need an explicit mapping of user → allowed operations → resource set and block everything else.

3. *Strong auditability / attribution (“who did what?”).* You want logs that can answer, after the fact: user X initiated action Y on resource Z at time T, and which policy decision produced it. If all you record is “the shared credential called endpoint /charges”, you’ll struggle when banks/investors/auditors ask for evidence.

4. *Confused-deputy and prompt-injection controls.* Multi-user agents are basically “capability routers” for untrusted inputs. You need to treat the agent as potentially tricked and ensure policy checks are independent of the model’s output. Practical controls: structured tool calls, server-side validation of parameters against policy, and disallowing free-form “apply changes” operations.

5. *Resource-level authorization, not just action-level.* “User can update invoices” isn’t enough—you usually need “user can update their invoices/customers.” That implies resource ownership/tenant mapping and consistent ID normalization.

6. *Approvals and reconciliation for high-risk actions.* For destructive or money-moving operations, require an approval step and keep a reversible trail (request → approval → execution → final receipt).

If you’re replying to the “shared key” scenario, I’d be curious how you handle: - user-to-resource mapping (tenant/customer ownership), and - whether every outbound request is intercepted for policy checks with deterministic logs, rather than relying on the agent’s behavior.

Most “access control for agents” demos skip one of those, and that’s where incidents come from.

Re:Launch HN: Alter (YC S25) – Access control for multi-user... by kdodhia on Wednesday October 28, 2026 @09:06AM (#50272936)
hey Shalom! Good list, agree that's where most incidents come from. on your two questions:

- every outbound request goes through our proxy. the agent never holds the downstream credential so there's no path around it, and policy is evaluated deterministically there, not by the model. every call gets an audit row, denials included, with the agent, the end user it was acting for, the delegation chain, the grant, the operation, and the policy decision plus which rule produced it. so "user X did Y on Z at T and here's why it was allowed" is answerable after the fact

- User to resource mapping, honest answer is it depends on the credential. Where the provider supports it we push per-user oauth, so each end user connects their own account and the provider's own ownership checks apply. that's the cleanest least privilege - With a shared key we can't know who owns invoice 123 unless something tells us. what we do have is rules on the operation and its params (methods, paths, ids, recipients, amounts), so you can pin a user or agent to specific resources. but we don't keep a general ownership graph of your customers' data, that mapping still lives with you or the provider

On the rest: agents can only ever get a subset of the user's permissions (delegation narrows, never widens), money moving and destructive ops can require human approval on the exact frozen request, and our ai review can only escalate to a human, never allow something the rules didn't