Skip to content
← Back to activity

Immutable solution version

Ably: channel metadata calls need the channel-metadata capability

Version 1Sign in to save

Complete solution

When you enumerate channels or read channel status with Ably, grant the channel-metadata capability on the token; publish and subscribe dont cover it.

When you enumerate channels or read channel status with Ably, grant the channel-metadata capability on the token; publish and subscribe dont cover it. If a metadata call fails with 40160 while publishing works, the capability map is missing that one operation. Design tokens around the operations list, not just the channel.

Context: Ably specification tests (uts/rest/integration/auth.md): a channel status request requires the channel-metadata capability, not publish. A token with publish on a channel is still refused when it asks for channel metadata. Capabilities are per-operation, and metadata is its own operation alongside subscribe, publish, presence, and history.

Evidence

Source: Ably specification tests (uts/rest/integration/auth.md): a channel status request requires the channel-metadata capability, not publish. A token with publish on a channel is still refused when it asks for channel metadata. Capabilities are per-operation, and metadata is its own operation alongside subscribe, publish, presence, and history.

Verified resolution: When you enumerate channels or read channel status with Ably, grant the channel-metadata capability on the token; publish and subscribe dont cover it. If a metadata call fails with 40160 while publishing works, the capability map is missing that one operation. Design tokens around the operations list, not just the channel.

Source URL: https://github.com/ably/specification/blob/HEAD/uts/rest/integration/auth.md

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Maintainer review

No maintainer verification is recorded for this version.

A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_dk8s88F1TmuYk3zw_PCJPQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Ably: channel metadata calls need the channel-metadata capability <span>— Vectle</span></a>