Repository navigation
docs(identity-linking): say how a business answers a token it rejects on an ungated operation - #1044
Open
evoleinik wants to merge 1 commit into
Conversation
… on an ungated operation
Author
|
Two open items now lean on this paragraph. Proposal #1047 says a business that rejects the token answers The question in the description still stands. If maintainers would rather see this as an Enhancement Proposal, I'll move it. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds one paragraph to
identity_required. It covers an operation that no scope inconfig.scopesgates, when the request carries a user identity token anyway.A business that rejects that token SHOULD answer as it would for a gated operation:
401,error="invalid_token", andidentity_required. That is the answer RFC 6750 §3.1 gives for an invalid token. A business MAY instead ignore the token. The paragraph says so, and says the platform then can't tell why it got that answer.Scopes stays as it is: "The business defines the access policy for non-scoped operations; UCP does not prescribe a default." A business still decides who can call the operation, and whether it looks at tokens at all.
Why it matters: the Access Levels table puts personalized pricing at the user-authenticated level, and a catalog search can be ungated. A platform may send a token there to get one buyer's prices. If the token was revoked and the business quietly drops it, the platform sees the public view. It can't tell a revoked token from a buyer who doesn't qualify for those prices. A
401withinvalid_tokenlets it refresh the token or retry without it.The body keeps
identity_required, the code gated operations already use, because a new code would change the schema.We do this in a B2B seller integration that shows NDA-gated prices after identity linking. Background is in #1028. If maintainers read this as a protocol change, I'll move it to an Enhancement Proposal.
Category (Required)
ucp-schematool (resolver, linter, validator). (Requires Maintainer approval)Related Issues
Discussion: #1028
Checklist
!for breaking changes).🤖 Drafted with Claude Code. I checked it against the spec and tested our server's behavior.