Skip to content

docs: add UCP protocol exception to scope naming conventions#104

Closed
maxedenharter0507 wants to merge 1 commit intootto-de:mainfrom
maxedenharter0507:ucp-scope-naming-exception
Closed

docs: add UCP protocol exception to scope naming conventions#104
maxedenharter0507 wants to merge 1 commit intootto-de:mainfrom
maxedenharter0507:ucp-scope-naming-exception

Conversation

@maxedenharter0507
Copy link
Copy Markdown
Contributor

Summary

Add exception note to scope naming conventions documentation to permit colons (:) in scope names when used exclusively for Google's UCP (User Consent Protocol) compliance.

Changes

  • Updated api-guidelines/rest/authorization/scopes/rules/shoud-adhere-to-scope-naming-conventions.md
  • Added exception block explaining UCP protocol's use of colons as delimiters
  • Example scope format: ucp:scopes:checkout_session

Context

Google's UCP protocol requires predefined scopes to use colons as delimiters in their names. This is the only exception to the alphanumeric + _ or - character restriction in the naming conventions rule.

This documentation update accompanies backend (Herakles) and frontend (Olymp) implementations that enable colon support in scope IDs for full UCP compliance.

Google's UCP protocol requires colon delimiters in predefined scope names
(e.g. ucp:scopes:checkout_session). This update documents the exception
that permits colons in scope names exclusively for UCP compliance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant